cross compiler sparc m68k

David Korn
Mon Feb 11 07:58:00 GMT 2002

>-----Original Message-----
>From: Peter Barada []
>Sent: 11 February 2002 15:12
>Subject: Re: cross compiler sparc m68k
>>Do not use newer binutils with gcc-2.95.3. There are problems at least
>>for the m68000 target, which has to be used for 68302 processors.
>What problems does binutils-2.11.* have with 68000?
>>The scripts from Bill Gatliff work out of the box for a C 
>only compiler
>>but need some tweaks for a C++ compiler. I have them in the company so
>>you may contact me next week if you run into problems.
>If you have a build script that creates a C++ compiler configured for
>m68k-elf, I'd be much appreciative.  I've been trying to put one
>together for a while and haven't had any luck, again failing 
>in libiberty.

  Peter, I am right in thinking that it fails when building the *target*
version of libiberty, yes?  From one of your earlier posts:

make[2]: Entering directory
make[2]: *** No targets specified and no makefile found.  Stop.
make[2]: Leaving directory
make[1]: *** [../libiberty/libiberty.a] Error 2
make[1]: Leaving directory
make: *** [all-target-libstdc++] Error 2

  IIRC, libstdc++ doesn't actually use this libiberty; it's just provided
as a convenience (hah!)  Have you tried just cd'ing into the target
libiberty directory


and doing "touch makefile; touch libiberty.a" ?  You might need to make a
few subdirs under there and make dummy libiberty.a in those as well to
recreate the effects of multilibbing, if that's relevant, but then if the
libstdc++ doesn't actually link with libiberty, the build should complete.

Burn your ID card!
Help support the campaign, copy this into your .sig!

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list