Re: I just want to add a .o to the link line

[Thomas Gagne]

It appears to be PIC-created.  For grins I created a .lo link to the .o file
and got around the errors.  Everything appears fine but this isn't a good
workaround for my .am file.  If there isn't, I'll have to include instructions
to create the link before attempting to build the library.

Tom Tromey wrote:

> >>>>> "Thomas" == Thomas Gagne <address@hidden> writes:
>
> Thomas> lib_LTLIBRARIES = libsybapi11.la
> Thomas> libsybapi11_la_SOURCES = gssybpublic.c gssybapi.c gssybcommon.c
> Thomas> libsybapi11_la_LIBADD = $(GEMSTONE)/lib/gciualib.o
>
> You want this to be `$(GEMSTONE)/lib/gciualib.lo'.
> If you can't make that happen then you're in trouble.
> What if the gciualib.o isn't built with pic?  Then it won't work in a
> shared library (roughly).
>
> You could hack around this restriction:
>
>     myobj.lo: $(GEMSTONE)/lib/gciualib.o
>             cp $(GEMSTONE)/lib/gciualib.o myobj.lo
>
>     libsybapi11_la_LIBADD = myobj.lo
>
> This is probably a bad idea.
>
> Tom
>
> _______________________________________________
> Libtool mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/libtool

--
.tom