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
