Am 17.11.2017 um 04:07 schrieb Helmut K. C. Tessarek:
On 2017-11-15 19:12, Rainer Jung wrote:
IMHO there is no clean and easy workaround but for now it should be
acceptable to set your LIBS environment variable to "-ldl" before
running configure.
Yep, the following worked:
LIBS=-ldl ./configu
On 2017-11-15 19:12, Rainer Jung wrote:
> IMHO there is no clean and easy workaround but for now it should be
> acceptable to set your LIBS environment variable to "-ldl" before
> running configure.
Yep, the following worked:
LIBS=-ldl ./configure --prefix=/usr/local/apr-util
--with-apr=/usr/loca
On 2017-11-15 19:19, Rainer Jung wrote:
>
> objdump -p /usr/local/lib/libcrypto.so
>
> By the way: most people use "ldd", but ldd follows the whole treee of
> dependencies. With objdump you can see more unfiltered, what you library
> really wants.
ldd -v or readelf -d are also pretty useful
I'll set the LIBS var and test it again later this evening.
On 2017-11-15 19:12, Rainer Jung wrote:
> IMHO there is no clean and easy workaround but for now it should be
> acceptable to set your LIBS environment variable to "-ldl" before
> running configure. Please don' give up if this still fails
Agreed. Seems we aren't correctly digging into pkgconfig or similar.
On Nov 15, 2017 6:12 PM, "Rainer Jung" wrote:
Am 15.11.2017 um 22:02 schrieb Helmut K. C. Tessarek:
> On 2017-11-15 03:53, Rainer Jung wrote:
>
>> Could you please provide the config.log that you get from that variant?
>> We
Too late to write error free mails:
Am 16.11.2017 um 01:12 schrieb Rainer Jung:
On Linux you can use "objdump" to look at dependencies of libraries, so
for instance
objdump /usr/local/lib/libcrypto.so
should have been:
objdump -p /usr/local/lib/libcrypto.so
By the way: most people use "ldd
Mini post scriptum: I meant "dl" library, not "ld" library (flag -ldl).
Am 15.11.2017 um 22:02 schrieb Helmut K. C. Tessarek:
On 2017-11-15 03:53, Rainer Jung wrote:
Could you please provide the config.log that you get from that variant?
We should be able from that to see where and why configure fails.
I have attached both config.log files in my first original pos
On 2017-11-15 03:53, Rainer Jung wrote:
> Could you please provide the config.log that you get from that variant?
> We should be able from that to see where and why configure fails.
I have attached both config.log files in my first original post:
./configure --prefix=/usr/local/apr-util --with-ap
Am 15.11.2017 um 07:55 schrieb Helmut K. C. Tessarek:
On 2017-11-15 01:17, William A Rowe Jr wrote:
There is NO way for autocrud to know the messes in your build environment.
One thought, although we go to effort to strip away other includes and
libs during the additive phase, it is possible yo
On 2017-11-15 01:17, William A Rowe Jr wrote:
> There is NO way for autocrud to know the messes in your build environment.
>
> One thought, although we go to effort to strip away other includes and
> libs during the additive phase, it is possible your prior package --with
> tag helped resolve open
On 2017-11-15 01:17, William A Rowe Jr wrote:
> But really, what you are describing makes no sense. You might obtain
> more help by starting with a description of your OS and installed system
> packages vis a vie OpenSSL an so on. None of us enjoy guessing games.
I'm using Fedora 20, although I ne
There is NO way for autocrud to know the messes in your build environment.
One thought, although we go to effort to strip away other includes and libs
during the additive phase, it is possible your prior package --with tag
helped resolve openssl's path.
But really, what you are describing makes n
On 2017-11-14 10:55, William A Rowe Jr wrote:
> Then in your second experiment, you were simply building against
> the system openssl (-dev[el]) package.
Which also makes no sense, since the output showed something different.
But this pretty much confirms there's a bug in configure, right?
I sho
Then in your second experiment, you were simply building against
the system openssl (-dev[el]) package.
On Mon, Nov 13, 2017 at 2:14 PM, Helmut K. C. Tessarek
wrote:
> On 2017-11-13 12:25, William A Rowe Jr wrote:
>> But does /usr/local/ssl/lib/include exist? If it does, that's just weird.
>
> N
On 2017-11-13 12:25, William A Rowe Jr wrote:
> But does /usr/local/ssl/lib/include exist? If it does, that's just weird.
No, /usr/local/ssl/lib/include does not exist either.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8
On Sun, Nov 12, 2017 at 7:47 PM, Helmut K. C. Tessarek
wrote:
> ./configure --prefix=/usr/local/apr-util --with-apr=/usr/local/apr
> --with-crypto --with-openssl=/usr/local/ssl
>
>
> adding "-I/usr/local/ssl/include" to CPPFLAGS
> setting LDFLAGS to "-L/usr/local/ssl/lib "
> configure: checki
./configure --prefix=/usr/local/apr-util --with-apr=/usr/local/apr
--with-crypto --with-openssl=/usr/local/ssl
adding "-I/usr/local/ssl/include" to CPPFLAGS
setting LDFLAGS to "-L/usr/local/ssl/lib "
configure: checking for openssl in /usr/local/ssl
checking openssl/x509.h usability... yes
ch
18 matches
Mail list logo