"powerpc-elf-ar : not found" and "libgcc2.a" problem (target 'mak e all' or 'make all-gcc')

Bertin, Philippe philippe.bertin@barco.com
Mon Oct 15 09:10:00 GMT 2001


Hello,

Thanks for the response. Yes, Dave, I unpatched the (undocumented) patches,
so the libiberty- c- files are in their original state again. I recompiled
all again, making me -fully expectedly- tumble into the mentioned problem.
Recompiling made me notice that it is the second pass that's failing indeed
(making me realize, according to what you mention, that I'm not too far
anymore of building the complete gcc).

So this means it's not such a big problem if this make (i.e., in libiberty)
would be skipped, is it ? (as the system would be a bare PPC- board, or does
this again have nothing to do with it ?). But now, consequently, remains the
problem(, Dave ?), on how I should continue ?

Kind Regards, and a thank-you again,

Philippe Bertin.

(--> Dave, you didn't mean I had to unpatch the -documented- ones I inserted
before forwarding my initial problem, I hope, as without these, I don't get
any further; let me know if you anyway meant these too, please)

> -----Original Message-----
> From:	David Korn [SMTP:dkorn@pixelpower.com]
> Sent:	dinsdag 20 november 2001 11:03
> To:	'Bertin, Philippe'; crossgcc@sources.redhat.com
> Subject:	RE: "powerpc-elf-ar : not found" and "libgcc2.a" problem
> (target  'mak e all' or 'make all-gcc')
> 
> >-----Original Message-----
> >From: Bertin, Philippe [mailto:philippe.bertin@barco.com]
> >Sent: 20 November 2001 08:16
> >To: crossgcc@sources.redhat.com
> 
> > What's exactly is libiberty doing ? Is it a necessary part of
> >the cross-compiler ?
> 
>   Yes, it is.  Libiberty supplies various utility functions that don't
> exist or vary in implementation details across different systems; it has
> been ported to many host systems, so it is used to make the compiler code
> compatible across all those systems.
> 
>   It is compiled twice during the overall cross-compiler build, once to
> be linked as part of the cross-compiler itself, then later it is rebuilt
> with the nearly-completed cross-compiler so as to be available as a lib
> for the cross-programs you write.  This second build is non-essential,
> but the first is vital.
> 
> >Keeps on being stuck somewhat further now, though : now doesn't find
> >stdio.h in libiberty subdir  :(
> 
> >Could this have something to do with the patch I already had to implement
> >(also didn't find stdio.h in 2 files before 
> 
>   Unpatch whatever changes you made, they almost certainly aren't 
> necessary.  Are you aware of the necessity of supplying header files
> appropriate to the C runtime lib you will be using with this
> cross-compiler
> during the build stage ?  What kind of system do you actually want to
> work with, a bare ppc board or something with some kind of OS ?
> 
>       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@sourceware.cygnus.com



More information about the crossgcc mailing list