Your message dated Sat, 03 Mar 2012 10:33:29 +
with message-id
and subject line Bug#584572: fixed in gcc-4.7 4.7.0~rc1-1
has caused the Debian Bug report #584572,
regarding symbol lookup error: undefined symbol
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Sat, 03 Mar 2012 10:33:29 +
with message-id
and subject line Bug#584572: fixed in gcc-4.7 4.7.0~rc1-1
has caused the Debian Bug report #584572,
regarding /usr/lib/libstdc++.so.6: undefined symbol: _ZNSt8messagesIcE2idE,
version GLIBCXX_3.4
to be marked as done.
This means
Your message dated Sat, 03 Mar 2012 10:33:29 +
with message-id
and subject line Bug#651550: fixed in gcc-4.7 4.7.0~rc1-1
has caused the Debian Bug report #651550,
regarding libstdc++6 4.6.1-4 breaks libstdc++6-4.4-dev 4.4.5-8 but doesn't
"conflict" with it
to be marked as done.
This means th
Your message dated Sat, 03 Mar 2012 10:33:29 +
with message-id
and subject line Bug#661118: fixed in gcc-4.7 4.7.0~rc1-1
has caused the Debian Bug report #661118,
regarding libstdc++6: is "Priority: required" but not pseudo-essential
to be marked as done.
This means that you claim that the pr
Your message dated Sat, 03 Mar 2012 10:33:29 +
with message-id
and subject line Bug#661385: fixed in gcc-4.7 4.7.0~rc1-1
has caused the Debian Bug report #661385,
regarding libstdc++6-4.6-dbg: libstdcxx Python package installed in the wrong
place
to be marked as done.
This means that you cla
gcc-4.7_4.7.0~rc1-1_amd64.changes uploaded successfully to localhost
along with the files:
gcc-4.7_4.7.0~rc1-1.dsc
gcc-4.7_4.7.0~rc1-1.tar.gz
gcc-4.7-source_4.7.0~rc1-1_all.deb
libstdc++6-4.7-doc_4.7.0~rc1-1_all.deb
gcc-4.7-locales_4.7.0~rc1-1_all.deb
gcc-4.7-base_4.7.0~rc1-1_amd64.deb
Accepted:
cpp-4.7_4.7.0~rc1-1_amd64.deb
to main/g/gcc-4.7/cpp-4.7_4.7.0~rc1-1_amd64.deb
fixincludes_4.7.0~rc1-1_amd64.deb
to main/g/gcc-4.7/fixincludes_4.7.0~rc1-1_amd64.deb
g++-4.7-multilib_4.7.0~rc1-1_amd64.deb
to main/g/gcc-4.7/g++-4.7-multilib_4.7.0~rc1-1_amd64.deb
g++-4.7_4.7.0~rc1-1_
There are disparities between your recently accepted upload and the
override file for the following file(s):
libstdc++6_4.7.0~rc1-1_amd64.deb: package says priority is important, override
says required.
Please note that a list of new sections were recently added to the
archive: cli-mono, databa
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42611
Bug 42611 depends on bug 42146, which changed state.
Bug 42146 Summary: ICE in tree_low_cst
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42146
What|Old Value |New Value
-
LAST_UPDATED: Obtained from SVN: tags/gcc_4_6_3_release revision 184738
Native configuration is arm-unknown-linux-gnueabi
=== libgomp tests ===
Running target unix
FAIL: libgomp.c++/ctor-3.C -O0 execution test
FAIL: libgomp.c++/ctor-3.C -O1 execution test
FAIL: libgomp.c++/c
LAST_UPDATED: Obtained from SVN: tags/gcc_4_6_3_release revision 184738
Native configuration is arm-unknown-linux-gnueabihf
=== libgomp tests ===
Running target unix
=== libgomp Summary ===
# of expected passes2678
# of unsupported tests 1
LAST_UPDATED: Obtained from SVN: tags/gcc_4_6_3_release revision 184738
Target: i486-linux-gnu
gcc version 4.6.3 (Debian 4.6.3-1)
Native configuration is i486-pc-linux-gnu
=== g++ tests ===
Running target unix
XPASS: g++.dg/uninit-pred-3_b.C (test for excess errors)
UNRESOLVED:
LAST_UPDATED: Obtained from SVN: tags/gcc_4_6_3_release revision 184738
Target: ia64-linux-gnu
gcc version 4.6.3 (Debian 4.6.3-1)
Native configuration is ia64-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/inherit/covariant7.C scan-tree-dump class "48
LAST_UPDATED: Obtained from SVN: tags/gcc_4_6_3_release revision 184738
Target: x86_64-kfreebsd-gnu
gcc version 4.6.3 (Debian 4.6.3-1)
Native configuration is x86_64-pc-kfreebsd-gnu
=== g++ tests ===
Running target unix
XPASS: g++.dg/uninit-pred-3_b.C (test for excess errors)
U
LAST_UPDATED: Obtained from SVN: tags/gcc_4_6_3_release revision 184738
Target: i486-kfreebsd-gnu
gcc version 4.6.3 (Debian 4.6.3-1)
Native configuration is i486-pc-kfreebsd-gnu
=== g++ tests ===
Running target unix
XPASS: g++.dg/uninit-pred-3_b.C (test for excess errors)
UNRES
LAST_UPDATED: Obtained from SVN: branches/gcc-4_7-branch revision 184781
Target: x86_64-linux-gnu
gcc version 4.7.0 20120302 (prerelease) (Debian 4.7.0~rc1-1)
Native configuration is x86_64-pc-linux-gnu
=== g++ tests ===
Running target unix
UNRESOLVED: attribute_plugin.c compil
LAST_UPDATED: Tue Feb 28 20:28:36 UTC 2012 (revision 184640)
Native configuration is arm-unknown-linux-gnueabi
=== boehm-gc tests ===
Running target unix
=== boehm-gc Summary ===
# of expected passes12
# of unsupported tests 1
LAST_UPDATED: Tue Feb 28 20:28:36 UTC 2012 (revision 184640)
Native configuration is arm-unknown-linux-gnueabihf
=== boehm-gc tests ===
Running target unix
=== boehm-gc Summary ===
# of expected passes12
# of unsupported tests 1
LAST_UPDATED: Tue Feb 28 20:28:36 UTC 2012 (revision 184640)
Target: ia64-linux-gnu
gcc version 4.7.0 20120228 (experimental) [trunk revision 184640] (Debian
20120228-1)
=== acats tests ===
FAIL: cb1010a
FAIL: cb1010c
FAIL: cb1010d
=== acats Summary ===
#
Hi Steve et al,
let me share a piece of news and please let me know if that is
possible that the issue was actually actually an alignment issue while
presenting itself as illop? Does alignment also concerns code blocks
and somehow incorrect opcode was read or what was it? sorry for such a
naive
20 matches
Mail list logo
