Date: Mon, 13 Jan 2003 17:48:40 -0500 From: "JoeB" <barbish@a1poweruser.com> To: "G D McKee" <freebsd@gdmckee.com>, "Jack L. Stone" <jackstone@sage-one.net>, "Matthew Seaman" <m.seaman@infracaninophile.co.uk>, <freebsd-questions@FreeBSD.ORG> Subject: RE: Apache_fp Port install problem Message-ID: <MIEPLLIBMLEEABPDBIEGEEGEDDAA.barbish@a1poweruser.com> In-Reply-To: <001301c2bb51$dfc6ad80$c800a8c0@p1000>
next in thread | previous in thread | raw e-mail | index | archive | help
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: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of G D McKee Sent: Monday, January 13, 2003 5:20 PM To: barbish@a1poweruser.com; Jack L. Stone; Matthew Seaman; freebsd-questions@FreeBSD.ORG 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" <barbish@a1poweruser.com> To: "Jack L. Stone" <jackstone@sage-one.net>; "Matthew Seaman" <m.seaman@infracaninophile.co.uk>; <freebsd-questions@FreeBSD.ORG> Sent: Sunday, January 12, 2003 5:02 PM Subject: RE: Apache_fp Port install problem > At 12:03 PM 1.12.2003 +0000, Matthew Seaman wrote: > >On Sat, Jan 11, 2003 at 12:01:44PM -0600, Jack L. Stone wrote: > >> At 05:44 PM 1.11.2003 +0000, 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: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Jack L. > Stone > Sent: Sunday, January 12, 2003 10:56 AM > To: Matthew Seaman; freebsd-questions@FreeBSD.ORG > 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 with windows frontpage client. > > Later Joe > > > > > > > > Best regards, > Jack L. Stone, > Administrator > > SageOne Net > http://www.sage-one.net > jackstone@sage-one.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MIEPLLIBMLEEABPDBIEGEEGEDDAA.barbish>