It's been such a long time since I've poked at this, but running nm
against /usr/lib/libc.a supports the notion that it's just a dummy.
nm -a libc.a
__lib__.o:
0 D @@DOPLNK
0 U @@XINIT@
0 D @STATIC
0 U CEESG003
0 U CEESTART
0 T __lib__very_unlikely_to_be_referenced_external_function
0 U printf
0 t private
There is no other .so or .dll form of libc that I've found so far. I try
to dust off some of the cobwebs and remember where the functions are
hiding.
Karl, It may help if you can you supply the names of some of the functions
you are having problems with.
Regards,
John Goodyear
z Systems Analytics zChampion
WSC zGrowth and z Systems Applied Technologies
Gaithersburg, MD
[email protected]
bulk88 <[email protected]> wrote on 10/06/2015 10:03:13 PM:
> From: bulk88 <[email protected]>
> To: Karl Williamson <[email protected]>
> Cc: "[email protected]" <[email protected]>, Perl5 Porters <perl5-
> [email protected]>, Jarkko Hietaniemi <[email protected]>, John Goodyear/
> Gaithersburg/IBM@IBMUS
> Date: 10/06/2015 10:03 PM
> Subject: Re: z/OS and libc
>
> Karl Williamson wrote:
> > I'm working on continuing to port perl5 to z/OS. One test that is
> > failing is beyond my knowledge level. The Dynaloader module has a
> > function dl_findfile() which looks for libraries in the path. It is
> > expecting to find libc at least, but is finding nothing.
> >
> > This test does not work on several platforms, even some Unix-like ones,
> > and my guess is it doesn't work on z/OS either. But I am hoping
someone
> > can give me more information.
> >
> > One of the comments in the perl source says:
> > # On OS/390, libc.a doesn't really hold anything at all,
> >
> > And that makes me think that looking for it (and perhaps any Unix-y
> > library) is futile.
>
> Verify that accuracy of that comment. Use nm to dump all the c symbols
> in libc.a. Does libc.a look like libc or not?
>
> Config.pm and Configure have a "libc" var that is set through some logic
> in Configure.
>
> Porting/Glossary says
> ----------------------------------------------------------
> libc (libc.U):
> This variable contains the location of the C library.
> ----------------------------------------------------------
>
> I would guess one purpose of that config var is automatically look for c
> symbols with nm if you aren't doing test compiles. I'll point out
> t/porting/libperl.t exists.
>
