Hi,

I'm trying to figure out why my 10.0-CURRENT machine is having issues producing 
*.so shared library...

[659] > uname -a
FreeBSD dx.burplex.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248165: Mon Mar 11 
18:20:30 PDT 2013     r...@dx.burplex.com:/usr/obj/usr/src/sys/FURAHA  amd64

checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... no

creating libtool
appending configuration tag "CXX" to libtool
checking whether the clang++ linker (/usr/bin/ld) supports shared libraries... 
no
checking whether the clang++ linker (/usr/bin/ld) supports shared libraries... 
no
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... unsupported

[660] > pkg version | grep libtool
libtool-2.4.2                      =



(as example) my 9.1-STABLE machine is working OK. 

# uname -a
FreeBSD do.burplex.com 9.1-STABLE FreeBSD 9.1-STABLE #0 r246923M: Sun Feb 17 
18:30:48 PST 2013     da3m0n8...@do.burplex.com:/usr/obj/usr/src/sys/KAGISO  
amd64

checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... freebsd9.1 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes

# pkg_info | grep libtool
libtool-2.4.2       Generic shared library support script



I kind of remember running into this in the past but I can't recall the 
solution.. 

Help or pointers appreciated!

Thank you,

-- 
Waitman Gobble
San Jose California USA
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to