On Sun, 2006-02-19 at 22:11 +0100, Ralf S. Engelschall wrote:
> On Sun, Feb 19, 2006, Joerg Lehrke wrote:
> 
> > I'm running in a similar problem with file (which is part of openpkg).
> >
> > GCC is using file to guess the default ABI on IRIX during the build
> > phase of libstdc++. Because of using the GNU file the ABI
> > "ELF 32-bit MSB mips-2" is used instead of "ELF N32 MSB mips-3" for the
> > library. The built compiler is generating "ELF N32 MSB mips-3" though.
> > This messes up every C++ compilation in the end.
> >
> > Since this may break the configure process on other platforms as well,
> > I'm wondering what would be the best solution. Why was file put in the
> > openpkg bootstrap package directly at all?
> 
> GNU file is part of RPM because RPM uses it for some content type
> guessing AFAIK. But the "openpkg" package installs file(1) under
> <prefix>/lib/openpkg/ and not <prefix>/bin/, so why does the file(1)
> from the "openpkg" package break anything during building of the "gcc"
> package?
>                                        Ralf S. Engelschall
>                                        [EMAIL PROTECTED]
>                                        www.engelschall.com

Just my guess. I failed to build MySQL over and over again and started
looking for the reason. What I found, was that my libstdc++.a comprised
only "ELF 32-bit MSB mips-2" object files. The original configure script
within gcc/libstdc++ finds out the ABI based on the output
of /usr/bin/file. After comparing GNU file and IRIX file output, I
thought I found the reason. But maybe I'm wrong and have to start
searching again :-(

        Cheers,
        J"org
-- 
Joerg Lehrke   GnuPG-KeyID: C66844AC     Pi-BI: 2593079121
The Knoc  http://k.noc.de/      Skype  callto://skypedzanq
Bgm.-Haffner-Str. 7,      D-87600 Kaufbeuren,      Germany
Tel +49 179 7882842           GNU -- Protect your freedom!

______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

Reply via email to