[PR 16152] perl-5.8.4 fails to build using gcc-3.3.4 on {ia64,arm,m68k}-linux

Bug #6828 reported by Debian Bug Importer
6
Affects Status Importance Assigned to Milestone
gcc-3.3 (Debian)
Fix Released
Unknown
gcc-3.3 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

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

Revision history for this message
In , James Troup (james-nocrew) wrote : Re: Bug#247176: perl_5.8.4-1(ia64/unstable): FTBFS: segv in miniperl

<email address hidden> writes:

> Package: perl
> Version: 5.8.4-1
> Severity: serious
>
> There was an error while trying to autobuild your package:

Arm dies in a similar manner, FWIW.

--
James

Revision history for this message
In , Goswin von Brederlow (brederlo) wrote : FTBFS: m68k: miniperl segfaults

Package: perl
Version: 5.8.4-1
Severity: normal
Followup-For: Bug #247176

Hi,

perl sems to build perl.static fine but then fails on the dynmic one:

...
/miniperl -Ilib configpm configpm.tmp
sh mv-if-diff configpm.tmp lib/Config.pm
/miniperl -Ilib lib/lib_pm.PL
Extracting lib.pm (with variable substitutions)
        AutoSplitting perl library
/miniperl -Ilib -e 'use AutoSplit; \
autosplit_lib_modules(@ARGV)' lib/*.pm
/miniperl -Ilib -e 'use AutoSplit; \
autosplit_lib_modules(@ARGV)' lib/*/*.pm
make lib/re.pm
make[2]: Entering directory `/home/mrvn/perl/perl-5.8.4'
cp ext/re/re.pm ext/re/re.tmp && sh mv-if-diff ext/re/re.tmp lib/re.pm
make[2]: Leaving directory `/home/mrvn/perl/perl-5.8.4'

        Making DynaLoader (static)
ext/util/make_ext: line 123: 17221 Segmentation fault ../$depth/miniperl -I../$depth/lib Makefile.PL INSTALLDIRS=perl PERL_CORE=1 $passthru
Warning: No Makefile!
make[2]: Entering directory `/home/mrvn/perl/perl-5.8.4/ext/DynaLoader'
make[2]: *** No rule to make target `config'. Stop.
..

I did send a full build logfile to buildd.debian.org but I'm not sure I
got the syntax right. If it doesn't show up i can post it extra.

MfG
 Goswin

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: m68k
Kernel: Linux 2.2.10
Locale: LANG=C, LC_CTYPE=C

Versions of packages perl depends on:
ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an
ii libdb4.0 4.0.14-1.2 Berkeley v4.0 Database Libraries [
ii libgdbm3 1.8.3-1 GNU dbm database routines (runtime
ii perl-base 5.8.2-2 The Pathologically Eclectic Rubbis
ii perl-modules 5.8.2-2 Core Perl modules.

-- no debconf information

Revision history for this message
In , Brendan O'Dea (bod) wrote : Re: Bug#247176: perl_5.8.4-1(ia64/unstable): FTBFS: segv in miniperl

On Mon, May 03, 2004 at 11:57:22AM -0600, <email address hidden> wrote:
>Package: perl
>Version: 5.8.4-1
>Severity: serious
>
>There was an error while trying to autobuild your package:
>> ./miniperl -w -Ilib -MExporter -e '<?>' || /usr/bin/make minitest
>> Attempt to free unreferenced scalar: SV 0x60000000000575e0.
>> ./miniperl -Ilib configpm configpm.tmp
>> make[1]: *** [lib/Config.pm] Segmentation fault
>> make[1]: Leaving directory `/build/buildd/perl-5.8.4'
>> make: *** [perl.static] Error 2

This appears to be an optimiser issue, setting DEB_BUILD_OPTIONS=noopt
in the envionment (-O0) allows the package to build sucessfully.

I added -g to the build to attempt to determine the point of faulure,
but unfortunately it doesn't SEGV under gdb (see comments on
#debian-ia64).

--bod

Revision history for this message
In , Adam Conrad (adconrad) wrote : perl segfaults during build

FWIW, as of 5.8.4-2, m68k appears to fail in exactly the same way as arm
and ia64.

... Adam

Revision history for this message
In , Adam Conrad (adconrad-trinitysoftware) wrote :

In the interest of building all the other packages that build-dep on the
newer perl, I'll be building the m68k packages with -O0 and uploading
them, but this bug should remain open until this issue is tracked down
and cleared up in the package itself (even if the fix is just to lower
optimisation in debian/rules on m68k/arm/ia64 for now).

... Adam

--
backup [n] (bak'up): The duplicate copy of crucial data that no one
                     bothered to make; used only in the abstract.

1024D/C6CEA0C9 C8B2 CB3E 3225 49BB 5ED2 0002 BE3C ED47 C6CE A0C9

Revision history for this message
In , Brendan O'Dea (bod) wrote : Re: Bug#247176: perl segfaults during build

On Fri, Jun 04, 2004 at 05:21:24PM +1000, Adam Conrad wrote:
>In the interest of building all the other packages that build-dep on the
>newer perl, I'll be building the m68k packages with -O0 and uploading
>them, but this bug should remain open until this issue is tracked down
>and cleared up in the package itself (even if the fix is just to lower
>optimisation in debian/rules on m68k/arm/ia64 for now).

You might try this patch first before building the whole thing as -O0.

--- perl-5.8.4/cflags.SH 2002-09-30 20:59:07.000000000 +1000
+++ /tmp/cflags.SH 2004-05-12 13:58:50.000000000 +1000
@@ -107,8 +107,7 @@
     perlmain) ;;
     perly) ;;
     pp) ;;
- pp_ctl) ;;
- pp_hot) ;;
+ pp_ctl|pp_hot|pp_sort) optimize=-O1;;
     pp_pack) ;;
     pp_sys) ;;
     regcomp) ;;

--bod

Revision history for this message
In , Adam Conrad (adconrad) wrote : perl build patch...

With that patch, the build fails with the following:

-----
cc -L/usr/local/lib -o miniperl \
    miniperlmain.o opmini.o libperl.a -ldl -lm -lpthread -lc -lcrypt
./miniperl -w -Ilib -MExporter -e '<?>' || /usr/bin/make minitest
/miniperl -Ilib configpm configpm.tmp
sh mv-if-diff configpm.tmp lib/Config.pm
/miniperl -Ilib lib/lib_pm.PL
Undefined subroutine &main::dirname called at lib/lib_pm.PL line 7.
make[1]: *** [lib/lib.pm] Error 9
make[1]: Leaving directory `/home/adconrad/build/perl/perl-5.8.4'
make: *** [perl.debug] Error 2
-----

The full build log is at:
http://a4000t.hk-soft.net/~adconrad/perl-build.log

.. Adam

Revision history for this message
In , Adam Conrad (adconrad-trinitysoftware) wrote : FTBFS: segv in miniperl

And, to make things more interesting, this is how the build ends when using
DEB_BUILD_OPTIONS=noopt:
------
./miniperl -Ilib configpm configpm.tmp
Name "main::INC" used only once: possible typo at configpm line 659.
Use of uninitialized value in index at (eval 1) line 10.
Use of uninitialized value in index at (eval 1) line 14.
Use of uninitialized value in substr at (eval 1) line 16.
Use of uninitialized value in index at (eval 1) line 10.
Use of uninitialized value in index at (eval 1) line 14.
Use of uninitialized value in substr at (eval 1) line 16.
Use of uninitialized value in string eq at configpm line 395.
Use of uninitialized value in numeric eq (==) at configpm line 395.
Use of uninitialized value in numeric eq (==) at configpm line 398.
Use of uninitialized value in numeric eq (==) at configpm line 398.
Use of uninitialized value in concatenation (.) or string at configpm line
408.
make[1]: *** [lib/Config.pm] Segmentation fault
make[1]: Leaving directory `/home/adconrad/build/perl/perl-5.8.4'
make: *** [perl.static] Error 2
------

Full build log at: http://a4000t.hk-soft.net/~adconrad/perl-build-2.log

.. Adam

--
backup [n] (bak'up): The duplicate copy of crucial data that no one
                     bothered to make; used only in the abstract.

1024D/C6CEA0C9 C8B2 CB3E 3225 49BB 5ED2 0002 BE3C ED47 C6CE A0C9

Revision history for this message
In , Matthias Klose (doko-cs) wrote : Re: (ia64/arm/m68k/unstable): FTBFS: segv in miniperl

This may be a compiler bug. On ia64 the package builds using gcc-3.4
from experimental. I didn't try to build 5.8.3 to see if this was
triggered by the new perl version.

Maybe it's an alternative to build miniperl with gcc-2.96 on ia64 and
gcc-2.95 on arm and m68k?

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

A perl-5.8.3-3 build on ia64-linux using gcc-3.3.4-1 succeeds.

Revision history for this message
In , Matthias Klose (doko-cs) wrote : working around perl-5.8.4 build failure on ia64, arm and m68k

clone 247176 -1
reassign -1 gcc-3.3
tags 247176 + patch
forwarded -1 http://gcc.gnu.org/PR16152
retitle -1 [PR 16152] perl-5.8.4 fails to build using gcc-3.3.4 on {ia64,arm,m68k}-linux
tags -1 + upstream

on ia64-linux the build succeeds using gcc-2.96 (not gcc-3.2). please check, if
gcc-3.2 or gcc-2.95 work on arm and m68k.

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

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

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

Message-ID: <email address hidden>
Date: Mon, 3 May 2004 11:57:22 -0600
From: <email address hidden>
To: <email address hidden>
Subject: perl_5.8.4-1(ia64/unstable): FTBFS: segv in miniperl

Package: perl
Version: 5.8.4-1
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of perl_5.8.4-1 on caballero by sbuild/ia64 1.170.5
> Build started at 20040503-1455

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: file, cpio, libdb4.2-dev, libgdbm-dev, netbase [!hurd-i386], gcc (>= 3:3.2.2-0)

[...]

> `sh cflags "optimize='-O2'" miniperlmain.o` miniperlmain.c
> CCCMD = cc -DPERL_CORE -c -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBIAN -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -Wall
> rm -f opmini.c
> cp op.c opmini.c
> `sh cflags "optimize='-O2'" opmini.o` -DPERL_EXTERNAL_GLOB opmini.c
> CCCMD = cc -DPERL_CORE -c -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBIAN -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -Wall
> rm -f opmini.c
> cc -L/usr/local/lib -o miniperl \
> miniperlmain.o opmini.o libperl.a -ldl -lm -lpthread -lc -lcrypt
> ./miniperl -w -Ilib -MExporter -e '<?>' || /usr/bin/make minitest
> Attempt to free unreferenced scalar: SV 0x60000000000575e0.
> ./miniperl -Ilib configpm configpm.tmp
> make[1]: *** [lib/Config.pm] Segmentation fault
> make[1]: Leaving directory `/build/buildd/perl-5.8.4'
> make: *** [perl.static] Error 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=ia64&pkg=perl&ver=5.8.4-1

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

Message-ID: <email address hidden>
Date: Mon, 03 May 2004 19:35:43 +0100
From: James Troup <email address hidden>
To: <email address hidden>
Subject: Re: Bug#247176: perl_5.8.4-1(ia64/unstable): FTBFS: segv in miniperl

<email address hidden> writes:

> Package: perl
> Version: 5.8.4-1
> Severity: serious
>
> There was an error while trying to autobuild your package:

Arm dies in a similar manner, FWIW.

--
James

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

Message-Id: <email address hidden>
Date: Wed, 05 May 2004 17:37:32 +0200
From: Goswin von Brederlow <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: FTBFS: m68k: miniperl segfaults

Package: perl
Version: 5.8.4-1
Severity: normal
Followup-For: Bug #247176

Hi,

perl sems to build perl.static fine but then fails on the dynmic one:

...
/miniperl -Ilib configpm configpm.tmp
sh mv-if-diff configpm.tmp lib/Config.pm
/miniperl -Ilib lib/lib_pm.PL
Extracting lib.pm (with variable substitutions)
        AutoSplitting perl library
/miniperl -Ilib -e 'use AutoSplit; \
autosplit_lib_modules(@ARGV)' lib/*.pm
/miniperl -Ilib -e 'use AutoSplit; \
autosplit_lib_modules(@ARGV)' lib/*/*.pm
make lib/re.pm
make[2]: Entering directory `/home/mrvn/perl/perl-5.8.4'
cp ext/re/re.pm ext/re/re.tmp && sh mv-if-diff ext/re/re.tmp lib/re.pm
make[2]: Leaving directory `/home/mrvn/perl/perl-5.8.4'

        Making DynaLoader (static)
ext/util/make_ext: line 123: 17221 Segmentation fault ../$depth/miniperl -I../$depth/lib Makefile.PL INSTALLDIRS=perl PERL_CORE=1 $passthru
Warning: No Makefile!
make[2]: Entering directory `/home/mrvn/perl/perl-5.8.4/ext/DynaLoader'
make[2]: *** No rule to make target `config'. Stop.
..

I did send a full build logfile to buildd.debian.org but I'm not sure I
got the syntax right. If it doesn't show up i can post it extra.

MfG
 Goswin

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: m68k
Kernel: Linux 2.2.10
Locale: LANG=C, LC_CTYPE=C

Versions of packages perl depends on:
ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an
ii libdb4.0 4.0.14-1.2 Berkeley v4.0 Database Libraries [
ii libgdbm3 1.8.3-1 GNU dbm database routines (runtime
ii perl-base 5.8.2-2 The Pathologically Eclectic Rubbis
ii perl-modules 5.8.2-2 Core Perl modules.

-- no debconf information

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

Message-ID: <email address hidden>
Date: Tue, 11 May 2004 23:07:35 +1000
From: Brendan O'Dea <email address hidden>
To: <email address hidden>, <email address hidden>
Cc: James Troup <email address hidden>
Subject: Re: Bug#247176: perl_5.8.4-1(ia64/unstable): FTBFS: segv in miniperl

On Mon, May 03, 2004 at 11:57:22AM -0600, <email address hidden> wrote:
>Package: perl
>Version: 5.8.4-1
>Severity: serious
>
>There was an error while trying to autobuild your package:
>> ./miniperl -w -Ilib -MExporter -e '<?>' || /usr/bin/make minitest
>> Attempt to free unreferenced scalar: SV 0x60000000000575e0.
>> ./miniperl -Ilib configpm configpm.tmp
>> make[1]: *** [lib/Config.pm] Segmentation fault
>> make[1]: Leaving directory `/build/buildd/perl-5.8.4'
>> make: *** [perl.static] Error 2

This appears to be an optimiser issue, setting DEB_BUILD_OPTIONS=noopt
in the envionment (-O0) allows the package to build sucessfully.

I added -g to the build to attempt to determine the point of faulure,
but unfortunately it doesn't SEGV under gdb (see comments on
#debian-ia64).

--bod

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

Message-ID: <08f801c43b2a$f9c2e0a0$0400000a@0c3.net>
Date: Sun, 16 May 2004 19:48:42 +1000
From: "Adam Conrad" <adconrad@0c3.net>
To: <email address hidden>
Subject: perl segfaults during build

FWIW, as of 5.8.4-2, m68k appears to fail in exactly the same way as arm
and ia64.

... Adam

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

Message-ID: <000101c44a04$8ba1d520$<email address hidden>>
Date: Fri, 4 Jun 2004 17:21:24 +1000
From: "Adam Conrad" <email address hidden>
To: <email address hidden>
Subject: perl segfaults during build

In the interest of building all the other packages that build-dep on the
newer perl, I'll be building the m68k packages with -O0 and uploading
them, but this bug should remain open until this issue is tracked down
and cleared up in the package itself (even if the fix is just to lower
optimisation in debian/rules on m68k/arm/ia64 for now).

... Adam

--
backup [n] (bak'up): The duplicate copy of crucial data that no one
                     bothered to make; used only in the abstract.

1024D/C6CEA0C9 C8B2 CB3E 3225 49BB 5ED2 0002 BE3C ED47 C6CE A0C9

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

Message-ID: <email address hidden>
Date: Sat, 5 Jun 2004 17:04:10 +1000
From: Brendan O'Dea <email address hidden>
To: Adam Conrad <email address hidden>, <email address hidden>
Subject: Re: Bug#247176: perl segfaults during build

On Fri, Jun 04, 2004 at 05:21:24PM +1000, Adam Conrad wrote:
>In the interest of building all the other packages that build-dep on the
>newer perl, I'll be building the m68k packages with -O0 and uploading
>them, but this bug should remain open until this issue is tracked down
>and cleared up in the package itself (even if the fix is just to lower
>optimisation in debian/rules on m68k/arm/ia64 for now).

You might try this patch first before building the whole thing as -O0.

--- perl-5.8.4/cflags.SH 2002-09-30 20:59:07.000000000 +1000
+++ /tmp/cflags.SH 2004-05-12 13:58:50.000000000 +1000
@@ -107,8 +107,7 @@
     perlmain) ;;
     perly) ;;
     pp) ;;
- pp_ctl) ;;
- pp_hot) ;;
+ pp_ctl|pp_hot|pp_sort) optimize=-O1;;
     pp_pack) ;;
     pp_sys) ;;
     regcomp) ;;

--bod

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

Message-ID: <27c201c44b6d$7843e350$0400000a@0c3.net>
Date: Sun, 6 Jun 2004 12:24:59 +1000
From: "Adam Conrad" <adconrad@0c3.net>
To: <email address hidden>
Subject: perl build patch...

With that patch, the build fails with the following:

-----
cc -L/usr/local/lib -o miniperl \
    miniperlmain.o opmini.o libperl.a -ldl -lm -lpthread -lc -lcrypt
./miniperl -w -Ilib -MExporter -e '<?>' || /usr/bin/make minitest
/miniperl -Ilib configpm configpm.tmp
sh mv-if-diff configpm.tmp lib/Config.pm
/miniperl -Ilib lib/lib_pm.PL
Undefined subroutine &main::dirname called at lib/lib_pm.PL line 7.
make[1]: *** [lib/lib.pm] Error 9
make[1]: Leaving directory `/home/adconrad/build/perl/perl-5.8.4'
make: *** [perl.debug] Error 2
-----

The full build log is at:
http://a4000t.hk-soft.net/~adconrad/perl-build.log

.. Adam

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

Message-ID: <000b01c44cf7$35bc9140$<email address hidden>>
Date: Tue, 8 Jun 2004 11:23:31 +1000
From: "Adam Conrad" <email address hidden>
To: <email address hidden>
Subject: FTBFS: segv in miniperl

And, to make things more interesting, this is how the build ends when using
DEB_BUILD_OPTIONS=noopt:
------
./miniperl -Ilib configpm configpm.tmp
Name "main::INC" used only once: possible typo at configpm line 659.
Use of uninitialized value in index at (eval 1) line 10.
Use of uninitialized value in index at (eval 1) line 14.
Use of uninitialized value in substr at (eval 1) line 16.
Use of uninitialized value in index at (eval 1) line 10.
Use of uninitialized value in index at (eval 1) line 14.
Use of uninitialized value in substr at (eval 1) line 16.
Use of uninitialized value in string eq at configpm line 395.
Use of uninitialized value in numeric eq (==) at configpm line 395.
Use of uninitialized value in numeric eq (==) at configpm line 398.
Use of uninitialized value in numeric eq (==) at configpm line 398.
Use of uninitialized value in concatenation (.) or string at configpm line
408.
make[1]: *** [lib/Config.pm] Segmentation fault
make[1]: Leaving directory `/home/adconrad/build/perl/perl-5.8.4'
make: *** [perl.static] Error 2
------

Full build log at: http://a4000t.hk-soft.net/~adconrad/perl-build-2.log

.. Adam

--
backup [n] (bak'up): The duplicate copy of crucial data that no one
                     bothered to make; used only in the abstract.

1024D/C6CEA0C9 C8B2 CB3E 3225 49BB 5ED2 0002 BE3C ED47 C6CE A0C9

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

Message-ID: <email address hidden>
Date: Mon, 21 Jun 2004 07:36:22 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>
CC: <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: (ia64/arm/m68k/unstable): FTBFS: segv in miniperl

This may be a compiler bug. On ia64 the package builds using gcc-3.4
from experimental. I didn't try to build 5.8.3 to see if this was
triggered by the new perl version.

Maybe it's an alternative to build miniperl with gcc-2.96 on ia64 and
gcc-2.95 on arm and m68k?

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

Message-ID: <email address hidden>
Date: Mon, 21 Jun 2004 08:29:17 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>
Subject: Re: (ia64/arm/m68k/unstable): FTBFS: segv in miniperl

A perl-5.8.3-3 build on ia64-linux using gcc-3.3.4-1 succeeds.

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

Message-ID: <email address hidden>
Date: Wed, 23 Jun 2004 08:42:58 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>, <email address hidden>, <email address hidden>
CC: <email address hidden>
Subject: working around perl-5.8.4 build failure on ia64, arm and m68k

clone 247176 -1
reassign -1 gcc-3.3
tags 247176 + patch
forwarded -1 http://gcc.gnu.org/PR16152
retitle -1 [PR 16152] perl-5.8.4 fails to build using gcc-3.3.4 on {ia64,arm,m68k}-linux
tags -1 + upstream

on ia64-linux the build succeeds using gcc-2.96 (not gcc-3.2). please check, if
gcc-3.2 or gcc-2.95 work on arm and m68k.

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

tags 255801 + fixed-upstream
severity 255801 important
retitle 255801 [PR 16152, fixed in 3.4] perl-5.8.4 fails to build using gcc-3.3.4 on {ia64,arm,m68k}-linux
thanks

Revision history for this message
Matt Zimmerman (mdz) wrote :

This bug does not appear to affect any Warty architectures

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

Message-ID: <email address hidden>
Date: Sat, 26 Jun 2004 11:57:36 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>
Subject: tag gcc report

tags 255801 + fixed-upstream
severity 255801 important
retitle 255801 [PR 16152, fixed in 3.4] perl-5.8.4 fails to build using gcc-3.3.4 on {ia64,arm,m68k}-linux
thanks

Revision history for this message
In , Matthias Klose (doko) wrote : Bug#255801: fixed in gcc-4.0 4.0.1-1
Download full text (23.3 KiB)

Source: gcc-4.0
Source-Version: 4.0.1-1

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.1-1_all.deb
  to pool/main/g/gcc-4.0/cpp-4.0-doc_4.0.1-1_all.deb
cpp-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/cpp-4.0_4.0.1-1_i386.deb
fastjar_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/fastjar_4.0.1-1_i386.deb
fixincludes_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/fixincludes_4.0.1-1_i386.deb
g++-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/g++-4.0_4.0.1-1_i386.deb
gcc-4.0-base_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gcc-4.0-base_4.0.1-1_i386.deb
gcc-4.0-doc_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/gcc-4.0-doc_4.0.1-1_all.deb
gcc-4.0-locales_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/gcc-4.0-locales_4.0.1-1_all.deb
gcc-4.0_4.0.1-1.diff.gz
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.1-1.diff.gz
gcc-4.0_4.0.1-1.dsc
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.1-1.dsc
gcc-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.1-1_i386.deb
gcc-4.0_4.0.1.orig.tar.gz
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.1.orig.tar.gz
gcj-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gcj-4.0_4.0.1-1_i386.deb
gfortran-4.0-doc_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/gfortran-4.0-doc_4.0.1-1_all.deb
gfortran-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gfortran-4.0_4.0.1-1_i386.deb
gij-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gij-4.0_4.0.1-1_i386.deb
gnat-4.0-doc_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/gnat-4.0-doc_4.0.1-1_all.deb
gnat-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gnat-4.0_4.0.1-1_i386.deb
gobjc-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gobjc-4.0_4.0.1-1_i386.deb
lib64gcc1_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/lib64gcc1_4.0.1-1_i386.deb
lib64stdc++6-4.0-dbg_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/lib64stdc++6-4.0-dbg_4.0.1-1_i386.deb
lib64stdc++6_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/lib64stdc++6_4.0.1-1_i386.deb
libffi4-dev_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libffi4-dev_4.0.1-1_i386.deb
libffi4_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libffi4_4.0.1-1_i386.deb
libgcc1_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcc1_4.0.1-1_i386.deb
libgcj-common_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/libgcj-common_4.0.1-1_all.deb
libgcj6-awt_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-awt_4.0.1-1_i386.deb
libgcj6-common_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/libgcj6-common_4.0.1-1_all.deb
libgcj6-dbg_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-dbg_4.0.1-1_i386.deb
libgcj6-dev_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-dev_4.0.1-1_i386.deb
libgcj6-src_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/libgcj6-src_4.0.1-1_all.deb
libgcj6_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcj6_4.0.1-1_i386.deb
libgfortran0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgfortran0_4.0.1-1_i386.deb
libgnat-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgnat-4.0_4.0.1-1_i386.deb
libmudflap0-dev_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libmudflap0-dev_4.0.1-1_i386.deb
libmudflap0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libmudflap0_4.0.1-1_i386.deb
libobjc1_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libobjc1_4.0.1-1_i386.deb
libstdc++6-4.0-dbg_4.0.1-1_i3...

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

Message-Id: <email address hidden>
Date: Sun, 10 Jul 2005 13:47:39 -0400
From: Matthias Klose <email address hidden>
To: <email address hidden>
Subject: Bug#255801: fixed in gcc-4.0 4.0.1-1

Source: gcc-4.0
Source-Version: 4.0.1-1

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.1-1_all.deb
  to pool/main/g/gcc-4.0/cpp-4.0-doc_4.0.1-1_all.deb
cpp-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/cpp-4.0_4.0.1-1_i386.deb
fastjar_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/fastjar_4.0.1-1_i386.deb
fixincludes_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/fixincludes_4.0.1-1_i386.deb
g++-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/g++-4.0_4.0.1-1_i386.deb
gcc-4.0-base_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gcc-4.0-base_4.0.1-1_i386.deb
gcc-4.0-doc_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/gcc-4.0-doc_4.0.1-1_all.deb
gcc-4.0-locales_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/gcc-4.0-locales_4.0.1-1_all.deb
gcc-4.0_4.0.1-1.diff.gz
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.1-1.diff.gz
gcc-4.0_4.0.1-1.dsc
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.1-1.dsc
gcc-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.1-1_i386.deb
gcc-4.0_4.0.1.orig.tar.gz
  to pool/main/g/gcc-4.0/gcc-4.0_4.0.1.orig.tar.gz
gcj-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gcj-4.0_4.0.1-1_i386.deb
gfortran-4.0-doc_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/gfortran-4.0-doc_4.0.1-1_all.deb
gfortran-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gfortran-4.0_4.0.1-1_i386.deb
gij-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gij-4.0_4.0.1-1_i386.deb
gnat-4.0-doc_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/gnat-4.0-doc_4.0.1-1_all.deb
gnat-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gnat-4.0_4.0.1-1_i386.deb
gobjc-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/gobjc-4.0_4.0.1-1_i386.deb
lib64gcc1_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/lib64gcc1_4.0.1-1_i386.deb
lib64stdc++6-4.0-dbg_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/lib64stdc++6-4.0-dbg_4.0.1-1_i386.deb
lib64stdc++6_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/lib64stdc++6_4.0.1-1_i386.deb
libffi4-dev_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libffi4-dev_4.0.1-1_i386.deb
libffi4_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libffi4_4.0.1-1_i386.deb
libgcc1_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcc1_4.0.1-1_i386.deb
libgcj-common_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/libgcj-common_4.0.1-1_all.deb
libgcj6-awt_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-awt_4.0.1-1_i386.deb
libgcj6-common_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/libgcj6-common_4.0.1-1_all.deb
libgcj6-dbg_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-dbg_4.0.1-1_i386.deb
libgcj6-dev_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcj6-dev_4.0.1-1_i386.deb
libgcj6-src_4.0.1-1_all.deb
  to pool/main/g/gcc-4.0/libgcj6-src_4.0.1-1_all.deb
libgcj6_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgcj6_4.0.1-1_i386.deb
libgfortran0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgfortran0_4.0.1-1_i386.deb
libgnat-4.0_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libgnat-4.0_4.0.1-1_i386.deb
libmudflap0-dev_4.0.1-1_i386.deb
  to pool/main/g/gcc-4.0/libmudflap0-de...

Revision history for this message
Daniel Robitaille (robitaille) wrote :

Fixed in Debian in Jul 2005

Changed in gcc-3.3:
status: Unconfirmed → Fix Released
Revision history for this message
In , Bts-link-upstream (bts-link-upstream) wrote : [bts-link] source package gcc-3.3

#
# bts-link upstream status pull for source package gcc-3.3
# see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
#

user <email address hidden>

# remote status report for #169862
# * http://gcc.gnu.org/PR1823
# * remote status changed: (?) -> RESOLVED
# * remote resolution changed: (?) -> RESOLVED
forwarded 169862 http://gcc.gnu.org/PR1823
usertags 169862 + status-RESOLVED resolution-FIXED

# remote status report for #200140
# * http://gcc.gnu.org/PR11370
# * remote status changed: (?) -> RESOLVED
# * remote resolution changed: (?) -> RESOLVED
forwarded 200140 http://gcc.gnu.org/PR11370
usertags 200140 + status-RESOLVED resolution-FIXED

# remote status report for #212260
# * http://gcc.gnu.org/PR11624
# * remote status changed: (?) -> RESOLVED
# * remote resolution changed: (?) -> RESOLVED
forwarded 212260 http://gcc.gnu.org/PR11624
usertags 212260 + status-RESOLVED resolution-FIXED

# remote status report for #223226
# * http://gcc.gnu.org/PR12491
# * remote status changed: (?) -> RESOLVED
# * remote resolution changed: (?) -> RESOLVED
forwarded 223226 http://gcc.gnu.org/PR12491
usertags 223226 + status-RESOLVED resolution-FIXED

# remote status report for #224413
# * http://gcc.gnu.org/PR11295
# * remote status changed: (?) -> RESOLVED
# * remote resolution changed: (?) -> RESOLVED
forwarded 224413 http://gcc.gnu.org/PR11295
usertags 224413 + status-RESOLVED resolution-FIXED

# remote status report for #226148
# * http://gcc.gnu.org/PR11793
# * remote status changed: (?) -> RESOLVED
# * remote resolution changed: (?) -> RESOLVED
forwarded 226148 http://gcc.gnu.org/PR11793
usertags 226148 + status-RESOLVED resolution-FIXED

# remote status report for #242158
# * http://gcc.gnu.org/PR9390
# * remote status changed: (?) -> RESOLVED
# * remote resolution changed: (?) -> RESOLVED
forwarded 242158 http://gcc.gnu.org/PR9390
usertags 242158 + status-RESOLVED resolution-FIXED

# remote status report for #255801
# * http://gcc.gnu.org/PR14279
# * remote status changed: (?) -> RESOLVED
# * remote resolution changed: (?) -> RESOLVED
forwarded 255801 http://gcc.gnu.org/PR14279
usertags 255801 + status-RESOLVED resolution-FIXED

thanks

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.