Bill Moseley <[EMAIL PROTECTED]> writes:
> I was building our package on a Solaris 2.6 machine and ended up with:
>
> ld: fatal: library -lz: not found
>
> On this machine libz is in /usr/local/lib.
>
> Running truss shows:
>
> open("/usr/ccs/lib/libz.so", O_RDONLY) Err#2 ENOENT
> open("/usr/ccs/lib/libz.a", O_RDONLY) Err#2 ENOENT
> open("/usr/lib/libz.so", O_RDONLY) Err#2 ENOENT
> open("/usr/lib/libz.a", O_RDONLY) Err#2 ENOENT
> ld: write(2, " l d : ", 4) = 4
> fatal: write(2, " f a t a l : ", 7) = 7
> library -lwrite(2, " l i b r a r y - l", 10) = 10
> zwrite(2, " z", 1) = 1
> : not foundwrite(2, " : n o t f o u n d", 11) = 11
>
> So it's not looking in /usr/local/lib.
>
> So my question is why is configure finding libz?
I can only guess that this happens because the compiler/linker and/or
flags are different between the link that succeeds at configure-time
and the one that fails at make-time.
You'll have to look through config.log to find the actual command that
worked.
