This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] Fix PR 13334, document bootstrap failures with non-standard CFLAGS

The problem here is that if a non-standard CFLAGS is used and bootstrap
failure in libiberty due to the used CFLAGS causing a warning with the
new compiler always like options being deprecated.

This patch documents this problem and fixes the PR which was for the
documentation of the problem.

Andrew Pinski

	* doc/install.texi: Document non-standard CFLAGS and bootstrap
	failures and warnings.

Index: install.texi
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.280
diff -u -p -r1.280 install.texi
--- install.texi	13 May 2004 06:40:25 -0000	1.280
+++ install.texi	28 May 2004 13:09:45 -0000
@@ -1460,6 +1460,12 @@ around this, by choosing @code{BOOT_CFLA
 stage1 compiler that were miscompiled, or by using @samp{make
 bootstrap4} to increase the number of stages of bootstrap.

+Note that using a non-standard @code{CFLAGS} can cause bootstrap to
+fail in @file{libiberty} if the @code{CFLAGS} causes a warning
+with the new compiler. For an example using @samp{-O2 -g -mcpu=i686}
+on @code{i686-pc-linux-gnu} will cause bootstrap failure as @code{-mcpu=}
+is deprecated in 3.4.0 and above.
If you used the flag @option{--enable-languages=@dots{}} to restrict
the compilers to be built, only those you've actually enabled will be
built. This will of course only build those runtime libraries, for

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]