Re: Apache_fp Port install problem
On Sat, 11 Jan 2003 11:31:22 -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? yeah, you need to have COMPAT3X=TRUE in your /etc/make.conf took me three day to figure that one out --- doug reynolds | the maverick | [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
At 07:31 PM 1.16.2003 -0500, Doug Reynolds wrote: On Sat, 11 Jan 2003 11:31:22 -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? yeah, you need to have COMPAT3X=TRUE in your /etc/make.conf took me three day to figure that one out --- doug reynolds | the maverick | [EMAIL PROTECTED] Hi, Doug: You say COMPAT3X=TRUE ...but the /etc/defaults/make.conf says: COMPAT3X= yes(note the spacing too) Will you double-check this syntax?? I thought it had to be the same as the default statement, but my first attempts using COMPAT3X= yes didn't do any good. Then someone (Gordon) suggested deleting /usr/scr and adding the statement as well. Did you do that too...??? ..or just the add to the make.conf I'd rather not delete /usr/src if not necessary and the question boils down to: COMPAT3X=TRUE vs COMPAT3X= yes (I guess) ...sorry for all the nit-pick questions, but I know the problems lies here and something simple. Thanks! Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
On Thu, 16 Jan 2003 19:52:33 -0600, Jack L. Stone wrote: I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? yeah, you need to have COMPAT3X=TRUE in your /etc/make.conf took me three day to figure that one out --- doug reynolds | the maverick | [EMAIL PROTECTED] Hi, Doug: You say COMPAT3X=TRUE ...but the /etc/defaults/make.conf says: COMPAT3X= yes(note the spacing too) Will you double-check this syntax?? I thought it had to be the same as the default statement, but my first attempts using COMPAT3X= yes didn't do any good. Then someone (Gordon) suggested deleting /usr/scr and adding the statement as well. Did you do that too...??? ..or just the add to the make.conf I'd rather not delete /usr/src if not necessary and the question boils down to: COMPAT3X=TRUE vs COMPAT3X= yes (I guess) ...sorry for all the nit-pick questions, but I know the problems lies here and something simple. I know for sure i did not delete my /usr/src; I don't think i even did a make clean, but i might have. i don't normally do that. I know it works, frontpage works everytime. this is what my make.conf say (in full) CPUTYPE=k6-2 NO_SENDMAIL=true COMPAT3X=true according to man make.conf The following list provides a name and short description for variables that are used during the world build: COMPAT1X (bool) Set to install the FreeBSD 1 compatibility libraries. COMPAT20 (bool) Set to install the FreeBSD 2.0 compatibility libraries. COMPAT21 (bool) Set to install the FreeBSD 2.1 compatibility libraries. COMPAT22 (bool) Set to install the FreeBSD 2.2 compatibility libraries. COMPAT3X (bool) Set to install the FreeBSD 3 compatibility libraries. COMPAT4X (bool) Set to install the FreeBSD 4 compatibility libraries. boolean should mean true or false, but in most cases, it means yes no --- doug reynolds | the maverick | [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
Hi I deleted my /usr/src and cvsupped and the usual make world and this fixed the issue - so no need for a complete reinstall after all!!! Many thanks Gordon - Original Message - From: Jack L. Stone [EMAIL PROTECTED] To: [EMAIL PROTECTED]; G D McKee [EMAIL PROTECTED]; Matthew Seaman [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, January 13, 2003 11:26 PM Subject: RE: Apache_fp Port install problem At 05:48 PM 1.13.2003 -0500, JoeB wrote: I installed apache-fp on newly install FBSD 4.7 system that was installed from cd without any compt selected from /stand/sysinstall process and apache-fp was the first port installed on this system and in went in with no problem. You must have an older version of compt3 on your FBSD system that is causing the problem. If you installed compatibility from the /stand/sysinstall process during the original install then I believe the ports/make environment does not know about it and the only solution is to reinstall FSBD from cd. The other problem area is that you may have a old version of compt3 on your ports installed environment and if so, you will have to find which of your installed ports has compt3 as a pre-rec, deinstall all the ports using it, delete compt3 from /usr/ports/distfiles, and then make the ports again. Or install portupgrade and let it do all the detail work for you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of G D McKee Sent: Monday, January 13, 2003 5:20 PM To: [EMAIL PROTECTED]; Jack L. Stone; Matthew Seaman; [EMAIL PROTECTED] Subject: Re: Apache_fp Port install problem Hi I have just cvsupped today and get the error - are you saying to add the COMPT3 into make.conf cd /usr/src make clean and rm -rf /usr/obj to get it to work? Is there not a few files I can copy to get it working? Many thanks Gordon A lot snipped out Joe, installed from a CD??? If that is from the ISO 4.7-RELEASE, then it predates the compatX3 change we are talking about here. I have 4.7-STABLE installed from Cvsups that further updated after the RELEASE all the way up to November 5. But, on November 11, the compatX3 ocurred and any install after November 11, FP is affected and does not cooperate. Does your /usr/src/UPDATING show the 20021110 change?? It's the last release note. If not, then your 4.7 is not compatX3 challenged as far as FP is concerned. When was your last CVSup...??? Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
At 07:33 PM 1.14.2003 -, G D McKee wrote: Hi I deleted my /usr/src and cvsupped and the usual make world and this fixed the issue - so no need for a complete reinstall after all!!! Many thanks Gordon A LOT chopped out Gorden, that is certainly good to hear! But, did you add the COMPATX3=yes to the make.conf file...??? Important to know this as well Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
Hi Yes I did!! Sorry!! Many thanks for all the help Gordon - Original Message - From: Jack L. Stone [EMAIL PROTECTED] To: G D McKee [EMAIL PROTECTED]; [EMAIL PROTECTED]; Matthew Seaman [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, January 14, 2003 8:15 PM Subject: Re: Apache_fp Port install problem At 07:33 PM 1.14.2003 -, G D McKee wrote: Hi I deleted my /usr/src and cvsupped and the usual make world and this fixed the issue - so no need for a complete reinstall after all!!! Many thanks Gordon A LOT chopped out Gorden, that is certainly good to hear! But, did you add the COMPATX3=yes to the make.conf file...??? Important to know this as well Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Apache_fp Port install problem
I installed apache-fp on newly install FBSD 4.7 system that was installed from cd without any compt selected from /stand/sysinstall process and apache-fp was the first port installed on this system and in went in with no problem. You must have an older version of compt3 on your FBSD system that is causing the problem. If you installed compatibility from the /stand/sysinstall process during the original install then I believe the ports/make environment does not know about it and the only solution is to reinstall FSBD from cd. The other problem area is that you may have a old version of compt3 on your ports installed environment and if so, you will have to find which of your installed ports has compt3 as a pre-rec, deinstall all the ports using it, delete compt3 from /usr/ports/distfiles, and then make the ports again. Or install portupgrade and let it do all the detail work for you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of G D McKee Sent: Monday, January 13, 2003 5:20 PM To: [EMAIL PROTECTED]; Jack L. Stone; Matthew Seaman; [EMAIL PROTECTED] Subject: Re: Apache_fp Port install problem Hi I have just cvsupped today and get the error - are you saying to add the COMPT3 into make.conf cd /usr/src make clean and rm -rf /usr/obj to get it to work? Is there not a few files I can copy to get it working? Many thanks Gordon - Original Message - From: JoeB [EMAIL PROTECTED] To: Jack L. Stone [EMAIL PROTECTED]; Matthew Seaman [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, January 12, 2003 5:02 PM Subject: RE: Apache_fp Port install problem At 12:03 PM 1.12.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 12:01:44PM -0600, Jack L. Stone wrote: At 05:44 PM 1.11.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 11:31:22AM -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? /usr/src/UPDATING says: 20021110: The definitions of the standard file streams (stdio, stdout, and stderr) have changed so that they are no longer compile-time constants. Some older binaries may require updated 3.X compatability libraries (for example, by setting COMPAT3X=yes for a buildworld/installworld). Alternatively to doing a buildworld with COMPAT3X=yes, you could install the misc/compat3x port. Good grief! I read the UPDATING as always, but this one did NOT sink in! Thank you so much for pointing me in the right direction before I shot myself in the foot If I go the misc/compat3x port route, I assume I need to redo the buildword?? If so, then I might as well include the COMPAT3X=yes in the make.conf. All that setting COMPAT3X=yes does is cause the buildworld process to uudecode and install some precompiled copies of FreeBSD-3.x shared libraries --- see /usr/src/lib/compat/compat3x.i386 for what's available. Those libraries were originally just copied off a 3.x machine, but since then kernel changes in 4.x or 5.0 have meant that certain changes have had to be back ported to RELENG_3 in order to maintain compatibility between the 3.x shlibs and the kernel. Supplying those libraries by installing the port achieves exactly the same effect, but quicker. However, the choice is entirely up to you. In the long run, putting COMPAT3X into /etc/make.conf would be my choice, as my regular schedule of buildworlds would ensure everything was up to date. Once the 3.x shlibs are in place, the binary frontpage binary supplied with the apache-fp port should pick them up OK. The interface between the 3.x shlibs and any applications linked to them should remain exactly the same. Cheers, Matthew Matthew, thanks again for the reply. However, I've tried both methods of the compat3x on a test server, including and whole new build/installworld
RE: Apache_fp Port install problem
At 05:48 PM 1.13.2003 -0500, JoeB wrote: I installed apache-fp on newly install FBSD 4.7 system that was installed from cd without any compt selected from /stand/sysinstall process and apache-fp was the first port installed on this system and in went in with no problem. You must have an older version of compt3 on your FBSD system that is causing the problem. If you installed compatibility from the /stand/sysinstall process during the original install then I believe the ports/make environment does not know about it and the only solution is to reinstall FSBD from cd. The other problem area is that you may have a old version of compt3 on your ports installed environment and if so, you will have to find which of your installed ports has compt3 as a pre-rec, deinstall all the ports using it, delete compt3 from /usr/ports/distfiles, and then make the ports again. Or install portupgrade and let it do all the detail work for you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of G D McKee Sent: Monday, January 13, 2003 5:20 PM To: [EMAIL PROTECTED]; Jack L. Stone; Matthew Seaman; [EMAIL PROTECTED] Subject: Re: Apache_fp Port install problem Hi I have just cvsupped today and get the error - are you saying to add the COMPT3 into make.conf cd /usr/src make clean and rm -rf /usr/obj to get it to work? Is there not a few files I can copy to get it working? Many thanks Gordon A lot snipped out Joe, installed from a CD??? If that is from the ISO 4.7-RELEASE, then it predates the compatX3 change we are talking about here. I have 4.7-STABLE installed from Cvsups that further updated after the RELEASE all the way up to November 5. But, on November 11, the compatX3 ocurred and any install after November 11, FP is affected and does not cooperate. Does your /usr/src/UPDATING show the 20021110 change?? It's the last release note. If not, then your 4.7 is not compatX3 challenged as far as FP is concerned. When was your last CVSup...??? Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
On Sat, Jan 11, 2003 at 12:01:44PM -0600, Jack L. Stone wrote: At 05:44 PM 1.11.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 11:31:22AM -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? /usr/src/UPDATING says: 20021110: The definitions of the standard file streams (stdio, stdout, and stderr) have changed so that they are no longer compile-time constants. Some older binaries may require updated 3.X compatability libraries (for example, by setting COMPAT3X=yes for a buildworld/installworld). Alternatively to doing a buildworld with COMPAT3X=yes, you could install the misc/compat3x port. Good grief! I read the UPDATING as always, but this one did NOT sink in! Thank you so much for pointing me in the right direction before I shot myself in the foot If I go the misc/compat3x port route, I assume I need to redo the buildword?? If so, then I might as well include the COMPAT3X=yes in the make.conf. All that setting COMPAT3X=yes does is cause the buildworld process to uudecode and install some precompiled copies of FreeBSD-3.x shared libraries --- see /usr/src/lib/compat/compat3x.i386 for what's available. Those libraries were originally just copied off a 3.x machine, but since then kernel changes in 4.x or 5.0 have meant that certain changes have had to be back ported to RELENG_3 in order to maintain compatibility between the 3.x shlibs and the kernel. Supplying those libraries by installing the port achieves exactly the same effect, but quicker. However, the choice is entirely up to you. In the long run, putting COMPAT3X into /etc/make.conf would be my choice, as my regular schedule of buildworlds would ensure everything was up to date. Once the 3.x shlibs are in place, the binary frontpage binary supplied with the apache-fp port should pick them up OK. The interface between the 3.x shlibs and any applications linked to them should remain exactly the same. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
At 12:03 PM 1.12.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 12:01:44PM -0600, Jack L. Stone wrote: At 05:44 PM 1.11.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 11:31:22AM -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? /usr/src/UPDATING says: 20021110: The definitions of the standard file streams (stdio, stdout, and stderr) have changed so that they are no longer compile-time constants. Some older binaries may require updated 3.X compatability libraries (for example, by setting COMPAT3X=yes for a buildworld/installworld). Alternatively to doing a buildworld with COMPAT3X=yes, you could install the misc/compat3x port. Good grief! I read the UPDATING as always, but this one did NOT sink in! Thank you so much for pointing me in the right direction before I shot myself in the foot If I go the misc/compat3x port route, I assume I need to redo the buildword?? If so, then I might as well include the COMPAT3X=yes in the make.conf. All that setting COMPAT3X=yes does is cause the buildworld process to uudecode and install some precompiled copies of FreeBSD-3.x shared libraries --- see /usr/src/lib/compat/compat3x.i386 for what's available. Those libraries were originally just copied off a 3.x machine, but since then kernel changes in 4.x or 5.0 have meant that certain changes have had to be back ported to RELENG_3 in order to maintain compatibility between the 3.x shlibs and the kernel. Supplying those libraries by installing the port achieves exactly the same effect, but quicker. However, the choice is entirely up to you. In the long run, putting COMPAT3X into /etc/make.conf would be my choice, as my regular schedule of buildworlds would ensure everything was up to date. Once the 3.x shlibs are in place, the binary frontpage binary supplied with the apache-fp port should pick them up OK. The interface between the 3.x shlibs and any applications linked to them should remain exactly the same. Cheers, Matthew Matthew, thanks again for the reply. However, I've tried both methods of the compat3x on a test server, including and whole new build/installworld and the latest 4.7-STABLE still hoses FrontPage. I even deleted and started from scratch on Apache+FP-1.27, but the FP install stops dead at trying to chown the uid:gid on the root web and gives the same error: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 This caught me by surprise because I'd had FP running fine with FBSD-4.7 (RELEASE and STABLE) on other servers, but it was the installs JUST prior to the change date of 20021110. In fact they where only 5 days earlier. FP still doesn't understand what's going on apparently. Backing down to the installs prior to 20021110 makes FP happy again. Unfortunately, until I figure out the cure, I can't track 4.7-STABLE. As much as it is a pain, I must run FP for the users. No doubt others running FP must have seen this by now nothing else is affected and 4.7-STABLE runs fine otherwise (tried several machines). Any other thoughts, Matthew or from anyone much appreciated. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Apache_fp Port install problem
At 12:03 PM 1.12.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 12:01:44PM -0600, Jack L. Stone wrote: At 05:44 PM 1.11.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 11:31:22AM -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? /usr/src/UPDATING says: 20021110: The definitions of the standard file streams (stdio, stdout, and stderr) have changed so that they are no longer compile-time constants. Some older binaries may require updated 3.X compatability libraries (for example, by setting COMPAT3X=yes for a buildworld/installworld). Alternatively to doing a buildworld with COMPAT3X=yes, you could install the misc/compat3x port. Good grief! I read the UPDATING as always, but this one did NOT sink in! Thank you so much for pointing me in the right direction before I shot myself in the foot If I go the misc/compat3x port route, I assume I need to redo the buildword?? If so, then I might as well include the COMPAT3X=yes in the make.conf. All that setting COMPAT3X=yes does is cause the buildworld process to uudecode and install some precompiled copies of FreeBSD-3.x shared libraries --- see /usr/src/lib/compat/compat3x.i386 for what's available. Those libraries were originally just copied off a 3.x machine, but since then kernel changes in 4.x or 5.0 have meant that certain changes have had to be back ported to RELENG_3 in order to maintain compatibility between the 3.x shlibs and the kernel. Supplying those libraries by installing the port achieves exactly the same effect, but quicker. However, the choice is entirely up to you. In the long run, putting COMPAT3X into /etc/make.conf would be my choice, as my regular schedule of buildworlds would ensure everything was up to date. Once the 3.x shlibs are in place, the binary frontpage binary supplied with the apache-fp port should pick them up OK. The interface between the 3.x shlibs and any applications linked to them should remain exactly the same. Cheers, Matthew Matthew, thanks again for the reply. However, I've tried both methods of the compat3x on a test server, including and whole new build/installworld and the latest 4.7-STABLE still hoses FrontPage. I even deleted and started from scratch on Apache+FP-1.27, but the FP install stops dead at trying to chown the uid:gid on the root web and gives the same error: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 This caught me by surprise because I'd had FP running fine with FBSD-4.7 (RELEASE and STABLE) on other servers, but it was the installs JUST prior to the change date of 20021110. In fact they where only 5 days earlier. FP still doesn't understand what's going on apparently. Backing down to the installs prior to 20021110 makes FP happy again. Unfortunately, until I figure out the cure, I can't track 4.7-STABLE. As much as it is a pain, I must run FP for the users. No doubt others running FP must have seen this by now nothing else is affected and 4.7-STABLE runs fine otherwise (tried several machines). Any other thoughts, Matthew or from anyone much appreciated. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jack L. Stone Sent: Sunday, January 12, 2003 10:56 AM To: Matthew Seaman; [EMAIL PROTECTED] Subject: Re: Apache_fp Port install problem Jack: Last Thursday I installed apache-fp from the ports collection on newly installed FBSD 4.7 box and it installed without any problems. But remember a clean install also installs a clean copy of all the frontpage pre-rec's which COMPAT3X is one. If I remember correctly you also have a lot of other mods on apache-fp and that may have messed up the COMPAT3X version you though you were using. All I am saying is as of 1/09/03 the apache-fp port installs cleanly and functions correctly
RE: Apache_fp Port install problem
At 12:02 PM 1.12.2003 -0500, JoeB wrote: At 12:03 PM 1.12.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 12:01:44PM -0600, Jack L. Stone wrote: At 05:44 PM 1.11.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 11:31:22AM -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? /usr/src/UPDATING says: 20021110: The definitions of the standard file streams (stdio, stdout, and stderr) have changed so that they are no longer compile-time constants. Some older binaries may require updated 3.X compatability libraries (for example, by setting COMPAT3X=yes for a buildworld/installworld). Alternatively to doing a buildworld with COMPAT3X=yes, you could install the misc/compat3x port. Good grief! I read the UPDATING as always, but this one did NOT sink in! Thank you so much for pointing me in the right direction before I shot myself in the foot If I go the misc/compat3x port route, I assume I need to redo the buildword?? If so, then I might as well include the COMPAT3X=yes in the make.conf. All that setting COMPAT3X=yes does is cause the buildworld process to uudecode and install some precompiled copies of FreeBSD-3.x shared libraries --- see /usr/src/lib/compat/compat3x.i386 for what's available. Those libraries were originally just copied off a 3.x machine, but since then kernel changes in 4.x or 5.0 have meant that certain changes have had to be back ported to RELENG_3 in order to maintain compatibility between the 3.x shlibs and the kernel. Supplying those libraries by installing the port achieves exactly the same effect, but quicker. However, the choice is entirely up to you. In the long run, putting COMPAT3X into /etc/make.conf would be my choice, as my regular schedule of buildworlds would ensure everything was up to date. Once the 3.x shlibs are in place, the binary frontpage binary supplied with the apache-fp port should pick them up OK. The interface between the 3.x shlibs and any applications linked to them should remain exactly the same. Cheers, Matthew Matthew, thanks again for the reply. However, I've tried both methods of the compat3x on a test server, including and whole new build/installworld and the latest 4.7-STABLE still hoses FrontPage. I even deleted and started from scratch on Apache+FP-1.27, but the FP install stops dead at trying to chown the uid:gid on the root web and gives the same error: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 This caught me by surprise because I'd had FP running fine with FBSD-4.7 (RELEASE and STABLE) on other servers, but it was the installs JUST prior to the change date of 20021110. In fact they where only 5 days earlier. FP still doesn't understand what's going on apparently. Backing down to the installs prior to 20021110 makes FP happy again. Unfortunately, until I figure out the cure, I can't track 4.7-STABLE. As much as it is a pain, I must run FP for the users. No doubt others running FP must have seen this by now nothing else is affected and 4.7-STABLE runs fine otherwise (tried several machines). Any other thoughts, Matthew or from anyone much appreciated. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jack L. Stone Sent: Sunday, January 12, 2003 10:56 AM To: Matthew Seaman; [EMAIL PROTECTED] Subject: Re: Apache_fp Port install problem Jack: Last Thursday I installed apache-fp from the ports collection on newly installed FBSD 4.7 box and it installed without any problems. But remember a clean install also installs a clean copy of all the frontpage pre-rec's which COMPAT3X is one. If I remember correctly you also have a lot of other mods on apache-fp and that may have messed up the COMPAT3X version you though you were using. All I am saying is as of 1/09/03 the apache-fp port
Re: Apache_fp Port install problem
On Sat, Jan 11, 2003 at 11:31:22AM -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? /usr/src/UPDATING says: 20021110: The definitions of the standard file streams (stdio, stdout, and stderr) have changed so that they are no longer compile-time constants. Some older binaries may require updated 3.X compatability libraries (for example, by setting COMPAT3X=yes for a buildworld/installworld). Alternatively to doing a buildworld with COMPAT3X=yes, you could install the misc/compat3x port. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Apache_fp Port install problem
At 05:44 PM 1.11.2003 +, Matthew Seaman wrote: On Sat, Jan 11, 2003 at 11:31:22AM -0600, Jack L. Stone wrote: I just updated from FBSD-4.5 to 4.7 on a server running apache_fp.1.26. The update somehow has broken the FP extensions (ugh!). I have tried a number of fixes, including portupgrade, but get a checksum error there. Have tried to rerun the present install of FP using fp_install.sh, but get this error: Who should own web root web on port 80 [www]: What should the group for web root web on port 80 be [www]: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp ERROR: Unable to chown web root web in port 80 Hit enter to continue I'm also seeing the __stderrp error in my httpd-error.log whenever I try to login to FP. So, something has changed in the FBSD-4.5-4.7 update and I've never seen this error, so don't know what needs to be fixed. I have another server running apache_fp.1.27 on FBSD.4.7 just fine. It's looking like an uninstall/reinstall completely for apache+fp didn't want to have to do that on a box with a bunch of virtual hosts. Has anyone seen the above problem on similar installs...??? /usr/src/UPDATING says: 20021110: The definitions of the standard file streams (stdio, stdout, and stderr) have changed so that they are no longer compile-time constants. Some older binaries may require updated 3.X compatability libraries (for example, by setting COMPAT3X=yes for a buildworld/installworld). Alternatively to doing a buildworld with COMPAT3X=yes, you could install the misc/compat3x port. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Good grief! I read the UPDATING as always, but this one did NOT sink in! Thank you so much for pointing me in the right direction before I shot myself in the foot If I go the misc/compat3x port route, I assume I need to redo the buildword?? If so, then I might as well include the COMPAT3X=yes in the make.conf. Sorry, a little dense after 3 hours sleep Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
