03.02.2013 15:28, Dimitry Andric:
Thanks for trying this out. Is there also a list of ports that *do*
compile (and hopefully run) successfully? :-)
I already switched to libc++ on my unstable STABLE-9 machines. Currently
I'm using this config:
*: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++
audio/flac databases/db5 devel/binutils devel/doxygen devel/qt4-designer
devel/qt4-qt3support devel/qt4-script devel/yasm graphics/libopenraw
graphics/tesseract lang/gcc multimedia/phonon-gstreamer
net-p2p/transmission-cli net-p2p/transmission-daemon
sysutils/smartmontools textproc/hunspell www/qt4-webkit
x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS
databases/mariadb-client emulators/pearpc www/libxul
x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS
www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS
Currently I have working seamonkey and slim built this way.
> ldd `which seamonkey`
/usr/local/bin/seamonkey:
libm.so.5 => /lib/libm.so.5 (0x800846000)
libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x800a65000)
libc++.so.1 => /usr/lib/libc++.so.1 (0x800c7e000)
libthr.so.3 => /lib/libthr.so.3 (0x800f34000)
libc.so.7 => /lib/libc.so.7 (0x801156000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x8014a5000)
I can post whole list of packages if anyone is interested. Everything
looks even better then when clang was introduced to ports - almost any
package works, the ones that doesn't just have a complicated
build/install process. No painful glitches yet.
--
Sphinx of black quartz, judge my vow.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
