Re: Bug#677139: gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5

2012-06-12 Thread Guillem Jover
On Wed, 2012-06-13 at 08:10:02 +0200, Raphael Hertzog wrote: > On Wed, 13 Jun 2012, Guillem Jover wrote: > > On Wed, 2012-06-13 at 07:06:47 +0200, Guillem Jover wrote: > > > I've actually have had this on my TODO to deal with, which I found > > > when checking libudt on armel some time ago. I'm rea

Re: Bug#677139: gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5

2012-06-12 Thread Raphael Hertzog
On Wed, 13 Jun 2012, Raphael Hertzog wrote: > If some of them are no longer "internal machinery" and no longer present in > random libraries, then we ought to de-blacklist them. Or rather, you should force their inclusion in libgcc's symbols file. We created the "ignore-blacklist" option for this

Re: Bug#677139: gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5

2012-06-12 Thread Raphael Hertzog
Hello, On Wed, 13 Jun 2012, Guillem Jover wrote: > On Wed, 2012-06-13 at 07:06:47 +0200, Guillem Jover wrote: > > I've actually have had this on my TODO to deal with, which I found > > when checking libudt on armel some time ago. I'm reassigning and will > > push a fix for dpkg 1.16.5. > > Actual

Bug#677139: gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5

2012-06-12 Thread Raphael Hertzog
On Tue, 12 Jun 2012, Matthias Klose wrote: > Raphael, should dpkg-shlibdeps behave differently about these? I can't see > anything wrong on the GCC side. I don't know. Is there anything special about this symbol? We have a bunch of "blacklisted" symbols in dpkg-shlibdeps. Should this one be added

Processed: Re: Bug#677139: gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5

2012-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 677139 libgcc1 Bug #677139 [dpkg-dev] gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5 Bug reassigned from package 'dpkg-dev' to 'libgcc1'. Ignoring request to alter found versions of bug #677139 to the same values previously se

Re: Bug#677139: gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5

2012-06-12 Thread Guillem Jover
reassign 677139 libgcc1 retitle 677139 libgcc1: Missing entries in symbols file on EABI arches thanks Sorry, it seems I misremembered the issue here! On Wed, 2012-06-13 at 07:06:47 +0200, Guillem Jover wrote: > On Mon, 2012-06-11 at 20:16:51 +0200, Bernhard R. Link wrote: > > Package: gcc-4.6 > >

Processed (with 1 errors): Re: Bug#677139: gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5

2012-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 677139 dpkg-dev Bug #677139 [gcc-4.6] gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5 Bug reassigned from package 'gcc-4.6' to 'dpkg-dev'. No longer marked as found in versions gcc-4.6/4.6.2-6. Ignoring request to alter fixed ve

Bug#677139: gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5

2012-06-12 Thread Guillem Jover
reassign 677139 dpkg-dev retitle dpkg-shlibdeps: Should blacklist __aeabi_unwind_cpp_pr1@GCC_3.5 thanks On Mon, 2012-06-11 at 20:16:51 +0200, Bernhard R. Link wrote: > Package: gcc-4.6 > Version: 4.6.2-6 > > Some large number of packages (I'd guess around 700 +/- 200 source packages) > generates

Bug#676558: gcc-4.6: Incorrect assembly code generated for loop over char ** in named sections

2012-06-12 Thread Chris
On 12/06/2012 7:40 AM, Matthias Klose wrote: [...] please could you recheck with 4.7 from unstable? I just installed unstable/sid and tested against gcc 4.7.0-13. The bug is also present in this version. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "uns

Bug#677285: libffi: missing symbol files on ppc64

2012-06-12 Thread Matthias Klose
On 12.06.2012 23:33, Aurelien Jarno wrote: > Source: libffi > Version: 3.0.10-3 > Severity: normal > Tags: patch > > libffi version 3.0.10-3 misses symbols file for ppc64. Please find them > attached. please could you update this for 3.0.11? thanks, Matthias -- To UNSUBSCRIBE, email to debia

Bug#677285: libffi: missing symbol files on ppc64

2012-06-12 Thread Aurelien Jarno
Source: libffi Version: 3.0.10-3 Severity: normal Tags: patch libffi version 3.0.10-3 misses symbols file for ppc64. Please find them attached. -- System Information: Debian Release: wheezy/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: ppc64 Kern

Bug#676558: gcc-4.6: Incorrect assembly code generated for loop over char ** in named sections

2012-06-12 Thread Chris
On 12/06/2012 7:40 AM, Matthias Klose wrote: [...] please could you recheck with 4.7 from unstable? I did not get 4.7 from unstable installed, so I checked against 4.7 from testing instead [gcc version 4.7.0 (Debian 4.7.0-8)]. I found that version 4.7.0-8 has this bug too. -- To UNSUBSCR

What do you think about unscheduled meetings?)

2012-06-12 Thread Obdulia Slavin
How r u doing gorgeous! It is Obdulia. If you are interested in spending unforgettable time in a company of smart, sex appeal girl then I am right before u! I felt in love with your pictures and so decided to send this mail! I'm thinking that u would not stay calm after staring at mine too. So

gcc-4.7_4.7.0-13_amd64.changes ACCEPTED into unstable

2012-06-12 Thread Debian FTP Masters
++6_4.7.0-13_amd64.deb Changes: gcc-4.7 (4.7.0-13) unstable; urgency=low . * Update to SVN 20120612 (r188457) from the gcc-4_7-branch. - Fix PR c++/53602 (LP: #1007616). . * Document the changed ssp-buffer-size default in Ubuntu 10.10 and later (Kees Cook). LP: #990141. * Fix PR c

Processing of gcc-4.7_4.7.0-13_amd64.changes

2012-06-12 Thread Debian FTP Masters
gcc-4.7_4.7.0-13_amd64.changes uploaded successfully to localhost along with the files: gcc-4.7_4.7.0-13.dsc gcc-4.7_4.7.0-13.diff.gz gcc-4.7-source_4.7.0-13_all.deb libstdc++6-4.7-doc_4.7.0-13_all.deb gcc-4.7-locales_4.7.0-13_all.deb gcc-4.7-base_4.7.0-13_amd64.deb libgcc1_4.7.0-13_a

Bug#675516: marked as done (gcc-4.7: Building cross-compiler fails because of wrongly-named man pages)

2012-06-12 Thread Debian Bug Tracking System
- GNU Standard C++ Library v3 (documentation files) libstdc++6-4.7-pic - GNU Standard C++ Library v3 (shared library subset kit) Closes: 675511 675516 676729 Changes: gcc-4.7 (4.7.0-13) unstable; urgency=low . * Update to SVN 20120612 (r188457) from the gcc-4_7-branch. -

Bug#675511: marked as done (gcc-4.7: Please drop dpkg-cross build-dependency when building cross-compilers)

2012-06-12 Thread Debian Bug Tracking System
les) libstdc++6-4.7-doc - GNU Standard C++ Library v3 (documentation files) libstdc++6-4.7-pic - GNU Standard C++ Library v3 (shared library subset kit) Closes: 675511 675516 676729 Changes: gcc-4.7 (4.7.0-13) unstable; urgency=low . * Update to SVN 20120612 (r188457) from the gcc-4_7-bran

Results for 4.7.0 (Debian 4.7.0-13) testsuite on x86_64-pc-linux-gnu

2012-06-12 Thread Matthias Klose
multiple precision floating-point computation developers tools ii libppl0.11-dev:amd64 0.11.2-6 Parma Polyhedra Library (development) svn-updates: updates from the 4.7 branch upto 20120612 (r188457). gcc-gfdl-build: Build a dummy s-tm-te

Bug#676421: gcc-4.7: cross-compiler wants /usr/$triplet/include/ instead of /usr/include/$triplet/

2012-06-12 Thread Matthias Klose
On 06.06.2012 22:18, Adam Borowski wrote: > Package: gcc-4.7 > Version: 4.7.0-11 > Severity: normal > > Hi! > > Building a cross-compiler fails with: > .- > The directory that should contain system headers does not exist: > /usr/arm-linux-gnueabi/include > `- this is the layout used by

Processed: reassign to gcc

2012-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 675026 gcc Bug #675026 [gcc-4.7] gcc-4.7: Debian README file is not accurate Bug reassigned from package 'gcc-4.7' to 'gcc'. No longer marked as found in versions gcc-4.7/4.7.0-8. Ignoring request to alter fixed versions of bug #675026 to

Processed: Re: Bug#676569: gcc-4.7: -nostdlib broken, multiarch library path always added

2012-06-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 676569 normal Bug #676569 [gcc-4.7] gcc-4.7: -nostdlib broken, multiarch library path always added Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 676569: http://b

Bug#676558: gcc-4.6: Incorrect assembly code generated for loop over char ** in named sections

2012-06-12 Thread Matthias Klose
On 07.06.2012 21:11, Christoph Schwarz wrote: > Package: gcc-4.6 > Version: 4.6.3-1 > Severity: normal > > Dear Maintainer, > > I have a program that loops over const char * pointers in named sections. > In this loop, incorrect generated assembly code causes wrong output, e.g. > it outputs (null)

Bug#676569: gcc-4.7: -nostdlib broken, multiarch library path always added

2012-06-12 Thread Matthias Klose
severity 676569 normal thanks -nostdlib doesn't say anything about discarding the -L flags. Did this change with 4.7? On 07.06.2012 22:14, Thorsten Glaser wrote: > Package: gcc-4.7 > Version: 4.7.0-12 > Severity: serious > Justification: breaks unrelated software > > The following scenario is br

Bug#677139: gcc-4.6: unresolved symbol __aeabi_unwind_cpp_pr1@GCC_3.5

2012-06-12 Thread Matthias Klose
Raphael, should dpkg-shlibdeps behave differently about these? I can't see anything wrong on the GCC side. On 11.06.2012 20:16, Bernhard R. Link wrote: > Package: gcc-4.6 > Version: 4.6.2-6 > > Some large number of packages (I'd guess around 700 +/- 200 source packages) > generates on armel and a

Bug#618351: gcc-doc: Still depends on gcc-4.4-doc after the move to 4.5.

2012-06-12 Thread Matthias Klose
On 11.06.2012 00:57, Axel Beckert wrote: > Hi Russ, > > Russ Allbery wrote: We're now at gcc 4.7 for most architectures, the freeze is close and gcc-doc still depends on gcc-4.4-doc. >> >>> ... because there doesn't seem to exist any gcc-4.x-doc package with >>> x >= 5. *puzzled* >> >> I