Bug#782391: g++-4.9: false-positive -Warray-bounds apprently due to wrong integer-range inference

Package: g++-4.9 Version: 4.9.2-10 Severity: normal This warning can be seen while compiling skaakii-1.0.0 on several architectures (looks like it includes some 64bit archs, plus sparc). It does not appear with g++-4.8. https://qa.debian.org/bls/packages/s/sjaakii.html

Bug#763160: gcc-4.7: suggests non-existant packages: libmudflap0*, libppl9, libpwl5, libcloog-ppl0

Package: gcc-4.7 Version: 4.7.4-2 Severity: normal Some of those packages seem to have differnt version numbers now, it is not clear whether the new versions would help. Some others are just not in the archive anymore (mudflap). -- System Information: Debian Release: jessie/sid APT prefers

Bug#763161: gcc-4.8: suggests non-existant packages: binutils-gold, libbacktrace1-dbg

Package: gcc-4.8 Version: 4.8.3-11 Severity: normal Those packages are apparently not part of Debian any more. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64

Bug#763162: gcc-4.9: suggests non-existant packages: binutils-gold, libvtv0-dbg

Package: gcc-4.9 Version: 4.9.1-14 Severity: normal The gcc-4.9 source does not build libvtv any more but the deb still suggests it. Binutils-gold is not a separate package any more. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500,

[amd64/g++] Suspected toolchain bug causing dlopen to segfault

Hello, Context: http://bugs.debian.org/734318 - tulip: [amd64] segfaults inside dlopen when loading plugins http://bugs.debian.org/723982 - dlopen: segfaults right inside call_init What we get here is a number of plugins that when dlopen'd cause an obscure segfault inside libc code. Upstream

[amd64/g++] Suspected toolchain bug causing dlopen to segfault

[resend with bugs CC'd] Hello, Context: http://bugs.debian.org/734318 - tulip: [amd64] segfaults inside dlopen when loading plugins http://bugs.debian.org/723982 - dlopen: segfaults right inside call_init What we get here is a number of plugins that when dlopen'd cause an obscure segfault

Bug#390357: 64-bit specific error in bigloo, or in gij ?

Hi gij maintainers, Since that error the bigloo jvm tests show only occurs during, well, the jvm tests, I am wondering if it could not be a gij 64bit issue. For the background, the bigloo scheme compiler, among other target runtime environements, can generate JVM bytecode, and it is the

Bug#337850: gcj: [hppa] Can't find default package 'java.lang'

4.0.2-3Java development headers and stati ii zlib1g1:1.2.3-6 compression library - runtime Versions of packages gcj-4.0 recommends: ii fastjar 1:4.0.2-3 Jar creation utility -- no debconf information -- Yann Dirson[EMAIL

Bug#281445: gcc-3.3: generated object file cannot be linked

-c -Wall -march=i486 -Os -fomit-frame-pointer -fno-builtin -ffreestanding -fPIC reloc.c Right, it is in memtest82 3.2, which I finally uploaded yesterday with forced use of gcc-3.2. Arch is i386. -- Yann Dirson[EMAIL PROTECTED] | Debian-related: [EMAIL PROTECTED] | Support Debian GNU

Bug#281445: gcc-3.3: generated object file cannot be linked

1:3.4.2-3GCC support library -- no debconf information -- Yann Dirson[EMAIL PROTECTED] | Debian-related: [EMAIL PROTECTED] | Support Debian GNU/Linux: | Freedom, Power, Stability, Gratis http://ydirson.free.fr/| Check

Re: [bigloo] Re: Bigloo on Linux/ARM

LD_VERBOSE= $file Could that be a ld.so issue, maybe triggered by unexpected things in ELF headers ? On Fri, Jun 04, 2004 at 12:04:56AM +0200, Yann Dirson wrote: On Tue, Jun 01, 2004 at 11:34:36AM +0200, I wrote: I'll try to build at -O0, and then at -O1 if -O0 worked, and will let you

Re: Bigloo on Linux/ARM

. -- Yann Dirson[EMAIL PROTECTED] |Why make M$-Bill richer richer ? Debian-related: [EMAIL PROTECTED] | Support Debian GNU/Linux: Pro:[EMAIL PROTECTED] | Freedom, Power, Stability, Gratuity http://ydirson.free.fr/| Check http://www.debian.org/

Bigloo on Linux/ARM

it to build, the generated code is bad. I'll try to build at -O0, and then at -O1 if -O0 worked, and will let you know. I should also have a closer look at how gcc-3.2 performs, but that would be a pain to have to use it, since it's supposed to be phased out from Debian... -- Yann Dirson[EMAIL

Re: [bigloo] 2.6a-beta status on Debian

in the Bigloo configuration process... Do you know whether they have a problem-report and/or fix easily available for application on our 3.3 ? The debian gcc maintainers may be interested in applying the fix... Regards, -- Yann Dirson[EMAIL PROTECTED] |Why make M$-Bill richer richer ? Debian

Bug#195480: gcj-3.3 thinks a decl conflicts with itself

is based). Regards, -- Yann Dirson[EMAIL PROTECTED] |Why make M$-Bill richer richer ? Debian-related: [EMAIL PROTECTED] | Support Debian GNU/Linux: Pro:[EMAIL PROTECTED] | Freedom, Power, Stability, Gratuity http://ydirson.free.fr/| Check http://www.debian.org/

Bug#195480: gcj-3.3 thinks a decl conflicts with itself

and stati ii zlib1g1:1.1.4-12 compression library - runtime -- no debconf information -- Yann Dirson[EMAIL PROTECTED] |Why make M$-Bill richer richer ? Debian-related: [EMAIL PROTECTED] | Support Debian GNU/Linux: Pro:[EMAIL PROTECTED] | Freedom, Power, Stability

Re: gcc-2.95 bugs on m68k: what to do ?

On Mon, Oct 21, 2002 at 09:43:05PM +0200, Matthias Klose wrote: Yann Dirson writes: I have several packages (e2fsprogs, bigloo) that fail to build on m68k, apparently due to one or more gcc bug(s). Maybe that's the same as #146006, and #89023, but I can't tell that myself. Madkiss

How was compiled cssc on ia64, and other issues

silly about that is that gcc-3.1 only seems to be held out of testing because an error in copyright file (and maybe because binutils is held, which seems to come from an arm-specific patch not being applicable any more)... Are these issues to be settled in the near future ? Regards, -- Yann Dirson

Re: How was compiled cssc on ia64, and other issues

guess it's not... Sigh. Regards, -- Yann Dirson [EMAIL PROTECTED] http://www.alcove.com/ Technical support managerResponsable de l'assistance technique Senior Free-Software Consultant Consultant senior en Logiciels Libres Debian developer ([EMAIL PROTECTED

Bug#151103: libgcj3: conflicts with classpath

-- Yann Dirson[EMAIL PROTECTED] |Why make M$-Bill richer richer ? Debian-related: [EMAIL PROTECTED] | Support Debian GNU/Linux: Pro:[EMAIL PROTECTED] | Freedom, Power, Stability, Gratuity http://ydirson.free.fr/| Check http://www.debian.org/ -- To UNSUBSCRIBE, email

Bug#147702: gij-3.0: cannot configure

error exit status 2 Indeed, the \ was doubled: --slave /usr/share/man/man1/java.1.gz java.1.gz /usr/share/man/man1/gij-wrapper-3.0.1.gz \\ -- Yann Dirson[EMAIL PROTECTED] |Why make M$-Bill richer richer ? Debian-related: [EMAIL PROTECTED] | Support Debian GNU/Linux: Pro

Bug#117513: openc++: segfault or Error 139 compiling anything, even empty file

when built against libgc5. At first reading, the assembly code seems to be correct, but I'll have to read it again to be sure - long time since I worked with x86 asm, and it was with the Intel syntax :(. I'm a bit at a loss... I'll have to see that with upstream developpers. Regards, -- Yann

Bug#117513: openc++: segfault or Error 139 compiling anything, even empty file

for the hint. Regards, -- Yann Dirson[EMAIL PROTECTED] |Why make M$-Bill richer richer ? Debian-related: [EMAIL PROTECTED] | Support Debian GNU/Linux: Pro:[EMAIL PROTECTED] | Freedom, Power, Stability, Gratuity http://ydirson.free.fr/| Check http://www.debian.org/