gcc-4.0 FTBFS on, uh, i386
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://
In Debian Bug tracker #329108, Matthias Klose (doko-cs) wrote : Re: Bug#329108: gcc-4.0 FTBFS on, uh, i386 | #1 |
Debian Bug Importer (debzilla) wrote : | #2 |
Automatically imported from Debian bug report #329108 http://
Matthias Klose (doko) wrote : | #3 |
breezy does have proper biarch
Debian Bug Importer (debzilla) wrote : | #4 |
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
--nextPart13136
Content-Type: text/plain;
charset="utf-8"
Content-
Content-
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/
Making bash sh solves this. Next up I get the following:
In file included from /usr/include/
/usr/include/
=20
=E2=80=98{=E2=80=99 token
/usr/include/
=20
=E2=80=98}=E2=80=99 token
/usr/include/
record or union initializer
/usr/include/
=20
for =E2=80=
/usr/include/
=99 undeclared here=20
(not in a function)
/usr/include/
=20
=E2=80=
/usr/include/
=20
=E2=80=98{=E2=80=99 token
/usr/include/
r=20
=E2=80=
/usr/include/
=20
of =E2=80=
/usr/include/
=20
=E2=80=98}=E2=80=99 token
/usr/include/
=80=98__u=E2=80=99
/usr/include/
=20
of =E2=80=
/usr/include/
record or union initializer
/usr/include/
=20
for =E2=80=
/usr/include/
=20
=E2=80=
/usr/include/
=20
=E2=80=98{=E2=80=99 token
/usr/include/
r=20
=E2=80=
/usr/include/
=20
of =E2=80=
/usr/include/
=20
=E2=80=98}=E2=80=99 token
/usr/include/
Debian Bug Importer (debzilla) wrote : | #5 |
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
In Debian Bug tracker #329108, GOTO Masanori (gotom) wrote : | #6 |
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
Debian Bug Importer (debzilla) wrote : | #7 |
Message-ID: <8164srkf0y.
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
In Debian Bug tracker #329108, Matthias Klose (doko-cs) wrote : | #8 |
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
Debian Bug Importer (debzilla) wrote : | #9 |
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
In Debian Bug tracker #329108, Matthias Klose (doko-cs) wrote : tag gcc report | #10 |
tags 329108 + pending
thanks
Debian Bug Importer (debzilla) wrote : | #11 |
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
In Debian Bug tracker #329108, Matthias Klose (doko) wrote : Bug#329108: fixed in gcc-4.0 4.0.2-3 | #12 |
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-
to pool/main/
cpp-4.0_
to pool/main/
fastjar_
to pool/main/
fixincludes_
to pool/main/
g++-4.0_
to pool/main/
gcc-4.0-
to pool/main/
gcc-4.0-
to pool/main/
gcc-4.0-
to pool/main/
gcc-4.0_
to pool/main/
gcc-4.0_4.0.2-3.dsc
to pool/main/
gcc-4.0_
to pool/main/
gcj-4.0_
to pool/main/
gfortran-
to pool/main/
gfortran-
to pool/main/
gij-4.0_
to pool/main/
gnat-4.
to pool/main/
gnat-4.
to pool/main/
gobjc-4.
to pool/main/
lib64gcc1_
to pool/main/
lib64gfortran0_
to pool/main/
lib64objc1_
to pool/main/
lib64stdc+
to pool/main/
lib64stdc+
to pool/main/
libffi4-
to pool/main/
libffi4_
to pool/main/
libgcc1_
to pool/main/
libgcj-
to pool/main/
libgcj6-
to pool/main/
libgcj6-
to pool/main/
libgcj6-
to pool/main/
libgcj6-
to pool/main/
libgcj6-
to pool/main/
libgcj6_
to pool/main/
libgfortran0-
to pool/main/
libgfortran0_
to pool/main/
libgnat-
to pool/main/
libmudflap0-
to pool/main/
lib...
Debian Bug Importer (debzilla) wrote : | #13 |
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-
to pool/main/
cpp-4.0_
to pool/main/
fastjar_
to pool/main/
fixincludes_
to pool/main/
g++-4.0_
to pool/main/
gcc-4.0-
to pool/main/
gcc-4.0-
to pool/main/
gcc-4.0-
to pool/main/
gcc-4.0_
to pool/main/
gcc-4.0_4.0.2-3.dsc
to pool/main/
gcc-4.0_
to pool/main/
gcj-4.0_
to pool/main/
gfortran-
to pool/main/
gfortran-
to pool/main/
gij-4.0_
to pool/main/
gnat-4.
to pool/main/
gnat-4.
to pool/main/
gobjc-4.
to pool/main/
lib64gcc1_
to pool/main/
lib64gfortran0_
to pool/main/
lib64objc1_
to pool/main/
lib64stdc+
to pool/main/
lib64stdc+
to pool/main/
libffi4-
to pool/main/
libffi4_
to pool/main/
libgcc1_
to pool/main/
libgcj-
to pool/main/
libgcj6-
to pool/main/
libgcj6-
to pool/main/
libgcj6-
to pool/main/
libgcj6-
to pool/main/
libgcj6-
to pool/main/
libgcj6_
to pool/main/
libgfortran0-
to pool/main/
libgfortran0_
to pool/main/
> 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