Hi,
Using native gcc compiler from x86_64 RHEL6.6 ... and trying to build 4.9.2
with a small footprint, only care about c and c++ languages... I tried to
follow the instructions in the installation regarding BOOT_CFLAGS,
CFLAGS_FOR_TARGET, STAGE1_TFLAGS ...
in my shell script I have:
../
On 12 April 2015 at 21:10, Ricardo Telichevesky wrote:
> I don't
> need to debug the compiler or any of the libraries at all, but is there any
> danger in getting rid of the -g flags?
There's no danger, you just won't be able to debug anything.
Wouldn't it be easier to just run strip on the final
Snapshot gcc-6-20150412 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20150412/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
The first release candidate for GCC 5.1 is available from
ftp://gcc.gnu.org/pub/gcc/snapshots/5.1.0-RC-20150412
and shortly its mirrors. It has been generated from SVN revision 222032.
I have so far bootstrapped and tested the release candidate on
x86_64-linux and i686-linux. Please test it
I see trunk is bumped to Version 6 now. Are we in Stage 1?
Jerry
Status
==
We have reached zero P1 regressions over the weekend (and < 100 important
regressions) and the branches/gcc-5-branch has been created last night
and GCC 5.1-rc1 built and announced.
The branch is now frozen for blocking regressions and documentation
fixes only, all changes to the bra
