[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wget2 | `./configure --with-openssl=yes` fails with linker error (#5
From: |
@rockdaboot |
Subject: |
Re: wget2 | `./configure --with-openssl=yes` fails with linker error (#595) |
Date: |
Sat, 23 Apr 2022 19:25:35 +0000 |
Tim Rühsen commented:
Looks like there is a clash. We use the gnulib modules `crypto/md5` etc. They
set
```
LIB_CRYPTO = -lcrypto
```
used in `Makefile`.
We only want this if no other md5_* implementation exists.
Since recently we have to link with the whole gnulib library (see
-Wl,--whole-archive in the linker command). I once created a patch for libtool
to avoid this, but someone wanted to remove that so that `slibtool` can be used
as a drop-in replcement for libtool. While `slibtool` is of no big interest to
me, the opportunity to get rid of the libtool patch convinced me. Maybe that
was a bad idea !?
We have to decide what to do:
- revert the changes and re-introduce the libtool patch
- drop the crypto modules from bootstrap.conf and don't provide hash algorithms
in case no TLS or crypto library is available
- find another fix or work-around
While we tried to support all kinds of combinations in the past, we can
possible simplify the build process and remove the --with-openssl code
completely. And also remove the gnulib crypto / hash fallback modules from
bootstrap.conf (second option in the list). WDYT ?
--
Reply to this email directly or view it on GitLab:
https://gitlab.com/gnuwget/wget2/-/issues/595#note_921793172
You're receiving this email because of your account on gitlab.com.