Bug#542666: bus errors

2009-08-20 Thread Andres Salomon
Here's more: localhost:~/telepathy-yafono# apt-get update Bus error localhost:~/telepathy-yafono# dpkg -i /var/cache/apt/archives/libstdc++6_4. libstdc++6_4.3.2-1.1_armel.deb libstdc++6_4.4.1-1_armel.deb libstdc++6_4.4.1-2_armel.deb localhost:~/telepathy-yafono# dpkg -i /var/cache/apt/ar

Bug#542666: libstdc++6: bus errors on ARM

2009-08-20 Thread Andres Salomon
Package: libstdc++6 Version: 4.4.1-2 Severity: important This is particularly problematic, as it breaks apt and aptitude on ARM. I'm not sure if it's all ARM hardware, or just mine. This is on an HTC G1 phone. localhost:~/telepathy-yafono# dpkg -l libstdc++6 [...] hi libstdc++6

Processed: Re: Processed: gcc -fPIE -pie generates corrupt executable on mips/mipsel

2009-08-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 526961 confget Bug #526961 [gcc-4.3] -fPIE -pie generates corrupt executable on mips/mipsel Bug reassigned from package 'gcc-4.3' to 'confget'. > tag 526961 + moreinfo Bug #526961 [confget] -fPIE -pie generates corrupt executable on mips/

Re: Processed: gcc -fPIE -pie generates corrupt executable on mips/mipsel

2009-08-20 Thread Matthias Klose
reassign 526961 confget tag 526961 + moreinfo thanks please evaluate if this is a duplicate of #532821 and then reassign and merge to the binutils report. On 20.08.2009 18:18, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: subscribe 526961 r...@ringlet.ne

Processed: gcc -fPIE -pie generates corrupt executable on mips/mipsel

2009-08-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > subscribe 526961 r...@ringlet.net There is no Debian Bug mailing list. If you wish to review bug reports please do so via http://www.debian.org/Bugs/ or ask this mail server to send them to you. soon: MAILINGLISTS_TEXT > reassign 526961 gcc-4.3 B

Re: GCC 4.4 run-time license and non-GPLv3 compilers

2009-08-20 Thread Matthias Klose
On 16.08.2009 10:50, Luk Claes wrote: Matthias Klose wrote: On 29.04.2009 04:49, Florian Weimer wrote: * Florian Weimer: I've asked the FSF for a clarification (the second time, the first clarification resulted in the Java bytecode exception). Until we know for sure how to interpret the exce