Hidden error(?) during build
Mon Jan 5 23:03:00 GMT 2009
On Mon, Jan 05, 2009 at 09:19:03PM +0100, Yann E. MORIN wrote:
> Nye, Micheal,
> On Monday 05 January 2009 21:08:05 Nye Liu wrote:
> > On Mon, Jan 05, 2009 at 09:00:01PM +0100, Yann E. MORIN wrote:
> > > I don't have PowerPC to test on. Does the toolchain work? What is .../getconf
> > > used for? Is it vital?
> > getconf is used to show how glibc is configured, eg "getconf -a"
> Surely there is a way around this, some incantation of:
> file -L /lib/libc.so.* |sed -r -e 's/.* (32|64)-bit .*/\1/;'
> Of course, if the libc was installed somewhere else, then you'd have
> to find where it is first...
At risk of going off topic:
i should clarify: what i meant by "here" was a different part of our
build system for our internal projects, not the tool chain build
scripts. I have *no* idea why *those glibc* scripts are checking getconf
"here" (for our projects) we can assume getconf always exists, it gets
installed as part of glibc, so we use it instead of "arch -m" :)
(818) 772-0576 fax
"Who would be stupid enough to quote a fictitious character?"
-- Don Quixote
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc