gcc-4.0 FTBFS on, uh, i386

Bug #22024 reported by Debian Bug Importer
6
Affects Status Importance Assigned to Milestone
gcc-4.0 (Debian)
Fix Released
Unknown
gcc-4.0 (Ubuntu)
Invalid
High
Matthias Klose

Bug Description

Automatically imported from Debian bug report #329108 http://bugs.debian.org/329108

Revision history for this message
In , Matthias Klose (doko-cs) wrote : Re: Bug#329108: gcc-4.0 FTBFS on, uh, i386

> On the latest i386 Sid, gcc-4.0 does not build from source, on my machine,
> and on a buildd (see the logs). With dash as sh, I get:

this is known, we're waiting on proper 64bit support from glibc. I'd
like to downgrade this one until we have the support.

Goto, you did say, you wanted address this after the last update. any
news?

    Matthias

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #329108 http://bugs.debian.org/329108

Revision history for this message
Matthias Klose (doko) wrote :

breezy does have proper biarch

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (4.7 KiB)

Message-Id: <email address hidden>
Date: Mon, 19 Sep 2005 12:12:10 -0400
From: Christopher Martin <email address hidden>
To: <email address hidden>
Subject: gcc-4.0 FTBFS on, uh, i386

--nextPart13136425.vzM4ZBCDmG
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Package: gcc-4.0
Version: 4.0.1-8
Severity: serious

Hello,

On the latest i386 Sid, gcc-4.0 does not build from source, on my machine,=
=20
and on a buildd (see the logs). With dash as sh, I get:

Will not build the Pascal compiler: disabled for 4.0
Will build the Ada compiler.
Will build the shared Ada libraries.
Will build the Treelang compiler.
Will build the FFI library.
Will run the testsuite.
/bin/bash: -c: line 0: syntax error near unexpected token `)'
make[1]: *** [stamps/04-configure-stamp] Error 2

Making bash sh solves this. Next up I get the following:

In file included from /usr/include/bits/mathinline.h:5,
                 from /usr/include/math.h:382,
                 from ../../../../src/libiberty/floatformat.c:27:
/usr/include/x86_64-linux/bits/mathinline.h:45: error: syntax error before=
=20
=E2=80=98{=E2=80=99 token
/usr/include/x86_64-linux/bits/mathinline.h:46: error: syntax error before=
=20
=E2=80=98}=E2=80=99 token
/usr/include/x86_64-linux/bits/mathinline.h:46: error: field name not in=20
record or union initializer
/usr/include/x86_64-linux/bits/mathinline.h:46: error: (near initialization=
=20
for =E2=80=98__u=E2=80=99)
/usr/include/x86_64-linux/bits/mathinline.h:46: error: =E2=80=98__x=E2=80=
=99 undeclared here=20
(not in a function)
/usr/include/x86_64-linux/bits/mathinline.h:47: error: syntax error before=
=20
=E2=80=98return=E2=80=99
/usr/include/x86_64-linux/bits/mathinline.h:51: error: syntax error before=
=20
=E2=80=98{=E2=80=99 token
/usr/include/x86_64-linux/bits/mathinline.h:52: error: conflicting types fo=
r=20
=E2=80=98__i=E2=80=99
/usr/include/x86_64-linux/bits/mathinline.h:46: error: previous declaration=
=20
of =E2=80=98__i=E2=80=99 was here
/usr/include/x86_64-linux/bits/mathinline.h:52: error: syntax error before=
=20
=E2=80=98}=E2=80=99 token
/usr/include/x86_64-linux/bits/mathinline.h:52: error: redefinition of =E2=
=80=98__u=E2=80=99
/usr/include/x86_64-linux/bits/mathinline.h:46: error: previous definition=
=20
of =E2=80=98__u=E2=80=99 was here
/usr/include/x86_64-linux/bits/mathinline.h:52: error: field name not in=20
record or union initializer
/usr/include/x86_64-linux/bits/mathinline.h:52: error: (near initialization=
=20
for =E2=80=98__u=E2=80=99)
/usr/include/x86_64-linux/bits/mathinline.h:53: error: syntax error before=
=20
=E2=80=98return=E2=80=99
/usr/include/x86_64-linux/bits/mathinline.h:57: error: syntax error before=
=20
=E2=80=98{=E2=80=99 token
/usr/include/x86_64-linux/bits/mathinline.h:58: error: conflicting types fo=
r=20
=E2=80=98__i=E2=80=99
/usr/include/x86_64-linux/bits/mathinline.h:46: error: previous declaration=
=20
of =E2=80=98__i=E2=80=99 was here
/usr/include/x86_64-linux/bits/mathinline.h:58: error: syntax error before=
=20
=E2=80=98}=E2=80=99 token
/usr/include/x86_64-linux/bits/mathinline.h:58: erro...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 19 Sep 2005 19:27:15 +0200
From: Matthias Klose <email address hidden>
To: Christopher Martin <email address hidden>,
        <email address hidden>
CC: <email address hidden>, <email address hidden>
Subject: Re: Bug#329108: gcc-4.0 FTBFS on, uh, i386

> On the latest i386 Sid, gcc-4.0 does not build from source, on my machine,
> and on a buildd (see the logs). With dash as sh, I get:

this is known, we're waiting on proper 64bit support from glibc. I'd
like to downgrade this one until we have the support.

Goto, you did say, you wanted address this after the last update. any
news?

    Matthias

Revision history for this message
In , GOTO Masanori (gotom) wrote :

At Mon, 19 Sep 2005 19:27:15 +0200,
Matthias Klose wrote:
> > On the latest i386 Sid, gcc-4.0 does not build from source, on my machine,
> > and on a buildd (see the logs). With dash as sh, I get:
>
> this is known, we're waiting on proper 64bit support from glibc. I'd
> like to downgrade this one until we have the support.
>
> Goto, you did say, you wanted address this after the last update. any
> news?

Does this mean glibc needs to support i386 support on amd64? If so,
no progress yet because I thought Jeff worked for it. Should it to be
available for gcc-4.0?

Regards,
-- gotom

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <8164srkf0y.wl%<email address hidden>>
Date: Fri, 23 Sep 2005 23:57:49 +0900
From: GOTO Masanori <email address hidden>
To: Matthias Klose <email address hidden>
Cc: Christopher Martin <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#329108: gcc-4.0 FTBFS on, uh, i386

At Mon, 19 Sep 2005 19:27:15 +0200,
Matthias Klose wrote:
> > On the latest i386 Sid, gcc-4.0 does not build from source, on my machine,
> > and on a buildd (see the logs). With dash as sh, I get:
>
> this is known, we're waiting on proper 64bit support from glibc. I'd
> like to downgrade this one until we have the support.
>
> Goto, you did say, you wanted address this after the last update. any
> news?

Does this mean glibc needs to support i386 support on amd64? If so,
no progress yet because I thought Jeff worked for it. Should it to be
available for gcc-4.0?

Regards,
-- gotom

Revision history for this message
In , Matthias Klose (doko-cs) wrote :

GOTO Masanori writes:
> At Mon, 19 Sep 2005 19:27:15 +0200,
> Matthias Klose wrote:
> > > On the latest i386 Sid, gcc-4.0 does not build from source, on my machine,
> > > and on a buildd (see the logs). With dash as sh, I get:
> >
> > this is known, we're waiting on proper 64bit support from glibc. I'd
> > like to downgrade this one until we have the support.
> >
> > Goto, you did say, you wanted address this after the last update. any
> > news?
>
> Does this mean glibc needs to support i386 support on amd64? If so,
> no progress yet because I thought Jeff worked for it. Should it to be
> available for gcc-4.0?

No, this is about amd64 support for i386, replacing amd64-libs. I'm
currently building i386 biarch packages using glibc-2.3.2, which is
bad. The idea was to keep this, until lkh/glibc provide the updated
kernel headers. AFAIK Jeff did contact you about that. the biarch
support for amd64 is another thing, which would be nice to have, but
is not as urgent, because the ia32-libs still work.

 Matthias

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 24 Sep 2005 01:53:46 +0200
From: Matthias Klose <email address hidden>
To: GOTO Masanori <email address hidden>, <email address hidden>
Cc: Christopher Martin <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: Bug#329108: gcc-4.0 FTBFS on, uh, i386

GOTO Masanori writes:
> At Mon, 19 Sep 2005 19:27:15 +0200,
> Matthias Klose wrote:
> > > On the latest i386 Sid, gcc-4.0 does not build from source, on my machine,
> > > and on a buildd (see the logs). With dash as sh, I get:
> >
> > this is known, we're waiting on proper 64bit support from glibc. I'd
> > like to downgrade this one until we have the support.
> >
> > Goto, you did say, you wanted address this after the last update. any
> > news?
>
> Does this mean glibc needs to support i386 support on amd64? If so,
> no progress yet because I thought Jeff worked for it. Should it to be
> available for gcc-4.0?

No, this is about amd64 support for i386, replacing amd64-libs. I'm
currently building i386 biarch packages using glibc-2.3.2, which is
bad. The idea was to keep this, until lkh/glibc provide the updated
kernel headers. AFAIK Jeff did contact you about that. the biarch
support for amd64 is another thing, which would be nice to have, but
is not as urgent, because the ia32-libs still work.

 Matthias

Revision history for this message
In , Matthias Klose (doko-cs) wrote : tag gcc report

tags 329108 + pending
thanks

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 15 Oct 2005 03:42:58 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>
Subject: tag gcc report

tags 329108 + pending
thanks

Revision history for this message
In , Matthias Klose (doko) wrote : Bug#329108: fixed in gcc-4.0 4.0.2-3
Download full text (13.7 KiB)

Source: gcc-4.0
Source-Version: 4.0.2-3

We believe that the bug you reported is fixed in the latest version of
gcc-4.0, which is due to be installed in the Debian FTP archive:

cpp-4.0-doc_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/cpp-4.0-doc_4.0.2-3_all.deb
cpp-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/cpp-4.0_4.0.2-3_i386.deb
fastjar_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/fastjar_4.0.2-3_i386.deb
fixincludes_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/fixincludes_4.0.2-3_i386.deb
g++-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/g++-4.0_4.0.2-3_i386.deb
gcc-4.0-base_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gcc-4.0-base_4.0.2-3_i386.deb
gcc-4.0-doc_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/gcc-4.0-doc_4.0.2-3_all.deb
gcc-4.0-locales_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/gcc-4.0-locales_4.0.2-3_all.deb
gcc-4.0_4.0.2-3.diff.gz
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.2-3.diff.gz
gcc-4.0_4.0.2-3.dsc
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.2-3.dsc
gcc-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.2-3_i386.deb
gcj-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gcj-4.0_4.0.2-3_i386.deb
gfortran-4.0-doc_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/gfortran-4.0-doc_4.0.2-3_all.deb
gfortran-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gfortran-4.0_4.0.2-3_i386.deb
gij-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gij-4.0_4.0.2-3_i386.deb
gnat-4.0-doc_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/gnat-4.0-doc_4.0.2-3_all.deb
gnat-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gnat-4.0_4.0.2-3_i386.deb
gobjc-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gobjc-4.0_4.0.2-3_i386.deb
lib64gcc1_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64gcc1_4.0.2-3_i386.deb
lib64gfortran0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64gfortran0_4.0.2-3_i386.deb
lib64objc1_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64objc1_4.0.2-3_i386.deb
lib64stdc++6-4.0-dbg_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64stdc++6-4.0-dbg_4.0.2-3_i386.deb
lib64stdc++6_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64stdc++6_4.0.2-3_i386.deb
libffi4-dev_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libffi4-dev_4.0.2-3_i386.deb
libffi4_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libffi4_4.0.2-3_i386.deb
libgcc1_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcc1_4.0.2-3_i386.deb
libgcj-common_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/libgcj-common_4.0.2-3_all.deb
libgcj6-awt_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-awt_4.0.2-3_i386.deb
libgcj6-common_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/libgcj6-common_4.0.2-3_all.deb
libgcj6-dbg_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-dbg_4.0.2-3_i386.deb
libgcj6-dev_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-dev_4.0.2-3_i386.deb
libgcj6-src_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/libgcj6-src_4.0.2-3_all.deb
libgcj6_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcj6_4.0.2-3_i386.deb
libgfortran0-dev_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgfortran0-dev_4.0.2-3_i386.deb
libgfortran0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgfortran0_4.0.2-3_i386.deb
libgnat-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgnat-4.0_4.0.2-3_i386.deb
libmudflap0-dev_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libmudflap0-dev_4.0.2-3_i386.deb
lib...

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (13.9 KiB)

Message-Id: <email address hidden>
Date: Mon, 24 Oct 2005 15:17:26 -0700
From: Matthias Klose <email address hidden>
To: <email address hidden>
Subject: Bug#329108: fixed in gcc-4.0 4.0.2-3

Source: gcc-4.0
Source-Version: 4.0.2-3

We believe that the bug you reported is fixed in the latest version of
gcc-4.0, which is due to be installed in the Debian FTP archive:

cpp-4.0-doc_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/cpp-4.0-doc_4.0.2-3_all.deb
cpp-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/cpp-4.0_4.0.2-3_i386.deb
fastjar_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/fastjar_4.0.2-3_i386.deb
fixincludes_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/fixincludes_4.0.2-3_i386.deb
g++-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/g++-4.0_4.0.2-3_i386.deb
gcc-4.0-base_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gcc-4.0-base_4.0.2-3_i386.deb
gcc-4.0-doc_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/gcc-4.0-doc_4.0.2-3_all.deb
gcc-4.0-locales_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/gcc-4.0-locales_4.0.2-3_all.deb
gcc-4.0_4.0.2-3.diff.gz
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.2-3.diff.gz
gcc-4.0_4.0.2-3.dsc
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.2-3.dsc
gcc-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.2-3_i386.deb
gcj-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gcj-4.0_4.0.2-3_i386.deb
gfortran-4.0-doc_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/gfortran-4.0-doc_4.0.2-3_all.deb
gfortran-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gfortran-4.0_4.0.2-3_i386.deb
gij-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gij-4.0_4.0.2-3_i386.deb
gnat-4.0-doc_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/gnat-4.0-doc_4.0.2-3_all.deb
gnat-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gnat-4.0_4.0.2-3_i386.deb
gobjc-4.0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/gobjc-4.0_4.0.2-3_i386.deb
lib64gcc1_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64gcc1_4.0.2-3_i386.deb
lib64gfortran0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64gfortran0_4.0.2-3_i386.deb
lib64objc1_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64objc1_4.0.2-3_i386.deb
lib64stdc++6-4.0-dbg_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64stdc++6-4.0-dbg_4.0.2-3_i386.deb
lib64stdc++6_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/lib64stdc++6_4.0.2-3_i386.deb
libffi4-dev_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libffi4-dev_4.0.2-3_i386.deb
libffi4_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libffi4_4.0.2-3_i386.deb
libgcc1_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcc1_4.0.2-3_i386.deb
libgcj-common_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/libgcj-common_4.0.2-3_all.deb
libgcj6-awt_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-awt_4.0.2-3_i386.deb
libgcj6-common_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/libgcj6-common_4.0.2-3_all.deb
libgcj6-dbg_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-dbg_4.0.2-3_i386.deb
libgcj6-dev_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-dev_4.0.2-3_i386.deb
libgcj6-src_4.0.2-3_all.deb
  to pool/main/g/gcc-4.0/libgcj6-src_4.0.2-3_all.deb
libgcj6_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgcj6_4.0.2-3_i386.deb
libgfortran0-dev_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/libgfortran0-dev_4.0.2-3_i386.deb
libgfortran0_4.0.2-3_i386.deb
  to pool/main/g/gcc-4.0/l...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.