Date: Thu, 18 Aug 2016 13:29:54 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: "O'Connor, Daniel" <darius@dons.net.au> Cc: Peter Jeremy <peter@rulingia.com>, freebsd current <freebsd-current@freebsd.org> Subject: Re: Somethign missing in my environment? Message-ID: <fbb13aa0-8be1-7bd8-bb1c-97924010d200@digiware.nl> In-Reply-To: <090825B1-6195-4DEE-BEDD-D8DE595C5B85@dons.net.au> References: <a0e01113-1ce2-6081-e6b2-74d511e07241@digiware.nl> <20160816203324.GJ65184@server.rulingia.com> <d5d8697f-a8b7-dc82-1729-46c5c0788cd6@digiware.nl> <20160817193950.GB22564@server.rulingia.com> <0a2a88a5-2064-135f-a4fa-3b4162f9698d@digiware.nl> <090825B1-6195-4DEE-BEDD-D8DE595C5B85@dons.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18-8-2016 00:56, O'Connor, Daniel wrote: > >> On 18 Aug 2016, at 06:12, Willem Jan Withagen <wjw@digiware.nl> wrote: >> >>> There's nothing immediately obvious. I suggest trying without the >>> "-DNOCLEAN -DNO_CLEAN" - they are shortcuts that aren't guaranteed to >>> work under all circumstances. And if that still fails, skip the '-j8' >>> because it's possible there are still race conditions in buildworld >>> (though that is very unlikely). >> >> Been there, done that, in all kinds of variations, but no go. >> >> Where should is definition normally come from? >> /usr/obj/usr/srcs/head/src/tmp/usr/lib/libgcc_s.so: undefined reference >> to `__gxx_personality_v0' >> cc: error: linker command failed with exit code 1 (use -v to see invocation) >> *** [h_raw.full] Error code 1 >> >> Or should it be available in libgcc_s.so, and did it not get include in >> a bizare way.... > > Remove NO_CLEAN et al and delete /usr/obj/* then try again. It is running single thread, but compiling clang is a rather hefty build. > Has it ever worked for you? When did it stop? What changed then? Ehhh, mmmm, having asked customers that question plenty of time. I give the answer reluctantly... But it has been working on this server from the day I installed it, which is somewhere around end of 2013. last time I used it was around May this year, to get a then uptodate current. Now I want to go forward again, but this was the result. I could/will try to build it on another amd64 server and install from there. --WjW --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fbb13aa0-8be1-7bd8-bb1c-97924010d200>