This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/10331] [x86 -> SH] can't compile c++ crosscompiler part of gcc crosscompiler for sh-elf


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10331


dank@kegel.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dkegel@ixiacom.com


------- Additional Comments From dank@kegel.com  2003-06-04 16:32 -------
I can reproduce this here, and I think I understand what's going on.
Try this after configuring a cross gcc:
   egrep "STMP_FIXPROTO =|Don't run fix" */*/build-gcc/gcc/Makefile

On architectures I can build, I see e.g.

ppc-405-linux/gcc-3.3-glibc-2.2.5/build-gcc/gcc/Makefile:STMP_FIXPROTO =
stmp-fixproto
ppc-405-linux/gcc-3.3-glibc-2.2.5/build-gcc/gcc/Makefile:# Don't run fixproto
ppc-405-linux/gcc-3.3-glibc-2.2.5/build-gcc/gcc/Makefile:STMP_FIXPROTO =

On sh4, which fails with the current bug, I see e.g.
sh4-linux/gcc-3.3-glibc-2.2.5/build-gcc/gcc/Makefile:STMP_FIXPROTO = stmp-fixproto

So, where's that "Don't run fixproto" come from?

$ find . -type f | xargs grep " 
./gcc/ChangeLog.4:      * config/i386/x-beos (STMP_FIXPROTO): Don't run fixproto.
./gcc/config/t-freebsd:# Don't run fixproto
./gcc/config/t-interix:# Don't run fixproto
./gcc/config/t-linux:# Don't run fixproto
./gcc/config/t-linux-aout:# Don't run fixproto
./gcc/config/t-netbsd:# Don't run fixproto
./gcc/config/t-openbsd:# Don't run fixproto
./gcc/config/cris/t-cris:# Don't run fixproto
./gcc/config/i386/t-beos:# Don't run fixproto
./gcc/config/i386/t-cygwin:# Don't run fixproto
./gcc/config/xtensa/t-xtensa:# Don't run fixproto

That's as far as I've gotten.  I don't really understand
the gcc/config files, but it seems this is where the problem may lie.





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]