This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: What happens when you --enable libgomp but not --enable-languages=fortran?
- From: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- To: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- Cc: gcc at gcc dot gnu dot org, Fortran List <fortran at gcc dot gnu dot org>
- Date: Mon, 10 Aug 2009 22:55:12 +0200
- Subject: Re: What happens when you --enable libgomp but not --enable-languages=fortran?
- References: <4A7957C7.6050505@gmail.com>
Hello Dave,
* Dave Korn wrote on Wed, Aug 05, 2009 at 11:58:31AM CEST:
> > libtool: link: /gnu/gcc/obj-patched-gnat2/./gcc/xgcc -B/gnu/gcc/obj-patched-gnat
> > 2/./gcc/ -B/opt/gcc-tools/i686-pc-cygwin/bin/ -B/opt/gcc-tools/i686-pc-cygwin/li
> > b/ -isystem /opt/gcc-tools/i686-pc-cygwin/include -isystem /opt/gcc-tools/i686-p
> > c-cygwin/sys-include -shared .libs/alloc.o .libs/barrier.o .libs/critical.o
[...]
> > o .libs/bar.o .libs/ptrlock.o .libs/time.o .libs/fortran.o .libs/affinity.o -
> > pthread -Wl,-O1 -o .libs/libgomp-1.dll -Wl,--enable-auto-image-base -Xlinker -
> > -out-implib -Xlinker .libs/libgomp-1.dll
> > xgcc: unrecognized option '-pthread'
> > Creating library file: .libs/libgomp-1.dll
> > libtool: link: (cd ".libs" && rm -f "libgomp.lib" && ln -s "libgomp-1.dll" "libg
> > omp.lib")
> > libtool: link: /opt/gcc-tools/i686-pc-cygwin/bin/ar rc .libs/libgomp.lib alloc.
> > o barrier.o critical.o env.o error.o iter.o iter_ull.o loop.o loop_ull.o ordered
[...]
> > /opt/gcc-tools/i686-pc-cygwin/bin/ar: .libs/libgomp.lib: File format not recogni
> > zed
> > make[4]: *** [libgomp.la] Error 1
> >
> > $ file i686-pc-cygwin/libgomp/.libs/libgomp.lib
> > i686-pc-cygwin/libgomp/.libs/libgomp.lib: symbolic link to `libgomp-1.dll'
>
> I configured the exact same sandbox yesterday with "--enable-libgomp
> --enable-languages=c,c++,ada,fortran" and it bootstrapped fine. I tried it
> today with libgomp but without fortran, and this happens. I noticed that this
> problem has been observed by someone on the MinGW users list, without much
> resolution. Something must have gone wrong with the libtool configuration
> somehow; there's no such thing as a libgomp.lib (whether symlink to a DLL or
> otherwise) in my previous successful build.
>
> Should I not be surprised that libgomp can't be built without fortran enabled,
> or should I open a PR?
Yes, and Cc: me in the PR, please; thanks.
Cheers,
Ralf