[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: glibc build failure



Finn Thain <fthain@telegraphics.com.au> writes:

> On Mon, 10 Jul 2006, Roger Leigh wrote:
>
>> > > Hi!
>> > > 
>> >> Roger Leigh <rleigh@debian.org> asked for a rebuild of glibc a) with
>> > > current version and gcc-3.2 
>> 
>> > Is that combination known to work on any other arch's?
>> 
>> I'm not sure if the 3.2 is a typo.  It fails reproducibly (4 times
>> now) with the current unstable sources (no modifications).  See also
>> #377699.
>>
>> The complete source tree is here:
>> http://people.debian.org/~rleigh/glibc2-failed-build.tar.bz2
>> The build log is in the above bug report.
>
> I was able to build those sources with two different cross toolchains:
> gcc-3.4.4 / binutils-2.15.94.0.2.2
> gcc-3.4.6 / binutils-2.17.50.0.2
>
> Obviously, I'm not using the same kernel headers, and my configure options 
> are different. You used,
>
> '--host=m68k-linux-gnu' '--build=m68k-linux-gnu'
> '--prefix=/usr' 
> '--without-cvs'
> '--enable-add-ons=libidn,linuxthreads ' 
> '--without-selinux' 
> '--with-headers=/home/rleigh/glibc2/glibc-2.3.6/debian/include' 
> '--enable-kernel=2.2.0'
> 'CC=gcc-3.4'
> 'CPPFLAGS=-isystem /home/rleigh/glibc2/glibc-2.3.6/debian/include' 
> 'build_alias=m68k-linux-gnu'
> 'host_alias=m68k-linux-gnu'
>
> whereas, I used,
>
> '--prefix=/usr'
> '--host=m68k-linux-gnu' '--build=powerpc-apple-darwin8.7.0'
> '--without-cvs'
> '--disable-profile' '--disable-debug' '--without-gd' '--enable-clocale=gnu' 
> '--with-headers=/opt/btc-0.10/gcc-3.4.6-binutils-2.17.50.0.2-glibc-2.3.6/m68k-linux/kernel-headers' 
> '--enable-add-ons=libidn,linuxthreads'
> '--without-selinux' 
> '--enable-kernel=2.2.0' 'CC=m68k-linux-gcc' 'CFLAGS=-O2'
> 'CPP=gcc -E -no-cpp-precomp'
> 'build_alias=powerpc-apple-darwin8.7.0' 
> 'host_alias=m68k-linux-gnu'
>
> My $CPP is set that way because I'm building on Mac OS X. I'm curious to 
> know why you needed to set -isystem in $CPPFLAGS?

I don't know.  I am simply building the Debian source "as is", with no
changes.

> The link command line that failed in your build is exactly the same here, 
> except it succeeds.
>
> Just prior to the link, from your log:
>
> gcc-3.4 iconvconfig.c -c -std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -fstrict-aliasing -g -pipe   
>
> ... and mine:
>
> m68k-linux-gcc iconvconfig.c -c -std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings
>
> I don't know whether this helps at all. I guess it doesn't if you already 
> have a good build.

I'm not sure if it's a problem with the build (the same sources have
previously built successfully on m68k).  I suspect a binutils
regression.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please sign and encrypt your mail.

Attachment: pgpLi1v4hSsaE.pgp
Description: PGP signature


Reply to: