Re: wget 1.7 configure errors
Maciej W. Rozycki [EMAIL PROTECTED] writes: On 7 Jun 2001, Hrvoje Niksic wrote: We build with rpath only if the SSL libraries are at a non-standard location, i.e. one not recognized by the system (we first try to build without rpath). In that case, building with rpath or its moral equivalent is the only way to produce a working executable. I think the following patch should solve the problem for platforms libtool supports. Maciej, this is excellent. With this, and possibly an upgrade to libtool 1.4 (but not Autoconf 2.50), we can release Wget 1.7.1.
wget 1.7 configure errors
I said ./configure --with-ssl but the script said it couldn't find ssl libs. They're in the default /usr/local/ssl location. Looking at config.log, I see that gcc is upset, claiming that -rpath is an invalid option. That's right. It's a linker option so gcc should see -Wl,-rpath. If I make that change, then configure finds the ssl libs and the build proceeds. In the midst of trying to debug this, I tried using another gcc by saying CC=/usr/new/bin/gcc ./configure ... This syntax is described in every GNU INSTALL document I've ever seen. Your script does not honor it. Your script really should. Thanks. -- Mars 2001-06-05 20:00:57.973 UTC (JD 2452066.334004) X = -0.302186621, Y = -1.326263232, Z = -0.599968130 (au) X' = 0.014245527, Y' = -0.001339436, Z' = -0.000999401 (au/d)
Re: wget 1.7 configure errors
Quoting tenthumbs ([EMAIL PROTECTED]): I said ./configure --with-ssl but the script said it couldn't find ssl libs. They're in the default /usr/local/ssl location. Looking at config.log, I see that gcc is upset, claiming that -rpath is an invalid option. That's right. It's a linker option so gcc should see -Wl,-rpath. If I make that change, then configure finds the ssl libs and the build proceeds. Yes, the SSL detection is broken on some systems. We are working on a fix. In the midst of trying to debug this, I tried using another gcc by saying CC=/usr/new/bin/gcc ./configure ... This syntax is described in every GNU INSTALL document I've ever seen. Your script does not honor it. Your script really should. Could you provide an example? On my machine, GCC is in /usr/local/bin by default (I'm using the GCC 3.0 development version which has some bugs, so I prevent to keep tow versions of the compiler). In this setup, `CC=/usr/bin/gcc ./configure ... ; make' will build wget with the old GCC 2.95.2 just fine. -- jan +-- Jan Prikryl| vr|vis center for virtual reality and visualisation [EMAIL PROTECTED] | http://www.vrvis.at +--
