This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/26889] libfortran build fails with: object requires TLS, but TLS failed to initialize
- From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Mar 2006 07:46:22 -0000
- Subject: [Bug fortran/26889] libfortran build fails with: object requires TLS, but TLS failed to initialize
- References: <bug-26889-10100@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #17 from ebotcazou at gcc dot gnu dot org 2006-03-28 07:46 -------
> "make" worked fine with gcc-3.4.x, gcc-3.3.x, gcc-2.9x etc.
Yes, but it's wrong up to (and including) 4.1.x. We only guarantee that the
compiler correctly compiles itself ("bootstraps"), not that it is correctly
compiled by other compilers at random optimization levels.
> Is this a solaris specific issue?
No, this has always been documented:
@section Building a native compiler
For a native build issue the command @samp{make bootstrap}. This
will build the entire GCC system, which includes the following steps:
@itemize @bullet
@item
Build host tools necessary to build the compiler such as texinfo, bison,
gperf.
@item
Build target tools for use by the compiler such as binutils (bfd,
binutils, gas, gprof, ld, and opcodes)
if they have been individually linked
or moved into the top level GCC source tree before configuring.
@item
Perform a 3-stage bootstrap of the compiler.
@item
Perform a comparison test of the stage2 and stage3 compilers.
@item
Build runtime libraries using the stage3 compiler from the previous step.
@end itemize
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26889