gcc: "cannot find -lz cannot find -lcrypto"

Message

LeeJunFan · Post by **LeeJunFan** » Thu Oct 31, 2013 9:42 am

Hello,

I'm having a hard time getting some 'old' software compiled. To cut a long story short. GCC says "cannot find -lz" and "cannot find -lcrypto".

This happened to me before, but as far as I know, that was simply solved by emerging libcrypto.
But not anymore!

I re-emerged libcrypto++ (where is the normal libcrypto?),
I re-emerged libtool,
I re-emerged gcc,
I emerge zlib,

gcc-config is set to: x86_64-pc-linux-gnu-4.7.3

I added zlib to the USE-variables in /etc/portage/make.conf.

So far no success.

Anybody an idea how to solve this issue?

Thanks in advance...

eyoung100 · Post by **eyoung100** » Thu Oct 31, 2013 3:10 pm

Code: Select all

emerge dev-libs/openssl <-- libcrypto
emerge zlib
emerge -uDN world

LeeJunFan · Post by **LeeJunFan** » Thu Oct 31, 2013 4:05 pm

Nope

Although I didn't say. Tried this already.
Now tried it again: Same error: "cannot find -lz" and "cannot find -lcrypto"

eyoung100 · Post by **eyoung100** » Thu Oct 31, 2013 4:14 pm

LeeJunFan wrote:Nope

Although I didn't say. Tried this already.
Now tried it again: Same error: "cannot find -lz" and "cannot find -lcrypto"

What is the old software

If you emerge gentoolkit, it contains equery:

Code: Select all

equery belongs /usr/lib/libcrypto.so*
dev-libs/openssl-1.0.1e-r1(/usr/lib64/libcrypto.so.1.0.0)
equery belongs /usr/lib/libz*
sys-libs/zlib-1.2.7 (/usr/lib64/libz.a)
sys-libs/zlib1.2.7(/usr/lib64/libz.so)

You may need to manually edit the software's configure script to point to the new library location if the old software is not in portage

VoidMage · Post by **VoidMage** » Thu Oct 31, 2013 4:46 pm

How about putting a build log with such failure in a pastebin ?

LeeJunFan · Post by **LeeJunFan** » Fri Nov 01, 2013 5:45 pm

@eyoung100

The software that I'm trying to compile is rdd-copy, version 2.0.7.
(http://sourceforge.net/projects/rdd/files/rdd/2.0.7/)

Then the equery-output:

Code: Select all

# equery belongs /usr/lib/libcrypto.so* 
 * Searching for /usr/lib/libcrypto.so,/usr/lib/libcrypto.so.1.0.0 ... 
dev-libs/openssl-1.0.1e-r1 (/usr/lib64/libcrypto.so.1.0.0)

# equery belongs /usr/lib/libz* 
 * Searching for /usr/lib/libz.so,/usr/lib/libzip.so,/usr/lib/libzip.so.2,/usr/lib/libzip.so.2.1.0 ... 
dev-libs/libzip-0.11.1 (/usr/lib64/libzip.so.2.1.0)
sys-libs/zlib-1.2.7 (/usr/lib64/libz.so)

BTW: The last line (sys-libs/zlib-1.2.7 (/usr/lib64/libz.so)) wasn't there in first instance. I emerged libzip. But unfortunately that also didn't solve my problem.

Still the same message after make:

Code: Select all

...
make[2]: Entering directory `/install/rdd-2.0.7/src'
gcc -pedantic -Wno-long-long -g3 -Wall -Wmissing-prototypes -g -O2 -static  -o rdd-copy  rddcopy.o librdd.a -lm -lz -lcrypto 
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lz
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lcrypto
...

@VoidMage

How about putting a build log with such failure in a pastebin ?

I'm sorry. I don't really know what you mean by that.

Do you mean the whole output of make?

eyoung100 · Post by **eyoung100** » Fri Nov 01, 2013 6:09 pm

Why are you compiling from a tarball, when the package exists in portage

Code: Select all

emerge -av app-forensics/rdd
[ebuild N   ]sys-apps-fuse-2.9.2 USE="-static-libs" 547 kB
[ebuild N   ]app-forensics/libewf-20130416:0/2 USE="fuse ssl unicode uuid zlib -debug -ewf -rawio -static-libs" 1,923 kB
[ebuild N  ~]app-forensics/rdd-3.0.4-r1 USE="-debug -doc" 5,759 kB

Total: 3 Packages (3 new), Size of downloads: 8,228 kB

The following keyword changes are necessary to proceed:
(see "package.accept_keywords" in the portage(5) man page for more details)
#required by app-forensics/rdd (argument)
=app-forensics/rdd-3.0.4-r1 ~amd64
<snip>

LeeJunFan · Post by **LeeJunFan** » Fri Nov 01, 2013 8:28 pm

That's version 3.0.4-r1.
And I specifically need version 2.0.7.

BTW: I did check if rdd-3.0.4-r1 emerged correctly. And yes it did.

eyoung100 · Post by **eyoung100** » Fri Nov 01, 2013 9:16 pm

The error your having maybe why 2.0.7 is no longer in the tree...
libcrypto-0.9.8 was merged into openssl awhile ago, which is why the linker cannot find the file. The linker is looking for libcrypt as if it weren't merged w/ openssl. Same thing goes for -lz

Why do you need 2.0.7

LeeJunFan · Post by **LeeJunFan** » Fri Nov 01, 2013 10:06 pm

That's a long story.

I'm gonna try to explain briefly.
Basically it's for compatibility reasons. The syntax for calling rdd 3 differs quite a lot from calling rdd 2.
And since a part of our software is a wrapper around version 2, it stopped functioning with version 3.

At the end, it's not the end of the world; I do have a compiled version, 64bit, available, that is already working on my Gentoo machine.
But I just can't stand it, that it doesn't seem to compile on this platform anymore.

I remember those days, that it was the other way around: When CentOS, or even Debian, had troubles (by default) getting stuff compiled; It was always Gentoo that helped us out.

I'm getting old...

Thanks anyways everybody!

VoidMage · Post by **VoidMage** » Sat Nov 02, 2013 1:11 am

Going by the line from the build log, you've quoted, for whatever silly reason that rdd-2.0.7 thing wants static libz and libcrypto.
Probably the sanest solution is to find the switch in the build system for that or to patch the dumb thing out.

LeeJunFan · Post by **LeeJunFan** » Sat Nov 02, 2013 10:18 am

VoidMage wrote:Going by the line from the build log, you've quoted, for whatever silly reason that rdd-2.0.7 thing wants static libz and libcrypto.
Probably the sanest solution is to find the switch in the build system for that or to patch the dumb thing out.

But I guess, if I do want to patch this, I have to that in the Makefile or the configure-script right?
Too bad. That is a little bit too far away of my abilities.

lagalopex · Post by **lagalopex** » Sat Nov 02, 2013 10:51 am

VoidMage wrote:Going by the line from the build log, you've quoted, for whatever silly reason that rdd-2.0.7 thing wants static libz and libcrypto.

Both libs (openssl and zlib) do have a "static-libs" use flags...

VoidMage · Post by **VoidMage** » Sat Nov 02, 2013 3:10 pm

lagalopex wrote:
VoidMage wrote:Going by the line from the build log, you've quoted, for whatever silly reason that rdd-2.0.7 thing wants static libz and libcrypto.
Both libs (openssl and zlib) do have a "static-libs" use flags...

Likely so, but changing that setting in the build system is the better solution, IMHO.