-7_amd64.deb
libstdc++6-4.6-doc_4.6.3-7_all.deb
to main/g/gcc-4.6/libstdc++6-4.6-doc_4.6.3-7_all.deb
libstdc++6-4.6-pic_4.6.3-7_amd64.deb
to main/g/gcc-4.6/libstdc++6-4.6-pic_4.6.3-7_amd64.deb
Changes:
gcc-4.6 (4.6.3-7) unstable; urgency=low
.
* Update to SVN 20120528 (r187930) from the gcc
gcc-4.6_4.6.3-7_amd64.changes uploaded successfully to localhost
along with the files:
gcc-4.6_4.6.3-7.dsc
gcc-4.6_4.6.3-7.diff.gz
gcc-4.6-source_4.6.3-7_all.deb
libstdc++6-4.6-doc_4.6.3-7_all.deb
gcc-4.6-locales_4.6.3-7_all.deb
gcc-4.6-base_4.6.3-7_amd64.deb
cpp-4.6_4.6.3-7_amd64.deb
3.1.0-5
multiple precision floating-point computation developers
tools
ii libppl0.11-dev:amd640.11.2-6
Parma Polyhedra Library (development)
svn-updates:
updates from the 4.7 branch up
#
# bts-link upstream status pull for source package gcc-4.7
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #673749 (http://bugs.debian.org/673749)
# Bug title: g++-4.7: gcc47 generates buggy co
++6_4.7.0-10_amd64.deb
Changes:
gcc-4.7 (4.7.0-10) unstable; urgency=low
.
* Update to SVN 20120528 (r187927) from the gcc-4_7-branch.
- Fix PR rtl-optimization/52528, PR lto/52178, PR target/53435,
PR ada/52362, PR target/53385, PR middle-end/53460,
PR tree-optimization/53465
gcc-4.7_4.7.0-10_amd64.changes uploaded successfully to localhost
along with the files:
gcc-4.7_4.7.0-10.dsc
gcc-4.7_4.7.0-10.diff.gz
gcc-4.7-source_4.7.0-10_all.deb
libstdc++6-4.7-doc_4.7.0-10_all.deb
gcc-4.7-locales_4.7.0-10_all.deb
gcc-4.7-base_4.7.0-10_amd64.deb
libgcc1_4.7.0-10_a
files)
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: 674830
Changes:
gcc-4.7 (4.7.0-10) unstable; urgency=low
.
* Update to SVN 20120528 (r187927) from the gcc-4_7-branch.
- Fix PR r
Hi,
> GCC 4.7 was blamed for this, but now I'm looking back and wondering if
> that was fair, and if it was such a bad thing all of this happened.
>
> The solution in gpsd VCS seems to have been applying a rather large
> changeset, fixing things from Coverity static analysis, potential buffer
> o
On 20/05/12 22:16, Bernd Zeimetz wrote:
>> After rebuilding gpsd today I had to realize that the stack protector makes
>> one
>> of the tools segfault since it was built with gcc 4.7. If gpsd wouldn't ship
>
> Actually I'm not exactly sure if it is the stack protectors' fault, but it is
> definit
9 matches
Mail list logo