Re: 2.0.49 (rc2) tarballs available
Hi, On Sat, 13 Mar 2004, Sander Striker wrote: Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ I guess you didn't get around to do the -rc3 yet. It seems that -rc2 works with --- snip --- www11: uname -a SunOS www11.thny.bbc.co.uk 5.8 Generic_108528-19 sun4u sparc SUNW,Sun-Fire-480R --- snap --- at least as well as 2.0.46. Andre' -- Andre' Breiler | Tel: +44 (0) 1628 40 BBC Internet Services | URL: http://support.bbc.co.uk Maiden House, Vanwell Road | Maidenhead, SL6 4UB | Mail me if possible. And use a Subject line.
2.0.49 (rc3) tarballs available, WAS: Re: 2.0.49 (rc2) tarballs available
On Wed, 2004-03-17 at 20:16, Andre Breiler wrote: Hi, On Sat, 13 Mar 2004, Sander Striker wrote: Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ I guess you didn't get around to do the -rc3 yet. Actually, I did :) You can find -rc3 in the usual place. The differences with rc2 are: - mod_cgid fix - docs update - windows build fix Sander
Re: 2.0.49 (rc2) tarballs available
Sander Striker wrote: And I've seen major concerns, so we'll see an rc3, tomorrow night. +1 from me on rc3; tested on HP-UX 11.11 and AIX 5.2
Re: 2.0.49 (rc3) tarballs available, WAS: Re: 2.0.49 (rc2) tarballs available
Sander Striker wrote: On Wed, 2004-03-17 at 20:16, Andre Breiler wrote: Hi, On Sat, 13 Mar 2004, Sander Striker wrote: Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ I guess you didn't get around to do the -rc3 yet. Actually, I did :) You can find -rc3 in the usual place. The differences with rc2 are: - mod_cgid fix - docs update - windows build fix Sander Quick sniff on Windows 2000 looks good. Bill
Re: 2.0.49 (rc3) tarballs available, WAS: Re: 2.0.49 (rc2) tarballs available
Hi, On Wed, 17 Mar 2004, Sander Striker wrote: On Wed, 2004-03-17 at 20:16, Andre Breiler wrote: Hi, On Sat, 13 Mar 2004, Sander Striker wrote: Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ I guess you didn't get around to do the -rc3 yet. Actually, I did :) You can find -rc3 in the usual place. The differences with Ups, seems I've been blind then (I've looked today morning) or I looked just a few mins too early. Ok, just built the -rc3 and seems to work within the lab. Next to get it onto the live box tomorrow morning. rc2 are: - mod_cgid fix - docs update - windows build fix Thank you, Andre' -- Andre' Breiler | Tel: +44 (0) 1628 40 BBC Internet Services | URL: http://support.bbc.co.uk Maiden House, Vanwell Road | Maidenhead, SL6 4UB | Mail me if possible. And use a Subject line.
Re: 2.0.49 (rc3) tarballs available, WAS: Re: 2.0.49 (rc2) tarballs available
* Sander Striker [EMAIL PROTECTED] |__ Wed, Mar 17, 2004 at 08:31:21PM +0100: You can find -rc3 in the usual place. The differences with rc2 are: - mod_cgid fix - docs update - windows build fix Looking good on; - Red Hat Linux 7.2, 7.3, 8.0, 9.0 - Fedora Core 1 Linux - Red Hat Enterprise Linux 2.1 (AS/ES), 3.0 (AS/ES) - Slackware Linux 8.1, 9.0, 9.1, and -current RH 7.3 had a libpcre.a issue during compile-time, but a quick symlink from /usr/lib to /lib fixed it. Take care. -- Chip Cuccio| [EMAIL PROTECTED] NORLUG VP and Sysadmin | http://norlug.org/~chipster/ Northfield Linux Users' Group | Northfield, Minnesota USA pgp0.pgp Description: PGP signature
Re: 2.0.49 (rc2) tarballs available
The Doctor wrote: On Sun, Mar 14, 2004 at 05:18:19PM -0700, The Doctor wrote: On Sun, Mar 14, 2004 at 04:04:31PM +, Joe Orton wrote: On Sun, Mar 14, 2004 at 07:22:24AM -0700, The Doctor wrote: Failure again on BSD/OS 5.1 It seems libtool does not know how to build shared libraries on BSD/OS 5.x; try editing srclib/apr/configure and search'n'replace the places where it says bsdi4 to read bsdi5. (this is clearly not a regression since 2.0.48) Using all static modules and libraries might work; try passing --disable-shared to configure. We need to replace bsdi4 with bsdi . That being said, mod_expires tend to fail . Any chance for an rc3? joe And in bsd/os 5.1 we have Syntax error on line 252 of /var/www/conf/httpd.conf: Cannot load /usr/libexec/apache/mod_expires.so into server: /usr/libexec/apache/mod_expires.so: Undefined PLT symbol ap_hook_insert_error_filter Next fix for RC3? In general: This all sounds like OS-specific libtool issues that are independent of changes between 2.0.48 and 2.0.49-rc2, and probably no release supported a DSO build on that level of BSD/OS. (If a prior release did work when built in exactly the same way, that may be a hint that a particular libtool version doesn't have these problems.) As far as attacking the mod_expires symptom: Need to determine if mod_expires is the only DSO busted or of most/all are busted. Play with the config file to try that out. (i.e., first comment out the LoadModule for mod_expires and see what if any fails next). Also, assuming nm is the way to display symbol table in BSD/OS, what is output of $ nm /path/to/httpd | grep ap_hook_insert $ nm /path/to/mod_expires.so | grep ap_hook_insert
Re: 2.0.49 (rc2) tarballs available
On Mon, 2004-03-15 at 12:44, Jeff Trawick wrote: The Doctor wrote: [...] And in bsd/os 5.1 we have Syntax error on line 252 of /var/www/conf/httpd.conf: Cannot load /usr/libexec/apache/mod_expires.so into server: /usr/libexec/apache/mod_expires.so: Undefined PLT symbol ap_hook_insert_error_filter Next fix for RC3? In general: This all sounds like OS-specific libtool issues that are independent of changes between 2.0.48 and 2.0.49-rc2, and probably no release supported a DSO build on that level of BSD/OS. (If a prior release did work when built in exactly the same way, that may be a hint that a particular libtool version doesn't have these problems. 2.0.48 and 2.0.49-rc2 were rolled with exactly the same libtool, so we can safely rule that out. Sander
Re: 2.0.49 (rc2) tarballs available
On Sun, Mar 14, 2004 at 07:32:01PM -0700, The Doctor wrote: On Sun, Mar 14, 2004 at 05:18:19PM -0700, The Doctor wrote: On Sun, Mar 14, 2004 at 04:04:31PM +, Joe Orton wrote: On Sun, Mar 14, 2004 at 07:22:24AM -0700, The Doctor wrote: Failure again on BSD/OS 5.1 It seems libtool does not know how to build shared libraries on BSD/OS 5.x; try editing srclib/apr/configure and search'n'replace the places where it says bsdi4 to read bsdi5. (this is clearly not a regression since 2.0.48) Using all static modules and libraries might work; try passing --disable-shared to configure. We need to replace bsdi4 with bsdi . What is the output of running srclib/apr/build/config.guess? That being said, mod_expires tend to fail . Did you replace *all* occurences of bsdi4 with bsdi4 This looks like a failure to detect the right -export-dynamic flag. If you capture the complete output of configure and attach it to the bug report you filed we can work out how to make libtool work on this platform. joe
Re: 2.0.49 (rc2) tarballs available
Sander Striker wrote: There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ This is not a regression issue, but it is a storage corruption issue as well as a simple fix that should be easy to review: *) mod_cgid: Fix storage corruption caused by use of incorrect pool. modules/generators/mod_cgid.c: r1.425 +1: trawick If there are changes before we release 2.0.49, I would love to see that fix in there, provided it has the votes.
Re: 2.0.49 (rc2) tarballs available
* Sander Striker [EMAIL PROTECTED] wrote: There are 2.0.49-rc2 tarballs available at: Please inform us of any problems you encounter. Thanks, I'm going to backport the enableexceptionhook docs. Please put them also into the next tag. Thanks! nd
Re: 2.0.49 (rc2) tarballs available
On Mon, 2004-03-15 at 22:02, André Malo wrote: * Sander Striker [EMAIL PROTECTED] wrote: There are 2.0.49-rc2 tarballs available at: Please inform us of any problems you encounter. Thanks, I'm going to backport the enableexceptionhook docs. Please put them also into the next tag. TB really honest, I think I saw enough +1s for rc2, I was planning on using that for the release. If there are major concerns not to do that, I'll do a rc3, but otherwise I'd like to get this one over and done with. Sander
Re: 2.0.49 (rc2) tarballs available
Jeff Trawick wrote: Sander Striker wrote: There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ This is not a regression issue, but it is a storage corruption issue as well as a simple fix that should be easy to review: *) mod_cgid: Fix storage corruption caused by use of incorrect pool. modules/generators/mod_cgid.c: r1.425 +1: trawick If there are changes before we release 2.0.49, I would love to see that fix in there, provided it has the votes. +1, this is an easy one to fix. Bill
Re: 2.0.49 (rc2) tarballs available
* Sander Striker [EMAIL PROTECTED] wrote: On Mon, 2004-03-15 at 22:02, André Malo wrote: * Sander Striker [EMAIL PROTECTED] wrote: There are 2.0.49-rc2 tarballs available at: Please inform us of any problems you encounter. Thanks, I'm going to backport the enableexceptionhook docs. Please put them also into the next tag. TB really honest, I think I saw enough +1s for rc2, I was planning on using that for the release. If there are major concerns not to do that, I'll do a rc3, but otherwise I'd like to get this one over and done with. -1 ;-) Seriously: I consider a directive without docs ... harmful. Additionally I remember at least the Win32 ssl.conf issue, which should get resolved. nd
Re: 2.0.49 (rc2) tarballs available
At 03:05 PM 3/15/2004, Sander Striker wrote: On Mon, 2004-03-15 at 22:02, André Malo wrote: * Sander Striker [EMAIL PROTECTED] wrote: There are 2.0.49-rc2 tarballs available at: Please inform us of any problems you encounter. Thanks, I'm going to backport the enableexceptionhook docs. Please put them also into the next tag. TB really honest, I think I saw enough +1s for rc2, I was planning on using that for the release. If there are major concerns not to do that, I'll do a rc3, but otherwise I'd like to get this one over and done with. -1 on win32 as folks pointed out the bogus state someone left ssl-std.conf in - so working on that patch now. Only Makefile.win should need pushing. A +1 after the patch should put us on the track for releasing it. Testers? Makefile.win on HEAD and APACHE_2_0_BRANCH should be golden. http://cvs.apache.org/viewcvs.cgi/httpd-2.0/Makefile.win?rev=1.120.2.14 Bill
Re: 2.0.49 (rc2) tarballs available
Hi, On Mon, 2004-03-15 at 22:02, André Malo wrote: * Sander Striker [EMAIL PROTECTED] wrote: There are 2.0.49-rc2 tarballs available at: Please inform us of any problems you encounter. Thanks, I'm going to backport the enableexceptionhook docs. Please put them also into the next tag. TB really honest, I think I saw enough +1s for rc2, I was planning on using that for the release. If there are major concerns not to do that, I'll do a rc3, but otherwise I'd like to get this one over and done with. if we would post here in html I would select font size=-3 but _if_ we get a rc-3 for other reasons I would be happy if we could get my ht* patches in... unfortunately this would violate the backport vote mecahnism, but I see no real reason against: - the htpasswd patch only extends the search for a valid temp dir - the htdigest patch uses now the same logic as htpasswd does - the first htdbm patch affects only NetWare, the second fixes a typo and corrects a bug which never worked before. currently none of the ht* tools work on NetWare, but that's probably true for a long time now, and therefore no reason to hold back a release. thanks, Guenter.
Re: 2.0.49 (rc2) tarballs available
+1 NetWare Jean-Jacques [EMAIL PROTECTED] 3/13/2004 5:32:53 AM Hi,There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/The differences with respect to the rc1 tarball are:- BeOS specific MPM fixes- Netware specific rand.c fixes- Documentation update- Berkeley DB detection fix on FreeBSDFurthermore the rc1 tarball was built using autoconf 2.57, while2.59 was used for rc2.Please inform us of any problems you encounter. Thanks,Sander
Re: 2.0.49 (rc2) tarballs available
On Mon, 2004-03-15 at 22:05, Sander Striker wrote: On Mon, 2004-03-15 at 22:02, André Malo wrote: * Sander Striker [EMAIL PROTECTED] wrote: There are 2.0.49-rc2 tarballs available at: Please inform us of any problems you encounter. Thanks, I'm going to backport the enableexceptionhook docs. Please put them also into the next tag. TB really honest, I think I saw enough +1s for rc2, I was planning on using that for the release. If there are major concerns not to do that, I'll do a rc3, but otherwise I'd like to get this one over and done with. And I've seen major concerns, so we'll see an rc3, tomorrow night. Sander
Re: 2.0.49 (rc2) tarballs available
Hi, A +1 after the patch should put us on the track for releasing it. Testers? Makefile.win on HEAD and APACHE_2_0_BRANCH should be golden. http://cvs.apache.org/viewcvs.cgi/httpd-2.0/Makefile.win?rev=1.120.2.14 +1; works again for me ; the ssl*.conf files are no longer empty. Guenter.
Re: 2.0.49 (rc2) tarballs available
On Sat, Mar 13, 2004 at 01:32:53PM +0100, Sander Striker wrote: Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ The differences with respect to the rc1 tarball are: - BeOS specific MPM fixes - Netware specific rand.c fixes - Documentation update - Berkeley DB detection fix on FreeBSD Furthermore the rc1 tarball was built using autoconf 2.57, while 2.59 was used for rc2. Please inform us of any problems you encounter. Thanks, Failure again on BSD/OS 5.1 Script started on Sat Mar 13 09:16:35 2004 sh-2.02# make install Making install in srclib Making install in apr Making all in strings Making all in passwd Making all in tables Making all in file_io/unix Making all in network_io/unix Making all in threadproc/unix Making all in misc/unix Making all in locks/unix Making all in time/unix Making all in mmap/unix Making all in shmem/unix Making all in user/unix Making all in memory/unix Making all in atomic/unix Making all in poll/unix Making all in support/unix Making all in dso/unix if [ ! -d /usr/include/apache ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/include/apache; fi; cp -p /usr/source/httpd-2.0.49-rc2/srclib/apr/include/*.h /usr/include/apache; if test -n /usr/source/httpd-2.0.49-rc2/srclib/apr; then cp -p /usr/source/httpd-2.0.49-rc2/srclib/apr/include/*.h /usr/include/apache; fi; if [ ! -d /usr/lib ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/lib; fi; /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp libapr-0.la /usr/lib cp .libs/libapr-0.lai /usr/lib/libapr-0.la cp .libs/libapr-0.a /usr/lib/libapr-0.a ranlib /usr/lib/libapr-0.a chmod 644 /usr/lib/libapr-0.a -- Libraries have been installed in: /usr/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. -- /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp apr.exp /usr/lib cp apr.exp /usr/lib/apr.exp if [ ! -d /var/www/build ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /var/www/build; fi; if [ -f libtool ]; then /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp libtool /var/www/build; fi; cp libtool /var/www/build/libtool if [ -f shlibtool ]; then /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp shlibtool /var/www/build; fi; if [ -f build/apr_rules.mk ]; then cp build/apr_rules.mk /var/www/build; fi; if [ ! -d /usr/bin ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/bin; fi; /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp apr-config /usr/bin cp apr-config /usr/bin/apr-config chmod 755 /usr/bin/apr-config Making install in apr-util Making all in buckets Making all in crypto Making all in dbm Making all in sdbm Making all in . Making all in encoding Making all in hooks Making all in ldap Making all in uri Making all in xml Making all in expat Making all in misc Making all in strmatch Making all in xlate if [ ! -d /usr/include/apache ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/include/apache; fi; cp -p /usr/source/httpd-2.0.49-rc2/srclib/apr-util/include/*.h /usr/include/apache if [ -n /usr/source/httpd-2.0.49-rc2/srclib/apr-util ]; then cp -p /usr/source/httpd-2.0.49-rc2/srclib/apr-util/include/*.h /usr/include/apache; fi; if [ ! -d /usr/lib ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/lib; fi; list='xml/expat'; for i in $list; do ( cd $i ; make DESTDIR= install ); done /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr-util/xml/expat/conftools/mkinstalldirs /usr/lib /usr/include/apache /bin/bash ../libtool --mode=install /usr/bin/install -c libexpat.la /usr/lib/libexpat.la /usr/bin/install -c .libs/libexpat.lai /usr/lib/libexpat.la /usr/bin/install -c .libs/libexpat.a /usr/lib/libexpat.a ranlib /usr/lib/libexpat.a chmod 644 /usr/lib/libexpat.a -- Libraries have been installed in: /usr/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the
Re: 2.0.49 (rc2) tarballs available
On Sun, 2004-03-14 at 15:22, The Doctor wrote: On Sat, Mar 13, 2004 at 01:32:53PM +0100, Sander Striker wrote: Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ The differences with respect to the rc1 tarball are: - BeOS specific MPM fixes - Netware specific rand.c fixes - Documentation update - Berkeley DB detection fix on FreeBSD Furthermore the rc1 tarball was built using autoconf 2.57, while 2.59 was used for rc2. Please inform us of any problems you encounter. Thanks, Failure again on BSD/OS 5.1 Yeah, I wasn't expecting that to go away, since there weren't any BSD fixes to this effect. Jeff asked you something in response to your failures with rc1: What got installed into /usr/libexec/apache by make install? Did the DSOs get installed with unexpected names? Second, does 2.0.48 built in exactly the same way fail in a similar manner? Could you please provide us with an answer to that so we can try and locate the cause of the problem? Thanks, Sander
Re: 2.0.49 (rc2) tarballs available
On Sun, Mar 14, 2004 at 04:07:27PM +0100, Sander Striker wrote: On Sun, 2004-03-14 at 15:22, The Doctor wrote: On Sat, Mar 13, 2004 at 01:32:53PM +0100, Sander Striker wrote: Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ The differences with respect to the rc1 tarball are: - BeOS specific MPM fixes - Netware specific rand.c fixes - Documentation update - Berkeley DB detection fix on FreeBSD Furthermore the rc1 tarball was built using autoconf 2.57, while 2.59 was used for rc2. Please inform us of any problems you encounter. Thanks, Failure again on BSD/OS 5.1 Yeah, I wasn't expecting that to go away, since there weren't any BSD fixes to this effect. Jeff asked you something in response to your failures with rc1: What got installed into /usr/libexec/apache by make install? Did the DSOs get installed with unexpected names? Second, does 2.0.48 built in exactly the same way fail in a similar manner? Could you please provide us with an answer to that so we can try and locate the cause of the problem? This works on BSD/Os 4.3 but screws up on 5.1 . I have a ticket with Wind river on this. they suspect the libtool but I would liketo come on baord the BSD/OS 5.1 Box and inspect this problem for yourselves. Thanks, Sander -- Member - Liberal International On 11 Sept 2001 the WORLD was violated. This is [EMAIL PROTECTED] Ici [EMAIL PROTECTED] Society MUST be saved! Extremists must dissolve. Time to see the eternal relegation of Man U, Liverpool, Everton and Millwall
Re: 2.0.49 (rc2) tarballs available
On Sun, Mar 14, 2004 at 04:07:27PM +0100, Sander Striker wrote: On Sun, 2004-03-14 at 15:22, The Doctor wrote: On Sat, Mar 13, 2004 at 01:32:53PM +0100, Sander Striker wrote: Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ The differences with respect to the rc1 tarball are: - BeOS specific MPM fixes - Netware specific rand.c fixes - Documentation update - Berkeley DB detection fix on FreeBSD Furthermore the rc1 tarball was built using autoconf 2.57, while 2.59 was used for rc2. Please inform us of any problems you encounter. Thanks, Failure again on BSD/OS 5.1 Yeah, I wasn't expecting that to go away, since there weren't any BSD fixes to this effect. Jeff asked you something in response to your failures with rc1: What got installed into /usr/libexec/apache by make install? Did the DSOs get installed with unexpected names? Oh that. We get the la 's installed and not the so's . apache 1.3.X does work acc BSD/OS . Second, does 2.0.48 built in exactly the same way fail in a similar manner? Could you please provide us with an answer to that so we can try and locate the cause of the problem? Thanks, Sander -- Member - Liberal International On 11 Sept 2001 the WORLD was violated. This is [EMAIL PROTECTED] Ici [EMAIL PROTECTED] Society MUST be saved! Extremists must dissolve. Time to see the eternal relegation of Man U, Liverpool, Everton and Millwall
Re: 2.0.49 (rc2) tarballs available
On Sun, 2004-03-14 at 16:16, The Doctor wrote: On Sun, Mar 14, 2004 at 04:07:27PM +0100, Sander Striker wrote: On Sun, 2004-03-14 at 15:22, The Doctor wrote: Failure again on BSD/OS 5.1 Yeah, I wasn't expecting that to go away, since there weren't any BSD fixes to this effect. Jeff asked you something in response to your failures with rc1: What got installed into /usr/libexec/apache by make install? Did the DSOs get installed with unexpected names? Second, does 2.0.48 built in exactly the same way fail in a similar manner? Could you please provide us with an answer to that so we can try and locate the cause of the problem? This works on BSD/Os 4.3 but screws up on 5.1 . I have a ticket with Wind river on this. they suspect the libtool but I would liketo come on baord the BSD/OS 5.1 Box and inspect this problem for yourselves. Could you try running 'buildconf' from the top of the tree and see if you get the same problem after that? Sander
Re: 2.0.49 (rc2) tarballs available
On Sun, Mar 14, 2004 at 07:22:24AM -0700, The Doctor wrote: Failure again on BSD/OS 5.1 It seems libtool does not know how to build shared libraries on BSD/OS 5.x; try editing srclib/apr/configure and search'n'replace the places where it says bsdi4 to read bsdi5. (this is clearly not a regression since 2.0.48) Using all static modules and libraries might work; try passing --disable-shared to configure. joe
Re: 2.0.49 (rc2) tarballs available
On Sun, Mar 14, 2004 at 04:39:46PM +0100, Sander Striker wrote: On Sun, 2004-03-14 at 16:16, The Doctor wrote: On Sun, Mar 14, 2004 at 04:07:27PM +0100, Sander Striker wrote: On Sun, 2004-03-14 at 15:22, The Doctor wrote: Failure again on BSD/OS 5.1 Yeah, I wasn't expecting that to go away, since there weren't any BSD fixes to this effect. Jeff asked you something in response to your failures with rc1: What got installed into /usr/libexec/apache by make install? Did the DSOs get installed with unexpected names? Second, does 2.0.48 built in exactly the same way fail in a similar manner? Could you please provide us with an answer to that so we can try and locate the cause of the problem? This works on BSD/Os 4.3 but screws up on 5.1 . I have a ticket with Wind river on this. they suspect the libtool but I would liketo come on baord the BSD/OS 5.1 Box and inspect this problem for yourselves. Could you try running 'buildconf' from the top of the tree and see if you get the same problem after that? Sander Tell me how and I will do it. -- Member - Liberal International On 11 Sept 2001 the WORLD was violated. This is [EMAIL PROTECTED] Ici [EMAIL PROTECTED] Society MUST be saved! Extremists must dissolve. Time to see the eternal relegation of Man U, Liverpool, Everton and Millwall
Re: 2.0.49 (rc2) tarballs available
* The Doctor [EMAIL PROTECTED] wrote: Could you try running 'buildconf' from the top of the tree and see if you get the same problem after that? Tell me how and I will do it. In the top src dir is a script 'buildconf'. You just run it before your configure run. You need autoconf and libtool installed on your box. ./buildconf ./configure ... nd
Re: 2.0.49 (rc2) tarballs available
On Sun, Mar 14, 2004 at 04:04:31PM +, Joe Orton wrote: On Sun, Mar 14, 2004 at 07:22:24AM -0700, The Doctor wrote: Failure again on BSD/OS 5.1 It seems libtool does not know how to build shared libraries on BSD/OS 5.x; try editing srclib/apr/configure and search'n'replace the places where it says bsdi4 to read bsdi5. (this is clearly not a regression since 2.0.48) Using all static modules and libraries might work; try passing --disable-shared to configure. We need to replace bsdi4 with bsdi . That being said, mod_expires tend to fail . Any chance for an rc3? joe -- Member - Liberal International On 11 Sept 2001 the WORLD was violated. This is [EMAIL PROTECTED] Ici [EMAIL PROTECTED] Society MUST be saved! Extremists must dissolve. Time to see the eternal relegation of Man U, Liverpool, Everton and Millwall
Re: 2.0.49 (rc2) tarballs available
The Doctor wrote: On Sun, Mar 14, 2004 at 04:04:31PM +, Joe Orton wrote: On Sun, Mar 14, 2004 at 07:22:24AM -0700, The Doctor wrote: Failure again on BSD/OS 5.1 It seems libtool does not know how to build shared libraries on BSD/OS 5.x; try editing srclib/apr/configure and search'n'replace the places where it says bsdi4 to read bsdi5. (this is clearly not a regression since 2.0.48) Using all static modules and libraries might work; try passing --disable-shared to configure. We need to replace bsdi4 with bsdi . That being said, mod_expires tend to fail . Any chance for an rc3? if libtool-generated segments in configure are incorrect I don't see us distributing a hacked configure... the s/bsdi4/bsdi/ substitution would be a local work-around for the libtool issue and a real fix will need to come with a libtool update what is the mod_expires issue? (mod_expires tend to fail)
Re: 2.0.49 (rc2) tarballs available
On Sun, Mar 14, 2004 at 05:18:19PM -0700, The Doctor wrote: On Sun, Mar 14, 2004 at 04:04:31PM +, Joe Orton wrote: On Sun, Mar 14, 2004 at 07:22:24AM -0700, The Doctor wrote: Failure again on BSD/OS 5.1 It seems libtool does not know how to build shared libraries on BSD/OS 5.x; try editing srclib/apr/configure and search'n'replace the places where it says bsdi4 to read bsdi5. (this is clearly not a regression since 2.0.48) Using all static modules and libraries might work; try passing --disable-shared to configure. We need to replace bsdi4 with bsdi . That being said, mod_expires tend to fail . Any chance for an rc3? joe And in bsd/os 5.1 we have Syntax error on line 252 of /var/www/conf/httpd.conf: Cannot load /usr/libexec/apache/mod_expires.so into server: /usr/libexec/apache/mod_expires.so: Undefined PLT symbol ap_hook_insert_error_filter Next fix for RC3? -- Member - Liberal International On 11 Sept 2001 the WORLD was violated. This is [EMAIL PROTECTED] Ici [EMAIL PROTECTED] Society MUST be saved! Extremists must dissolve. Time to see the eternal relegation of Man U, Liverpool, Everton and Millwall
RE: 2.0.49 (rc2) tarballs available
How does one sign up as a tester and or deugger Steve -Original Message- From: The Doctor [mailto:[EMAIL PROTECTED] Sent: 14 March 2004 09:22 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: 2.0.49 (rc2) tarballs available On Sat, Mar 13, 2004 at 01:32:53PM +0100, Sander Striker wrote: Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ The differences with respect to the rc1 tarball are: - BeOS specific MPM fixes - Netware specific rand.c fixes - Documentation update - Berkeley DB detection fix on FreeBSD Furthermore the rc1 tarball was built using autoconf 2.57, while 2.59 was used for rc2. Please inform us of any problems you encounter. Thanks, Failure again on BSD/OS 5.1 Script started on Sat Mar 13 09:16:35 2004 sh-2.02# make install Making install in srclib Making install in apr Making all in strings Making all in passwd Making all in tables Making all in file_io/unix Making all in network_io/unix Making all in threadproc/unix Making all in misc/unix Making all in locks/unix Making all in time/unix Making all in mmap/unix Making all in shmem/unix Making all in user/unix Making all in memory/unix Making all in atomic/unix Making all in poll/unix Making all in support/unix Making all in dso/unix if [ ! -d /usr/include/apache ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/include/apache; fi; cp -p /usr/source/httpd-2.0.49-rc2/srclib/apr/include/*.h /usr/include/apache; if test -n /usr/source/httpd-2.0.49-rc2/srclib/apr; then cp -p /usr/source/httpd-2.0.49-rc2/srclib/apr/include/*.h /usr/include/apache; fi; if [ ! -d /usr/lib ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/lib; fi; /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp libapr-0.la /usr/lib cp .libs/libapr-0.lai /usr/lib/libapr-0.la cp .libs/libapr-0.a /usr/lib/libapr-0.a ranlib /usr/lib/libapr-0.a chmod 644 /usr/lib/libapr-0.a -- Libraries have been installed in: /usr/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. -- /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp apr.exp /usr/lib cp apr.exp /usr/lib/apr.exp if [ ! -d /var/www/build ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /var/www/build; fi; if [ -f libtool ]; then /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp libtool /var/www/build; fi; cp libtool /var/www/build/libtool if [ -f shlibtool ]; then /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp shlibtool /var/www/build; fi; if [ -f build/apr_rules.mk ]; then cp build/apr_rules.mk /var/www/build; fi; if [ ! -d /usr/bin ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/bin; fi; /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr/libtool --mode=install cp apr-config /usr/bin cp apr-config /usr/bin/apr-config chmod 755 /usr/bin/apr-config Making install in apr-util Making all in buckets Making all in crypto Making all in dbm Making all in sdbm Making all in . Making all in encoding Making all in hooks Making all in ldap Making all in uri Making all in xml Making all in expat Making all in misc Making all in strmatch Making all in xlate if [ ! -d /usr/include/apache ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/include/apache; fi; cp -p /usr/source/httpd-2.0.49-rc2/srclib/apr-util/include/*.h /usr/include/apache if [ -n /usr/source/httpd-2.0.49-rc2/srclib/apr-util ]; then cp -p /usr/source/httpd-2.0.49-rc2/srclib/apr-util/include/*.h /usr/include/apache; fi; if [ ! -d /usr/lib ]; then /usr/source/httpd-2.0.49-rc2/srclib/apr/build/mkdir.sh /usr/lib; fi; list='xml/expat'; for i in $list; do ( cd $i ; make DESTDIR= install ); done /bin/bash /usr/source/httpd-2.0.49-rc2/srclib/apr-util/xml/expat/conftools/mkinsta lldirs /usr/lib /usr/include/apache /bin/bash ../libtool --mode=install /usr/bin/install -c libexpat.la /usr/lib/libexpat.la /usr/bin/install -c .libs/libexpat.lai /usr/lib/libexpat.la /usr/bin/install -c .libs/libexpat.a /usr/lib/libexpat.a ranlib /usr/lib/libexpat.a chmod 644 /usr/lib/libexpat.a -- Libraries have been installed in: /usr/lib For the best in promotional products
RE: 2.0.49 (rc2) tarballs available
On Mon, 15 Mar 2004, Steve Rieger (Apache) wrote: How does one sign up as a tester and or deugger You can subscribe to the testers mailing list if you want to receive notices of release candidates... (see http://httpd.apache.org/lists.html). And/or you can just try it out, see if it bombs, and if it does, report back here on [EMAIL PROTECTED] :) --Cliff
Re: 2.0.49 (rc2) tarballs available
* Sander Striker [EMAIL PROTECTED] wrote: There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ The differences with respect to the rc1 tarball are: - BeOS specific MPM fixes - Netware specific rand.c fixes - Documentation update - Berkeley DB detection fix on FreeBSD Furthermore the rc1 tarball was built using autoconf 2.57, while 2.59 was used for rc2. Test suite runs fine on my Gentoo Linux box with: config.nice: #! /bin/sh # # Created by configure CC=gcc; export CC CFLAGS=-O3 -Wall -pipe -march=athlon -freorder-blocks -freorder-functions -maccumulate-outgoing-args -fomit-frame-pointer; export CFLAGS ./configure \ -q \ --prefix=/work/nd/httpd-2.0.49 \ --enable-modules=all \ --enable-ssl \ --enable-logio \ --enable-bucketeer \ --enable-deflate \ --enable-proxy \ $@ and gcc -v: [..] gcc-Version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7) So +1 here. nd
Re: 2.0.49 (rc2) tarballs available
Thumbs up on; - Red Hat Linux 7.2, 7.3, 8.0, 9.0 - Fedora Core 1 Linux - Red Hat Enterprise Linux 2.1 (AS/ES), 3.0 (AS/ES) - Slackware Linux 8.1, 9.0, 9.1, and -current whew +1 Thanks. -- Chip Cuccio| [EMAIL PROTECTED] NORLUG VP and Sysadmin | http://norlug.org/~chipster/ Northfield Linux Users' Group | Northfield, Minnesota USA pgp0.pgp Description: PGP signature
Re: 2.0.49 (rc2) tarballs available
Hi, There are 2.0.49-rc2 tarballs available at: http://httpd.apache.org/dev/dist/ The differences with respect to the rc1 tarball are: - BeOS specific MPM fixes - Netware specific rand.c fixes - Documentation update - Berkeley DB detection fix on FreeBSD Just found that on Win32 the ssl conf files are now empty (zero bytes); this is also with rc1 - sorry but just found... Guenter.
