Date: Mon, 18 May 2015 15:34:05 -0700 From: NGie Cooper <yaneurabeya@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: Craig Rodrigues <rodrigc@freebsd.org>, George Neville-Neil <gnn@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, "freebsd-testing@freebsd.org" <testing@freebsd.org> Subject: Re: External toolchain build failing due to missing --sysroot Message-ID: <CAGHfRMAnTuwJZqvSPL4bZj3ZM9iGtLHgKo%2BGziyQ0xiqvKTOzg@mail.gmail.com> In-Reply-To: <C4873476-AE95-4A74-87A2-842CB616B3D6@bsdimp.com> References: <CAG=rPVfDZUV5c5b9wNWuG5BkN4xrT-r3pofm%2Brst74FD5kMYYQ@mail.gmail.com> <146A0A16-F33B-42AF-A8D5-B1D16775A409@bsdimp.com> <CAG=rPVdWSa-69Mf0W0x=9bx3ekGs_QKJpqdeSd=GMCBO5kUKAw@mail.gmail.com> <C4873476-AE95-4A74-87A2-842CB616B3D6@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 18, 2015 at 1:27 PM, Warner Losh <imp@bsdimp.com> wrote: > >> On May 18, 2015, at 2:02 PM, Craig Rodrigues <rodrigc@FreeBSD.org> wrote= : >> >> On Mon, May 18, 2015 at 12:30 PM, Warner Losh <imp@bsdimp.com> wrote: >> >> > On Mar 20, 2015, at 2:10 PM, Craig Rodrigues <rodrigc@FreeBSD.org> wro= te: >> > >> > Warner, >> > >> > I can't get the external toolchain build of CURRENT to work, >> > because --sysroot seems to be missing in some places. >> >> I don=E2=80=99t believe that this has actually never worked, or if it di= d appear >> to work, it was only by accident. We have no ability to generate a >> proper sysroot in the tree today, though we do come close at points. >> Sean Bruno has been reporting issues with libgcc and external >> toolchains for months, and I=E2=80=99ve not had the time to track those >> issues to ground. >> >> It seems to work now. See: >> https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-April/001660.= html > > It is quite fragile though. It looks like you are using it in one of the > configurations that work (hence my accidental comment). But working > in some configurations is better than it has been in the past... I'm dealing with this to some extent at $work. Hardcoding paths to libraries proved to be a painpoint, along with some of the linker script stuff that was introduced recently: $ ls -l /usr/lib/libnv.so lrwxr-xr-x 1 root wheel 15 Apr 9 12:45 /usr/lib/libnv.so -> /lib/libnv.= so.0 $ cat /usr/lib/libc.so /* $FreeBSD$ */ GROUP ( /lib/libc.so.7 /usr/lib/libc_nonshared.a /usr/lib/libssp_nonshared.= a ) These paths are extremely fixed because they're hardcoded... You can sort of kind of use --sysroot=3D, but there's a lot of gymnastics I'm having to go through reinventing the wheel from past experience with embedded Linux... Thanks, -NGie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGHfRMAnTuwJZqvSPL4bZj3ZM9iGtLHgKo%2BGziyQ0xiqvKTOzg>