Good evening,
I am observing that doing a buildworld on stable (r202448) with
WITH_CTF=1 breaks /usr/libexec/cc1plus on my amd64. Doing so causes
cc1plus to crash with internal errors and ports like devel/popt don't
even make it through the configure stage ("fails sanity check").
Is this behaviour expected? Is it discouraged to build world WITH_CTF?
Regards.
Riggs
On Sun, Jan 17, 2010 at 12:54:41AM +0100, Thomas Zander wrote:> Good evening, > > I am observing that doing a buildworld on stable (r202448) with > WITH_CTF=1 breaks /usr/libexec/cc1plus on my amd64. Doing so causes > cc1plus to crash with internal errors and ports like devel/popt don't > even make it through the configure stage ("fails sanity check"). > Is this behaviour expected? Is it discouraged to build world WITH_CTF?WITH_CTF=1 results in the broken static binaries after strip(1). Do not use it (yet) for buildworld. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100117/61cf1ba7/attachment.pgp
On Sun, Jan 17, 2010 at 14:04, Kostik Belousov <kostikbel@gmail.com> wrote:> WITH_CTF=1 results in the broken static binaries after strip(1). > Do not use it (yet) for buildworld.Thank you, I must have missed this somehow. Is it maybe worth a footnote in the handbook? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/dtrace-enable.html Regards, Riggs