Date: Mon, 17 Oct 2016 14:56:32 -0700 From: Oleksandr Tymoshenko <gonzo@bluezbox.com> To: Shankar Giri Venkita Giri <girivs@gmx.com> Cc: freebsd-arm@freebsd.org Subject: Re: XDEV fix Message-ID: <685F6317-A439-48A0-9D0C-07C0C47E1D99@bluezbox.com> In-Reply-To: <trinity-a3f6b891-b412-4c2f-99a4-703cecc8e02a-1476685734719@3capp-mailcom-bs03> References: <trinity-a3f6b891-b412-4c2f-99a4-703cecc8e02a-1476685734719@3capp-mailcom-bs03>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Oct 16, 2016, at 11:28 PM, Shankar Giri Venkita Giri = <girivs@gmx.com> wrote: >=20 > XDEV has been broken for a while in FreeBSD 11. As of today, I had to = perform minimal patches to get it to build successfully. Can someone = review this and try it out to make sure? > Also clang being a native cross-compiler, I was wondering if XDEV had = specific advantages. Hi Shankar, Thanks for submitting the patch. But I am afraid it fixes symptoms, and not the cause of the problem. Actually there are multiple problems. clang-based xdev is broken due to this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213217 gcc-based xdev (I've just checked sparc64) is broken for another reason I have no idea about so far. Both failures are in sysroot part of xdev (libraries) Some time ago I suggested to get rid of sysroot part and reduce it down to cross-toolchain: compiler + binutils. Although system clang in theory can act as a cross-comipler it's useless without binutils: = https://lists.freebsd.org/pipermail/freebsd-arch/2016-October/018000.html Since you're probably the only person other than me who uses xdev I am interested in hearing about your use case. May be it's easier to move cross-toolchain part to packages and get rid of xdev altogether.=20=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?685F6317-A439-48A0-9D0C-07C0C47E1D99>