Hans-Joachim Ehlers wrote:
> FYI:
>
> $ which_fileset libm.a
> /usr/ccs/lib/libm.a bos.adt.libm 5.3.0.0
>
> thus the lilbm.a comes from the bos.adt.libm fileset.
>
> Handy in case the file is installed and you would like to know the package:
>
> $ lslpp -Lc | grep libm # List
FYI:
$ which_fileset libm.a
/usr/ccs/lib/libm.a bos.adt.libm 5.3.0.0
thus the lilbm.a comes from the bos.adt.libm fileset.
Handy in case the file is installed and you would like to know the package:
$ lslpp -Lc | grep libm # List all file in colum format
$ lslpp -wc "*lib
Jim,
libm comes from the glibc-devel package on my SLES 10 linux box. I'm
not sure where it comes from on AIX. I do have it installed on my AIX
machine, but with it being AIX, I'm not sure where to look to find out
how it got there. :)
There's one more problem you might run into - I haven't dug i
John Calcote wrote:
> Jim,
>
> I've checked in a couple of sets of changes that allow AIX to compile
> (reasonably) cleanly, and to not core-dump when executed - my test was
> limited to slptool findscopes, which is an easy test because it
> doesn't rely on network configuration to work correctly
John Calcote wrote:
> Jim,
>
> I've checked in a couple of sets of changes that allow AIX to compile
> (reasonably) cleanly, and to not core-dump when executed - my test was
> limited to slptool findscopes, which is an easy test because it
> doesn't rely on network configuration to work correctly
Jim,
I've checked in a couple of sets of changes that allow AIX to compile
(reasonably) cleanly, and to not core-dump when executed - my test was
limited to slptool findscopes, which is an easy test because it
doesn't rely on network configuration to work correctly.
Unfortunately, I haven't had ti
