Very Computer

I need to create a shared library that exports only two (of
its many) symbols to programs that link with it. Under HP-UX,
this can be done with the "+e" option to ld, but how is this
possible with the Solaris ld?

Thanks for any hint in advance,

Lutz Vieweg

--
 Lutz Vieweg

 Kaiserstrasse 65          | Phone: +49-69-236929
 60329 Frankfurt am Main   | Fax:   +49-69-236930

Quote:> I need to create a shared library that exports only two (of
> its many) symbols to programs that link with it. Under HP-UX,
> this can be done with the "+e" option to ld, but how is this
> possible with the Solaris ld?

cc -M mapfile -h libname.so.1 -o libname.so.1 -G file.o -lc

where mapfile contains:

{
global:
        public_symbol1;
        public_symbol2;
local:
        *;

Quote:};

---
Bart Smaalders                  Solaris Clustering      SunSoft

http://playground.sun.com/~barts                   2550 Garcia Ave
                                                        Mt View, CA 94043-1100

Quote:> > I need to create a shared library that exports only two (of
> > its many) symbols to programs that link with it. Under HP-UX,
> > this can be done with the "+e" option to ld, but how is this
> > possible with the Solaris ld?

> You'll want to read the Linker and Libraries Manual sections regarding
> mapfiles.  In short:

> cc -M mapfile -h libname.so.1 -o libname.so.1 -G file.o -lc

> where mapfile contains:

> {
> global:
>    public_symbol1;
>    public_symbol2;
> local:
>    *;
> };

> See the answerbook for the details....

In the 2.5 Linker and Libraries Guide (part of the Software Developer
Answerbook) see:

  o     Chapter 2, starting at section `Defining Additional Symbols'
        for an introduction to the new mapfile syntax.

  o     The new Chapter 5 for an overall guide to Versioning - this
        new mapfile syntax allows for establishing internal versions
        (symbol groupings) within a dynamic object.

  o     Appendix B provides a Versioning Cheat Sheet.

Rod.

Regards,

Lutz Vieweg

--
 Lutz Vieweg

 Kaiserstrasse 65          | Phone: +49-69-236929
 60329 Frankfurt am Main   | Fax:   +49-69-236930

Quote:> > > > I need to create a shared library that exports only two (of
> > > > its many) symbols to programs that link with it. Under HP-UX,
> > > > this can be done with the "+e" option to ld, but how is this
> > > > possible with the Solaris ld?

> > This functionality was first made available in Solaris 2.5.

> That's odd, we want to support Solaris 2.4 as well... is there
> any way to make it work under 2.4?

You can build your shared object on 2.5 using this new ld(1) feature
and still use the object on 2.4.

Note, part of this ld(1) technology records an internal version name
to represent the symbol interface you've defined.  If you intend to use
the shared object to link against on 2.4, I'd recommend that you suppress
this internal version name recording:

        cc -G -o libfoo.so.1 -Mmapfile -Wl,-znoversion $(OBJS)

Rod.