This fails with g++-4.6.1-4 from testing at the same place.
I've updated the packages in sourceforge, so no patches are needed.
I've attached a revised build.sh which runs the tests with the
current versions.
I was about to dive into a rant about "why didn't you try this before
releasing gcc/g++
Processing commands for cont...@bugs.debian.org:
> retitle 630441 g++-4.6 miscompilation
Bug #630441 [g++-4.6] g++-4.6.0-10 miscompilation
Changed Bug title to 'g++-4.6 miscompilation' from 'g++-4.6.0-10 miscompilation'
>
End of message, stopping processing here.
Please contact me if you need ass
Package: gnat-4.6
Version: 4.6.1-1
Severity: important
Justification: fails to build from source
gnat-4.6 fails to build on mips/mipsel due to a bootstrap comparison
failure. It appears that it is due to stage2 and stage3 not being
compiled with the same options: stage2 is compiled without debuggi
On 07/20/2011 11:54 AM, Andy Chittenden wrote:
>> By the way, Andy, could you give a quick reminder of what you are
>> using gcc 4.2 and 4.3 to do?
>
> We have some old code that we need to maintain that won't compile with later
> versions of the compiler.
IMO the better approach would be mult
Jonathan Nieder wrote:
> 1. Is there any GCC command-line option that people can use to work
>around this kind of thing (e.g., to add a directory to the front of
>the search order)?
Just for kicks (and in case there's a good place to document it):
mkdir /usr/local/lib/gcc/4.3.5
> By the way, Andy, could you give a quick reminder of what you are
> using gcc 4.2 and 4.3 to do?
We have some old code that we need to maintain that won't compile with later
versions of the compiler.
--
Andy, BlueArc Engineering
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debia
Jonathan Nieder wrote:
> Are there symlinks under /usr/lib/gcc hard-coding the path to libstdc++
> and libgfortran?
Ah, found them. Yes, in libstdc++6-4.x-dev and gfortran-4.x packages
(which presumably also need to be marked broken). Sorry for the noise.
--
To UNSUBSCRIBE, email to debian-
Matthias Klose wrote:
> libgcc2 and libgcc4 are missing. But I don't like it. Why stop at
> libgcc/libgomp, and not at libstdc++ and libgfortran?
Are there symlinks under /usr/lib/gcc hard-coding the path to libstdc++
and libgfortran?
> For now, I'll add an
> unconditional break on gcc-4.1 and g
Your message dated Wed, 20 Jul 2011 04:21:27 -0500
with message-id <20110720092127.ga26...@elie.gateway.2wire.net>
and subject line Re: apache2 segfault after libgomp1 4.2.2-4 4.3-20080116-1
upgrade
has caused the Debian Bug report #464072,
regarding apache2 segfault after libgomp1 4.2.2-4 4.3-200
On 07/20/2011 10:17 AM, Jonathan Nieder wrote:
> Jonathan Nieder wrote:
>
>> 2. Would it make sense to introduce a new package libgcc1-multiarch
>>and make libgcc1 into a compatibility package that ships a symlink
>>
>> /lib/libgcc_s.so.1 -> /lib/$arch/libgcc_s.so.1
>>
>>for the sake
Jonathan Nieder wrote:
> 2. Would it make sense to introduce a new package libgcc1-multiarch
>and make libgcc1 into a compatibility package that ships a symlink
>
> /lib/libgcc_s.so.1 -> /lib/$arch/libgcc_s.so.1
>
>for the sake of smooth partial upgrades?
i.e., something like this?
Simon Josefsson wrote:
> Jonathan Nieder writes:
>> Upgrading libgcj-bc to 4.6.1-2 fixes it.
[...]
> Did you see this recently? I just uploaded libidn-1.22-2 which happened
> to be built correctly on both sparc and powerpc. So it seems this issue
> is gone again? At least on the buildd's.
See
Jonathan Nieder writes:
> reassign 630417 libgcj-bc 1.106
> affects 630417 + gcj-4.6-jdk
> found 630417 gcc-defaults/1.96
> fixed 630417 gcc-defaults/1.107
> quit
> (pruning cc list)
>
> Hi,
>
> Simon Josefsson wrote:
>
>> Ok, so possibly #630417 does not fix the problem? I'm cc'ing the bug
>> f
13 matches
Mail list logo
