Bruce Dubbs wrote:
> This is curious because we are using a sed:
>
> sed -i "s:-lcrypto:/usr/lib/libcrypto.a:g" configure
>
> to force a static library. When I leave out the sed, openssl builds
> fine. Looking at the errors above it looks like the libcrypto.a file
> has some calls to load functions dynamically. The
> dl{open,close,error,sym} functions are built as a part of binutils.
> Right now this looks like a problem with openssl's building shared
> libraries.
>
> My next step will be to go back and rebuild openssl without the 'shared'
> parameter and then try building openssh again with the static libcrypto.a.
I rebuilt openssl without the 'shared' parameter and copied libcrypto.a
to /usr/lib. I got the same errors.
I then tried linking in /usr/lib/libdl.a and got a warning about using
this statically and an error about a missing __dl{something}. I then
tried using the dynamic library libdl.so and the build completed.
If we use:
sed -i "s:-lcrypto:/usr/lib/libcrypto.a -ldl:g" configure
openssl will build without error, but that seems to just implement what
we are trying to avoid with the sed in the first place.
As I see it, we can just remove the sed completely or use the one above
with -ldl in it. I'm not sure which is best.
Opinions?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
