Matthias Apitz <[email protected]> writes: > El día Tuesday, June 11, 2013 a las 06:23:47AM -0300, Raphael Kubo da Costa > escribió: > >> Anyway, I suspect it's related to kdepimlibs4 and friends. I've tried >> to reproduce it here with -CURRENT and clang but everything work >> fine. What FreeBSD version are you running, and which compiler are you using? > > On what architecture you have tested it, amd64 or i386? I have setup a > new empty VM with -CURRENT and ports from SVN with i386 and the > compilation of certain parts of KDE fail with SIGSEGV of automoc4.
amd64, I normally don't have any i386 systems around, and the tinderbox swills recently created for me is also an amd64 installation. I could try to set up a new i386 VM, but it takes time. Do you have an i386 box I could have access to? > Do you want to see a complete nohup.out? See also the issue re/ > automoc4 in our bucktracing. I'll reply in that thread. I have an AMD64 as well. Tell me what commands you want me to issue and I'll send the output to the list. FreeBSD foo.bar.com 9.1-STABLE FreeBSD 9.1-STABLE #1 r250333: Tue May 7 22:30:37 CDT 2013 [email protected]:/usr/obj/usr/src/sys/foobar amd64 clang -v FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 Target: x86_64-unknown-freebsd9.1 Thread model: posix _______________________________________________ kde-freebsd mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
