This is the mail archive of the
mailing list for the GCC project.
Re: Linking with libgomp (ia64-hp-hpux11.23)
- From: Steve Ellcey <sje at cup dot hp dot com>
- To: rth at redhat dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 7 Mar 2006 15:13:24 -0800 (PST)
- Subject: Re: Linking with libgomp (ia64-hp-hpux11.23)
> From: Richard Henderson <firstname.lastname@example.org>
> On Mon, Mar 06, 2006 at 11:32:01AM -0800, Steve Ellcey wrote:
> > | ld: (Warning) Symbol "__udivsi3" is not exported but is imported by a shared library
> > | ld: (Warning) Symbol "__divsi3" is not exported but is imported by a shared library
> > | 2 warnings.
> Are these being referenced from libgomp? If so, why weren't they
> resolved when linking libgomp? Otherwise we need more info.
They are being referenced from libgomp. libstdc++ and libgfortran also
generate references to these routines and I don't get errors when
compiling with C++ or Fortran.
OK, I finally figured out part of this, when I compile with C++ or
Fortran, I get -lgcc_s on the link line. When I compile with -fopenmp I
do not get -lgcc_s on the link line. If I add it to the compile
directly or via -shared-libgcc then the warnings go away.
Not sure how to do that automatically yet.
> > Notice that the -lgomp comes in front of the -L flags. With the HP
> > linker this means that those directories will not be searched for
> > libgomp. If I move the -lgomp to after the -L options then I find
> > libgomp.
> It could well be that the libgomp_link spec is in the wrong place.
Yes, I figured this part out and will submit a patch shortly, but it
does not fix the first problem.