This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi all, I have encoutered (about ?) the same problem around November last year. But I don't remember what the solution has been (sorry for that, I just occasionally cross-compiled, and have encoutered that many problems that I don't remember the exact solution to this specific problem). You might be helped having a look into the logs on this newsgroup around Nov-Dec last year ... I can have a look too (later, though ...) Regards, Philippe Bertin > -----Original Message----- > From: David Korn [SMTP:dkorn@pixelpower.com] > Sent: maandag 11 februari 2002 16:58 > To: 'Peter Barada' > Cc: crossgcc@sources.redhat.com > Subject: RE: cross compiler sparc m68k > > >-----Original Message----- > >From: Peter Barada [mailto:pbarada@mail.wm.sps.mot.com] > >Sent: 11 February 2002 15:12 > >To: wolfgang.fritz@gmx.net > >Cc: crossgcc@sources.redhat.com > >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 > `/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68 > k- > elf/build-gcc/m68k-elf/libiberty' > make[2]: *** No targets specified and no makefile found. Stop. > make[2]: Leaving directory > `/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68 > k- > elf/build-gcc/m68k-elf/libiberty' > make[1]: *** [../libiberty/libiberty.a] Error 2 > make[1]: Leaving directory > `/home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68 > k- > elf/build-gcc/m68k-elf/libstdc++' > 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 > > /home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-g++-2.95.3/m68k > -e > lf/build-gcc/m68k-elf/libiberty > > 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. > > > DaveK > -- > Burn your ID card! http://www.optional-identity.org.uk/ > 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. > > www.mimesweeper.com > ********************************************************************** > > ------ > Want more information? See the CrossGCC FAQ, > http://www.objsw.com/CrossGCC/ > Want to unsubscribe? Send a note to > crossgcc-unsubscribe@sources.redhat.com ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |