Steve Langasek <[EMAIL PROTECTED]> writes:
> retitle 369642 g++-4.0/alpha: -fvisibility-inlines-hidden segfaults on
> reference to static method
> thanks
>
> Minimal test case attached, bug title updated accordingly. Build with g++
> -c -fvisibility-inlines-hidden on alpha to see the fun.
Maybe
The removal of the email address:
[EMAIL PROTECTED]
>From the mailing list:
Al-Manahel Newsletter List
is all set.
Date of this removal: Tue May 30 22:53:49 2006
Please save this email message for future reference.
--
retitle 369642 g++-4.0/alpha: -fvisibility-inlines-hidden segfaults on
reference to static method
thanks
Minimal test case attached, bug title updated accordingly. Build with g++
-c -fvisibility-inlines-hidden on alpha to see the fun.
Nice workaround for any of g++-4.0, g++-4.1, gcc-snapshot is
Processing commands for [EMAIL PROTECTED]:
> retitle 369642 g++-4.0/alpha: -fvisibility-inlines-hidden segfaults on
> reference to static method
Bug#369642: qt4-x11: FTBFS on alpha
Changed Bug title.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracki
Processing commands for [EMAIL PROTECTED]:
> clone 368883 -1
Bug#368883: qt4-x11: FTBFS on alpha
Bug 368883 cloned as bug 369642.
> reassign -1 g++-4.0
Bug#369642: qt4-x11: FTBFS on alpha
Bug reassigned from package `qt4-x11' to `g++-4.0'.
> severity -1 important
Bug#369642: qt4-x11: FTBFS on al
Processing commands for [EMAIL PROTECTED]:
> tags 367038 etch
Bug#367038: every upload of gcc breaks links in include directory
There were no tags set.
Tags added: etch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adminis
Processing commands for [EMAIL PROTECTED]:
> reassign 369547 gfortran-4.0
Bug#369547: gfortran: strange behaviour in unformatted writing
Bug reassigned from package `gfortran' to `gfortran-4.0'.
> tags 369547 + fixed-upstream
Bug#369547: gfortran: strange behaviour in unformatted writing
There we
reassign 369547 gfortran-4.0
tags 369547 + fixed-upstream
tags 369547 + upstream
severity 369547 important
thanks
gfortran-4.0 is not generally unusable.
Francesco Poli writes:
> Hi!
>
> The issue you are experiencing seems to be due to record-marker length
> lack of interoperability.
>
> In br
Processing commands for [EMAIL PROTECTED]:
> tag 361441 + fixed
Bug#361441: internal compiler error: in add_virtual_operand, at
tree-ssa-operands.c
Tags were: fixed-upstream upstream
Tags added: fixed
> tag 361591 + fixed
Bug#361591: internal compiler error: verify_ssa failed
Tags were: fixed-up
follows.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 30 May 2006 15:54:59 +0200
Source: gcc-snapshot
Binary: gcc-snapshot
Architecture: amd64 i386 powerpc source
Version: 20060530-1
Distribution: unstable
Urgency: low
Maintainer: Debian GCC Maintainers
Changed-By: Martin
Accepted:
gcc-snapshot_20060530-1.dsc
to pool/main/g/gcc-snapshot/gcc-snapshot_20060530-1.dsc
gcc-snapshot_20060530-1.tar.gz
to pool/main/g/gcc-snapshot/gcc-snapshot_20060530-1.tar.gz
gcc-snapshot_20060530-1_amd64.deb
to pool/main/g/gcc-snapshot/gcc-snapshot_20060530-1_amd64.deb
gcc-snapshot
gcc-snapshot_20060530-1_multi.changes uploaded successfully to localhost
along with the files:
gcc-snapshot_20060530-1.tar.gz
gcc-snapshot_20060530-1.dsc
gcc-snapshot_20060530-1_i386.deb
gcc-snapshot_20060530-1_amd64.deb
gcc-snapshot_20060530-1_powerpc.deb
Greetings,
Your Debian
Hi!
The issue you are experiencing seems to be due to record-marker length
lack of interoperability.
In brief, AIUI, the problem is that Fortran standard specifications do
not mandate any low level form for unformatted file I/O.
Hence every compiler adopts its own form and *no* unformatted file
i
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
gcc-snapshot_20060530-1.dsc
gcc-snapshot_20060530-1.tar.gz
gcc-snapshot_20060530-1_amd64.deb
gcc-snapshot_20060530-1_i386.deb
This looks like an upload, but a .changes file is missing, so the job
ca
--
fang at csl dot cornell dot edu changed:
What|Removed |Added
CC||fang at csl dot cornell dot
|
Package: gcc-snapshot
Version: 20060508-1
Looking at it now...
> Automatic build of asymptote_1.03-1 on bigsur by sbuild/mips 0.46
...
> g++ -Wall -ansi -DHAVE_CONFIG_H -DUSEGC -g -Wall -O2 -I/usr/include/gc -I
> . -I /usr/include/gc -o drawpath.o -c drawpath.cc
> drawpath.cc: In member funct
severity 367038 grave
thanks
On Sat, May 13, 2006 at 01:44:08AM +0200, Peter Eisentraut wrote:
> Package: java-gcj-compat
> Version: 1.0.30-4
> Severity: important
this is merely grave, the package renders gcj totally unusable.
> This package supplies:
>
> $ ls -l /usr/lib/jvm/java-gcj/includ
Processing commands for [EMAIL PROTECTED]:
> severity 367038 grave
Bug#367038: every upload of gcc breaks links in include directory
Severity set to `grave' from `important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(ad
Falk Hueffner wrote:
> Aurelien Jarno <[EMAIL PROTECTED]> writes:
>
> > Falk Hueffner a écrit :
> >> Aurelien Jarno <[EMAIL PROTECTED]> writes:
> >>
> >>>On arm, ia64 and alpha the glibc fails to build with gcc-4.1.
> >> On Alpha the problem is:
> >> {standard input}: Assembler messages:
> >> {sta
On Tue, May 30, 2006 at 02:50:16PM +0200, Wouter Verhelst wrote:
> On Tue, May 30, 2006 at 12:05:26PM +0200, Andreas Barth wrote:
> > Timeline
> >
> > Now, let's please take a more detailed look at the time line:
> > Thu 15 Jun 06:
> > last chance to switch to gcc 4.1, pyth
Aurelien Jarno <[EMAIL PROTECTED]> writes:
> Falk Hueffner a écrit :
>> Aurelien Jarno <[EMAIL PROTECTED]> writes:
>>
>>>On arm, ia64 and alpha the glibc fails to build with gcc-4.1.
>> On Alpha the problem is:
>> {standard input}: Assembler messages:
>> {standard input}:341: Error: macro requires
Falk Hueffner a écrit :
Aurelien Jarno <[EMAIL PROTECTED]> writes:
On arm, ia64 and alpha the glibc fails to build with gcc-4.1.
On Alpha the problem is:
{standard input}: Assembler messages:
{standard input}:341: Error: macro requires $at register while noat in effect
{standard input}:374
Aurelien Jarno <[EMAIL PROTECTED]> writes:
> On arm, ia64 and alpha the glibc fails to build with gcc-4.1.
On Alpha the problem is:
{standard input}: Assembler messages:
{standard input}:341: Error: macro requires $at register while noat in effect
{standard input}:374: Error: macro requires $at
On Tue, May 30, 2006 at 04:44:49PM +0200, Aurelien Jarno wrote:
> >I tried it on akire, but was interrupted by real world issues.
> >When you could give a more detailed HowTo (sbuild, dpkg-buildpackage,
> >whatever) I would retry...
> Very easy:
> dget http://people.debian.org/~aurel32/glibc/gli
Package: gfortran
Version: 4:4.0.3-4
Severity: grave
Justification: renders package unusable
I'm not sure this is a bug but I could not find any documentation of
this anomalous behaviuor.
Below you find two programs:
qaz.f
zaq.f
qaz.f writes 3 integers in un unformatted file
zaq.f reads three i
On Tue, May 30, 2006 at 04:31:33PM +0200, Aurelien Jarno wrote:
> I haven't done a build on m68k yet.
I tried it on akire, but was interrupted by real world issues.
When you could give a more detailed HowTo (sbuild, dpkg-buildpackage,
whatever) I would retry...
--
Ciao...//
Ingo Juergensmann a écrit :
On Tue, May 30, 2006 at 04:31:33PM +0200, Aurelien Jarno wrote:
I haven't done a build on m68k yet.
I tried it on akire, but was interrupted by real world issues.
When you could give a more detailed HowTo (sbuild, dpkg-buildpackage,
whatever) I would retry...
Aurelien Jarno a écrit :
Hi all,
As gcc-4.1 may be the default compiler soon (I hope so), I have tried to
build the glibc with it.
Currently it builds and works on the following architectures:
amd64, hppa, i386, mips, mipsel, sparc
The packages are available [1], but a but outdated. It shoul
--- Comment #11 from pinskia at gcc dot gnu dot org 2006-05-30 13:58
---
*** Bug 27816 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-05-30 13:58 ---
*** This bug has been marked as a duplicate of 20133 ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
On Tue, May 30, 2006 at 12:05:26PM +0200, Andreas Barth wrote:
> Timeline
>
>
> Now, let's please take a more detailed look at the time line:
>
>
> Thu 15 Jun 06:
>
> last chance to switch to gcc 4.1, python 2.4
> review architectures one more time
> last
31 matches
Mail list logo