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
On Sun, Jan 17, 2010 at 14:04, Kostik Belousov kostik...@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?
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
