RE: libc.so.4 not found
It's a normal part of PHK malloc, the standard FreeBSD malloc. It's for turning on certain debugging options. PHK used a cute trick with symlinks to avoid having to actually open a configuration file. See malloc(3). Jason Young Access US Chief Network Engineer -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Leif Neland Sent: Wednesday, November 29, 2000 4:23 PM To: Kris Kennaway Cc: [EMAIL PROTECTED] Subject: Re: libc.so.4 not found On Sat, 25 Nov 2000, Kris Kennaway wrote: On Sat, Nov 25, 2000 at 10:28:53PM +0100, Leif Neland wrote: Could this be the reason why Avp (virusscanner) for FreeBSD 4X just dumps core on Fbsd current? It works on a Fbsd stable. Could be malloc.conf defaults. i.e. a bug in avp triggered by the debugging /etc/malloc.conf settings in -current. Kris A truss shows Avp tries to open /etc/malloc.conf, but I have no such file on any of my systems, stable or current. But Avp continues after this failure. Do I need /etc/malloc.conf? Where do I find one? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libc.so.4 not found
On a fresh hard drive I installed 5.0 20001123 Current and got the following after installation: Local package initialization:/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found I tried again from scratch with 5.0 20001124 Current and have the same problem. This affects emacs, apache, and unfortunately cvsup I have played with some symbolic links with no luck. This came from reading- http://www.freebsd.org/handbook/linuxemu-lbc-install.html#LINUXEMU-LIBS-PORT but I don't think this has anything to do with Linux Binary Compatibility. This was the closes I came when searching on ld-elf.so.1 and libc.so.4 Note the only change between my 11/23 and 11/24 install was I added Netscape Communicator 4.74 and got- xfree86-aoutlibs-3.3.3 installation aborted error code 1 Any ideas on the libc? Derek To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
On Sat, Nov 25, 2000 at 12:18:43AM -0800, Derek Schene' wrote: On a fresh hard drive I installed 5.0 20001123 Current and got the following after installation: Local package initialization:/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found we bumped the libc version to 5, but we didn't make compat4 libaries available for installation yet. I'll renew my annoyance with the fact that we just bumped this without even figuring out why things broke or if we could change them in a way to save functionality without having to bump the version number[1]. We also never propogated this bump to RELENG_4, so the release shipped with the worst of both worlds. To answer your question, though: I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible should happen. This should work until we get our act together regarding this change. -- Bill Fumerola - security yahoo / Yahoo! inc. - [EMAIL PROTECTED] / [EMAIL PROTECTED] 1. to my knowledge. I tried to keep up on this thread but its possible someone figure it out and we just didn't revert the libc bump. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
On Sat, Nov 25, 2000 at 02:44:08AM -0600, Bill Fumerola wrote: On Sat, Nov 25, 2000 at 12:18:43AM -0800, Derek Schene' wrote: On a fresh hard drive I installed 5.0 20001123 Current and got the following after installation: Local package initialization:/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found we bumped the libc version to 5, but we didn't make compat4 libaries available for installation yet. In this case it doesn't matter -- "a fresh hard drive" and "local package" implies that the -current packages on ftp.freebsd.org haven't been built since the bump and are thus slightly out dated. I'll renew my annoyance with the fact that we just bumped this without even figuring out why things broke or if we could change them in a way to save functionality without having to bump the version number[1]. It doesn't matter as at least Garrett has some changes he's going to make that aren't compatible. libc.so will be at least at version "5" in FreeBSD 5.0, so we'll have to go thru this pain eventually anyway. We also never propagated this bump to RELENG_4, so the release shipped with the worst of both worlds. Huh? Why the worst of both worlds?? To answer your question, though: I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible should happen. This should work until we get our act together regarding this change. I'm not quite sure what isn't together other than no compat4x libc.so.4 yet -- I can certainly create one, but I'll have to update it for the libc.so.4 in 4.3 and 4.4. Don't forget the compat libs are uuencoded files, so CVS will see large diffs. If people don't mind, I'll certainly make the compat libs now. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
Could this be the reason why Avp (virusscanner) for FreeBSD 4X just dumps core on Fbsd current? It works on a Fbsd stable. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
On Sat, Nov 25, 2000 at 12:44:34PM -0600, Bill Fumerola wrote: Huh? Why the worst of both worlds?? Incompatible changes AND no way to differentiate between the two. (plus we don't even know what changed it, so we have no way of telling people "your libc before X won't work with binarys that use the frobozz() interface) There wasn't an incompatible change. There is too much confusion on this issue. There were two things that caused a problem. 1. a bug in libc_r such that programs that ran before, crashed. 2. a 4.1.1-RELEASE libc.so.4 was being used on a 4.0-RELEASE system. #1 just showed off incorrect application code. #2 has never been officially supported. People who have binaries they can't recompile will need them. The fact that it pains our CVS tree really isn't an issue to me, This is -current, so people should be able to deal with the issue. I'll probably put a 4.2-RELEASE libc.so.4 up for people to download and put in /usr/lib/compat manually. I'd like to think we have software engineering that utilizes source code management, and not the other way around. I would like to think that way too -- but that isn't the truth. As I said, I'm willing to commit a compat lib now, but I don't want any crap when I update it and the diff is the size of the file itself. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
I am not sure, if anybody care for this fix, but I just copied libc.so.5 to libc.so.4 when kde was complaining about not finding it. I am not sure if this should work, but it does work just fine... JAn On Sat, 25 Nov 2000, David O'Brien wrote: On Sat, Nov 25, 2000 at 12:44:34PM -0600, Bill Fumerola wrote: Huh? Why the worst of both worlds?? Incompatible changes AND no way to differentiate between the two. (plus we don't even know what changed it, so we have no way of telling people "your libc before X won't work with binarys that use the frobozz() interface) There wasn't an incompatible change. There is too much confusion on this issue. There were two things that caused a problem. 1. a bug in libc_r such that programs that ran before, crashed. 2. a 4.1.1-RELEASE libc.so.4 was being used on a 4.0-RELEASE system. #1 just showed off incorrect application code. #2 has never been officially supported. People who have binaries they can't recompile will need them. The fact that it pains our CVS tree really isn't an issue to me, This is -current, so people should be able to deal with the issue. I'll probably put a 4.2-RELEASE libc.so.4 up for people to download and put in /usr/lib/compat manually. I'd like to think we have software engineering that utilizes source code management, and not the other way around. I would like to think that way too -- but that isn't the truth. As I said, I'm willing to commit a compat lib now, but I don't want any crap when I update it and the diff is the size of the file itself. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
Thanks for everyone's input, I feel I'm getting closer and see where my previous thinking had gone wrong. I tried this- I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible should happen. and now when booting get- Local package initialization:fopen: No such file or directory So I copied libc.so.4 from the 4.0 livefile cdThis gave the same message (also had a core dump but may be unrelated). But the good news is now emacs, cvsup, etc. are working. I don't know if this matters but when looking at- implies that the -current packages on ftp.freebsd.org haven't been built since the bump and are thus slightly out dated. I'm thinking the snapshot came from current.freebsd.org? (SNAP5) And when it was mentioned- 2. a 4.1.1-RELEASE libc.so.4 was being used on a 4.0-RELEASE system. I thought I may have problems with using 4.0-RELEASE libc.so.4 on a 5.0-CURRENT system and may be better going with the symlink to libc.so.5? or look for a 4.2-RELEASE libc.so.4 up for people to download and put in /usr/lib/compat manually.? Thanks, Derek To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
On Sat, Nov 25, 2000 at 03:34:49PM -0800, Derek Schene' wrote: I tried this- I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible should happen. Since nothing has changed in the -CURRENT libc yet, this will work. BTW, you'd want to do the same for libc_r.so.4. Local package initialization:fopen: No such file or directory I would go into /usr/local/etc/rc.d/ and try to figure out *which* binary is causing all the trouble so the problem can be efficiently debugged. At this point you're skating around the problem rather than just hit it head on. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
On Sat, Nov 25, 2000 at 10:28:53PM +0100, Leif Neland wrote: Could this be the reason why Avp (virusscanner) for FreeBSD 4X just dumps core on Fbsd current? It works on a Fbsd stable. Could be malloc.conf defaults. i.e. a bug in avp triggered by the debugging /etc/malloc.conf settings in -current. Kris PGP signature
