On Thu Nov 3 11, Matthias Apitz wrote: > El día Thursday, November 03, 2011 a las 11:28:47AM +0000, Alexander Best escribió: > > > > It turns out that the problem is more general! A lot of ./configure > > > scripts are detecting in 10-CUR that they can't or should not build > > > shared libs; the problem is that the OS is detected now as > > > > > > host_os: freebsd10.0 > > > > > > and the ./configure scripts have tests like this: here's my config.log after building and installing security/p11-kit. i have edited my newvers.sh according to UPDATING and uname -a now properly reports: FreeBSD otaku 9.9-CURRENT FreeBSD 9.9-CURRENT #9: Thu Nov 3 11:41:08 CET 2011 arundel_at_otaku:/usr/obj/usr/git-freebsd-head/sys/ARUNDEL amd64 still for me the issue remains: no libs get built and thus not installed! cheers. alex > > > > > > ports/audio/jack/work/jack-audio-connection-kit-0.121.3: > > > > > > case $host_os in > > > ... > > > freebsd1*) > > > dynamic_linker=no > > > ;; > > > ... > > > > > > And now? I'm cluesless now how we could solve this :-( > > > > are you sure this issue is related to the freebsd1* case? > > I can only comment what I saw: > > - OS was detected as freebsd10.0 (I inserted a 'echo $host_os' into the > ./configure script > > - ./configure said that it should/will not build shared libs > > - the *.so* were missing in ports/audio/jack/work/... and in > /usr/local/lib > > I will remove all /usr/ports/* and /usr/local/* and /var/db/pkg/* and > will start from scratch with "cvs checkout" and will set UNAME_r as > explained in ports/UPDATING; > > will let you know the result > > matthias > > -- > Matthias Apitz > e <guru_at_unixarea.de> - w http://www.unixarea.de/ > UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) > UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:19 UTC