Date: Thu, 2 Feb 2012 11:57:59 -0500 From: Pierre-Luc Drouin <pldrouin@pldrouin.net> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Clang and ports Message-ID: <CANT0rcvz0%2BRzM7OTbsE7OxNswMiy5_EzheqbZeYRrrK-f-uCcg@mail.gmail.com> In-Reply-To: <4F2A3E0F.6060707@gmail.com> References: <4F2A3E0F.6060707@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 2, 2012 at 2:41 AM, Joshua Isom <jrisom@gmail.com> wrote: > I know that build cluster lists some ports that have problems with clang, > but it doesn't say if they're tested or not. I set up a clang jail to test > out things before switching to clang for general use. When I try running > mencoder to encode a file to x264, it seg faults. Changing options doesn't > change anything. A gdb backtrace points to x264 being the problem. > Everything compiles and installs, but the build's useless. Is clang ready > for ports, or is it only safe for kernel/world? > ______________________________**_________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions<http://lists.freebsd.org/mailman/listinfo/freebsd-questions>; > To unsubscribe, send any mail to "freebsd-questions-** > unsubscribe@freebsd.org <freebsd-questions-unsubscribe@freebsd.org>" > I noticed that anything that uses Java does not work when the FreeBSD world is built with clang, because Java does not like something about vsnprintf in libc as generated by Clang and it causes it to always seg fault (at least on i386). I posted a PR about this: http://www.freebsd.org/cgi/query-pr.cgi?pr=164637
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANT0rcvz0%2BRzM7OTbsE7OxNswMiy5_EzheqbZeYRrrK-f-uCcg>