This is the mail archive of the
crossgcc@sourceware.org
mailing list for the crossgcc project.
See the CrossGCC FAQ for lots
more information.
Re: error: conflicting types for 'psignal'
Tried to do paste using pastebin.com, but my browser wouldn't allow
it (the
'paste' option gets greyed as soon as I select and copy the contents
of that
file) - it may be because the actual build.log is over 27mb in size,
so any
other suggestions you have are welcome! I could compress that file
(it is
less than 1mb when archived), attach it in an email and send it
privately to
you - let me know if you would like me to do that.
Sure. Just send me the log and config.
Just did - let me know how you get on.
After spending 11 hours battling it out yesterday I was successful in
completing the build at last!
The problem seems to be stemming from the gcc version I used - 4.5.2.
When switched to 4.4.5 and did a few other tweaks I was able to complete
the process. I used the following package versions - gmp 5.0.1, mpfr
3.0.1, mpc 0.9, cloog 0.15.10, ppl 0.10.2, binutils 2.20.1, glibc 2.13
+ ports, gcc 4.4.5.
What I think helped me was using glibc and its ports packages - I was
able to include the newest versions, thankfully. I also discovered, what
I think is a bug in gcc.sh and have 2 patches to propose : 1) for fixing
an issue between ct-ng, ppl/cloog and gcc; and 2) for using mpfr 3.x+ to
build gcc 4.4.5 (without it mpfr 2.4.2 or older *must* be used,
otherwise build fails). Should I submit these patches as they are (in
clear text, not as attachments) for review? Yann?
Another issue I experienced is that I cannot use ppl version 0.11 and
above to build gcc 4.4.5 - linking fails with "undefined reference"
errors, so I was forced to use version 0.10.2 instead.
Lastly, when I built my executables (small programs which test the
functionality of the cross-compiler - nothing fancy) and list their
capabilities using "file" I get this: ELF 32-bit MSB executable, PowerPC
or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs),
for GNU/Linux 2.6.35, with unknown capability 0x41000000 = 0x13676e75,
with unknown capability 0x10000 = 0xb0401, stripped
There are 2 things which I don't know about - what is "unknown
capability 0x41000000" and "unknown capability 0x10000"? As evident, the
system is PPC, the CPU for which the whole toolchain is built is 603e
(G2 as it is also known).
Bryan, did you manage to find what the problem is with gcc 4.5.2?
--
For unsubscribe information see http://sourceware.org/lists.html#faq