[Bug middle-end/41357] libgomp build fail

["davek at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #31 from davek at gcc dot gnu dot org  2009-09-28 05:48 -------
(In reply to comment #30)
> I still get 
> 
> /bin/sh ./libtool --tag CC   --mode=link /usr/local/src/trunk/objdir/./gcc/xgcc
> -B/usr/local/src/trunk/objdir/./gcc/ -B/usr/local/gnu/i686-pc-cygwin/bin/
> -B/usr/local/gnu/i686-pc-cygwin/lib/ -isystem
> /usr/local/gnu/i686-pc-cygwin/include -isystem
> /usr/local/gnu/i686-pc-cygwin/sys-include    -Wall -Werror -Wc,-pthread -g -O2 
>  -Wl,-O1   -o libgomp.la -version-info 1:0:0  -no-undefined -bindir
> "/usr/local/gnu/bin" -rpath /usr/local/gnu/lib/gcc/i686-pc-cygwin/4.5.0
> alloc.lo barrier.lo critical.lo env.lo error.lo iter.lo iter_ull.lo loop.lo
> loop_ull.lo ordered.lo parallel.lo sections.lo single.lo task.lo team.lo
> work.lo lock.lo mutex.lo proc.lo sem.lo bar.lo ptrlock.lo time.lo fortran.lo
> affinity.lo  
> libtool: link: rm -fr  .libs/libgomp.dll.a
> libtool: link: /usr/local/src/trunk/objdir/./gcc/xgcc
> -B/usr/local/src/trunk/objdir/./gcc/ -B/usr/local/gnu/i686-pc-cygwin/bin/
> -B/usr/local/gnu/i686-pc-cygwin/lib/ -isystem
> /usr/local/gnu/i686-pc-cygwin/include -isystem
> /usr/local/gnu/i686-pc-cygwin/sys-include    -shared  .libs/alloc.o
> .libs/barrier.o .libs/critical.o .libs/env.o .libs/error.o .libs/iter.o
> .libs/iter_ull.o .libs/loop.o .libs/loop_ull.o .libs/ordered.o .libs/parallel.o
> .libs/sections.o .libs/single.o .libs/task.o .libs/team.o .libs/work.o
> .libs/lock.o .libs/mutex.o .libs/proc.o .libs/sem.o .libs/bar.o .libs/ptrlock.o
> .libs/time.o .libs/fortran.o .libs/affinity.o    -pthread -Wl,-O1   -o
> .libs/cyggomp-1.dll -Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker
> .libs/libgomp.dll.a
> xgcc: unrecognized option '-pthread'
> Creating library file:
> .libs/libgomp.dll.a.libs/team.o:team.c:(.debug_info+0x1084): undefined
> reference to `_gomp_tls_data'
> collect2: ld returned 1 exit status
> 
> make[4]: *** [libgomp.la] Error 1

  Yeah, confirmed at r.152230; this bug is not yet fixed.  Note that it's a
different .o file from those mentioned in the original error.  Haven't yet
debugged it to see how it's going wrong.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41357