Your message dated Mon, 23 Nov 2009 23:37:00 -0500
with message-id <4b0b62ec.4030...@fifthhorseman.net>
and subject line debian bug #548842 resolved in libstdc++6 4.4.2-3
has caused the Debian Bug report #548842,
regarding libc6: alignment error in /lib/ld-linux.so.3 on armel
to be marked as done.
reassign 548842 libstdc++6
found 548842 4.4.1-4
thanks
On 11/23/2009 07:04 PM, Aurelien Jarno wrote:
> The problem is most probably a non word aligned relocation in the
> program you are trying to run or one of its library. You can list them
> with objdump -R file.
Since armel is a 32-bit machin
Processing commands for cont...@bugs.debian.org:
> reassign 548842 libstdc++6
Bug #548842 [gcc-4.3] libc6: alignment error in /lib/ld-linux.so.3 on armel
Bug reassigned from package 'gcc-4.3' to 'libstdc++6'.
Bug No longer marked as found in versions 4.3.4-2.
> found 548842 4.4.1-4
Bug #548842 [li
On Mon, Sep 28, 2009 at 11:34:06PM -0400, Daniel Kahn Gillmor wrote:
> Package: libc6
> Version: 2.9-25
> Severity: normal
>
> I'm running alsaplayer on an armel platform, using the -text frontend
> and the -alsa output. I've configured my armel machine to send a SIGBUS
> to any process which ma
On Mon, 23 Nov 2009, Carlos O'Donell wrote:
> I can successfully run apt-get with the new libstdc++6 that I just built.
>
> The testsuite result is cleaner:
> ~~~
> FAIL: 29_atomics/atomic_flag/clear/1.c execution test
> FAIL: 29_atomics/atomic_flag/test_and_set/explicit.c execution test
>
>
On Mon, Nov 23, 2009 at 08:17:03AM -0500, Carlos O'Donell wrote:
> On Mon, Nov 23, 2009 at 5:22 AM, Aurelien Jarno wrote:
> > Carlos O'Donell a écrit :
> >> On Sun, Nov 22, 2009 at 5:05 PM, John David Anglin
> >> wrote:
> While I set out the glibc types exactly as before (binary compatible),
On Mon, Nov 23, 2009 at 5:22 AM, Aurelien Jarno wrote:
> Carlos O'Donell a écrit :
>> On Sun, Nov 22, 2009 at 5:05 PM, John David Anglin
>> wrote:
While I set out the glibc types exactly as before (binary compatible),
the alignment restrictions were changed subtly.
>>> Excellent debuggi
Hi Lucas,
I talked to upstream and was assured that upstream is just as clueless as I am:
Both their and my build attempts on amd64 always worked fine, even if making
with -jX for some 2 <= X <= 8.
Is there any way one could get access to the system you're building these
packages, or could you t
Carlos O'Donell a écrit :
> On Sun, Nov 22, 2009 at 5:05 PM, John David Anglin
> wrote:
>>> While I set out the glibc types exactly as before (binary compatible),
>>> the alignment restrictions were changed subtly.
>> Excellent debugging!
>
> I have adjusted the glibc lock structure alignments to
9 matches
Mail list logo
