atom feed22 messages in org.freebsd.freebsd-currentRe: ELF ldconfig
FromSent OnAttachments
Joe AbleySep 19, 1998 9:27 am 
Terry LambertSep 19, 1998 10:24 am 
Joe AbleySep 19, 1998 10:38 am 
Joe AbleySep 19, 1998 10:45 am 
Terry LambertSep 19, 1998 10:49 am 
John PolstraSep 19, 1998 1:32 pm 
Joe AbleySep 19, 1998 4:16 pm 
Mark HuizerSep 19, 1998 4:36 pm 
Joe AbleySep 19, 1998 6:33 pm 
Dan NelsonSep 19, 1998 8:13 pm 
David HollandSep 19, 1998 9:00 pm 
Joe AbleySep 19, 1998 10:02 pm 
Peter WemmSep 20, 1998 12:50 am 
Terry LambertSep 20, 1998 2:29 am 
Terry LambertSep 20, 1998 2:48 am 
David HollandSep 20, 1998 10:55 am 
David HollandSep 20, 1998 11:04 am 
Terry LambertSep 20, 1998 2:24 pm 
David HollandSep 20, 1998 4:39 pm 
Terry LambertSep 21, 1998 1:17 am 
David HollandSep 21, 1998 11:30 am 
David HollandSep 24, 1998 1:58 pm 
Subject:Re: ELF ldconfig
From:Mark Huizer (free@xaa.iae.nl)
Date:Sep 19, 1998 4:36:12 pm
List:org.freebsd.freebsd-current

The ELF hints file is built by sbin/ldconfig/elfhints.c, which is very particular about the files in the search path it will include - for example, in /usr/local/lib, libslang.so.1.2.2 is built by the slang port, but no link under the name libslang.so.1 is present.

It is intentional that the ELF ldconfig ignores libraries with more than one version number. The problem you're seeing is simply caused by the fact that the libslang port hasn't been updated yet for ELF. See the conversion guidelines for more details:

http://www.freebsd.org/~asami/elf-guidelines.txt

Well, I started looking for it alright, but it seems a bit rude to me to just make it libslang.1, and considering that the libslang makefile is talking about elf major and minor version numbers, I got confused a little :-) does elf except only major, or is that a FreeBSD specific thing, or what? And why doesn't it matter when versions get upgraded and all?

Mark

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message