You're making a lot of terrible assumptions and drawing several
incorrect conclusions. xnu-792 is not the same as "darwin7.9.2", and
no configure script in the last 6 years should be detecting a Mac OS
X system as "ppc-apple-darwin" (it should be "powerpc-apple-darwin").
What is the output of
% uname -r
% type uname
% /usr/share/libtool/config.guess
If you have GNU coreutils installed, something bad may be happening.
Shantonu
On Oct 2, 2005, at 3:42 PM, Marcin Dalecki wrote:
On 2005-10-03, at 00:26, Andrew Pinski wrote:
6) Is this whining reporting significant information, for the
person that wants to fix the bug?
Well on the system in question ppc-apple-darwin-7.8.0 the perl
script
in question simply doesn't work. Since there doesn't appear to be
much in the way of it inside acinclude.m4 it appears that setting
unconditionally enable_symvers inside the following:
I can confirm now that --disable-symvers worked fine on my system.
This perl script works just fine for me on powerpc-darwin7.9.0 I
don't
see why are we piping the output to nm when it should be piping nm's
output to c++filt.
Also this perl script works fine on powerpc-darwin7.4.0 also.
Well to be a bit more precise I have the following at hand:
uname -a
Darwin dzc14.neoplus.adsl.tpnet.pl 8.2.0 Darwin Kernel Version
8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu 792.2.4.obj~3/
RELEASE_PPC Power Macintosh powerpc
The configure scripting drama translates this in to:
ppc-apple-darwin7.8.0.
I'm not quite sure if this is correct since guessing the GCC
version interpretation here I would expect this to came out as:
ppc-apple-darwin7.9.2
aka: Tiger darwin 10.4.2
A fairly plain system without any additional fink darwinports or
similar packages. Perhaps this could be the cause that we have
basically different nm programs in action here?
