Re: wget 1.7 configure errors

2001-06-07 Thread Hrvoje Niksic

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.



Re: wget 1.7 configure errors

2001-06-06 Thread TenThumbs

On Tue, 5 Jun 2001, Jan Prikryl wrote:


 Yes, the SSL detection is broken on some systems. We are working on a
 fix.


Since wget is now a crypto application, I suggest extreme caution here.

On my system, only static SSL libraries exist. It bothers me greatly
that an attacker could corrupt a shared crypto library and, thus,
corrupt all crypto apps. Now your current testing uses rpath which is
irrelevant with static libs, but building with rpath is not benign
because that same attacker (or another one) could plant strange
libraries in the rpath location and wget could be compromised. I would
suggest either testing whether shared SSL libraries exist or providing
configure options so the user can choose.



 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.


This is my error. I have a config.site script and a cc definition
crept in by mistake. I'm sorry that I bothered you with this.

In the midst of all this, I built wget with debugging and gcc turned up
these warnings:

rbuf.c:68: warning: implicit declaration of function `ssl_iread'
retr.c:122: warning: implicit declaration of function `ssl_iread'
gen_sslfunc.c:155: warning: implicit declaration of function `select_fd'

Some header files are not included and some are incomplete. Wget works
because the defaults happen to match the actual functions. It is not a
big deal though.

Thanks.

-- 
Jupiter
2001-06-06 19:07:22.660 UTC (JD 2452067.296790)
X  =   0.631953667, Y  =   4.648285018, Z  =   1.977027736 (au)
X' =  -0.007581252, Y' =   0.001124320, Z' =   0.000666516 (au/d)




wget 1.7 configure errors

2001-06-05 Thread tenthumbs

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

2001-06-05 Thread Jan Prikryl

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
+--