On 03/05/2012 10:12 AM, Richard Guenther wrote:
On Sat, 3 Mar 2012, Ralf Corsepius wrote:
On 03/03/2012 02:58 PM, Richard Guenther wrote:
On Sat, Mar 3, 2012 at 11:17 AM, Ralf Corsepius
<ralf.corsep...@rtems.org> wrote:
On 03/02/2012 02:44 PM, Richard Guenther wrote:
GCC 4.7.0 Release Candidate available from gcc.gnu.org
The first release candidate for GCC 4.7.0 is available from
ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
and shortly its mirrors. It has been generated from SVN revision
184777.
I have so far bootstrapped and tested the release candidate on
x86_64-linux. Please test it and report any issues to bugzilla.
If all goes well, I'd like to release 4.7.0 in about three weeks.
Trying to cross-build for sparc-rtems4.11 rpms fails with this:
error: Installed (but unpackaged) file(s) found:
/opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ar
/opt/rtems-4.11/bin/sparc-rtems4.11-gcc-nm
/opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ranlib
/opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ar
/opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-nm
/opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ranlib
Are these<target>-gcc-{ar,nm,ranlib} really supposed to be
installed? Why? The rationale escapes me.
<target>-<target>-gcc-{ar,nm,ranlib} surely is not correct.
Wasn't that fixed? ...
Dunno, I used your tarball ;)
In any case, please file a bugreport.
Will do so, ASAP.
Btw, if you can help track down what goes wrong with the
gcc/Makefile.in:install-gcc-ar rule that would be helpful.
I think the bug I remember was about Go language binaries.
Correct, go had a similar issue until recently
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48410) and C++ also had it
a while (several years?) ago.
Ralf
