Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Jun 2015 03:02:14 -0700
From:      NGie Cooper <yaneurabeya@gmail.com>
To:        Dimitry Andric <dim@freebsd.org>
Cc:        Baptiste Daroussin <bapt@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>,  "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>,  "src-committers@freebsd.org" <src-committers@freebsd.org>
Subject:   Re: svn commit: r284898 - in head: . share/mk
Message-ID:  <CAGHfRMAxMv1L-sDwyRt7=DyRkZx4D1hohPtA%2B-1F786FpEu5-A@mail.gmail.com>
In-Reply-To: <FC14665C-B3BF-4353-A815-B934347FF092@FreeBSD.org>
References:  <201506272328.t5RNSvQS063168@svn.freebsd.org> <260A448A-7195-49E6-8CCD-9F0753B61A18@gmail.com> <20150628074103.GA68142@ivaldir.etoilebsd.net> <CAGHfRMAW3D8Y69iQefSYQJ=kk1UdZMg3v6Kp-FoWFtLg5BXM3w@mail.gmail.com> <20150628074931.GB68142@ivaldir.etoilebsd.net> <CAGHfRMCy5teyWJ22ZKkNVW=-tXoHdB0Ck%2BsYcrFcm_RY7-e6Og@mail.gmail.com> <20150628085714.GC68142@ivaldir.etoilebsd.net> <FC14665C-B3BF-4353-A815-B934347FF092@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 28, 2015 at 2:48 AM, Dimitry Andric <dim@freebsd.org> wrote:
> On 28 Jun 2015, at 10:57, Baptiste Daroussin <bapt@FreeBSD.org> wrote:
>>
>> On Sun, Jun 28, 2015 at 01:44:21AM -0700, NGie Cooper wrote:
>>> On Sun, Jun 28, 2015 at 12:49 AM, Baptiste Daroussin <bapt@freebsd.org> wrote:
>>> ...
>>>> Not at all I have this on a both where I haven't yet r284898 iirc it is like
>>>> this since the beginning I do not remember seeing those ld scripts with absolute
>>>> path.
>>>
>>> $ cat /usr/lib/libc.so
>>> /* $FreeBSD$ */
>>> GROUP ( /lib/libc.so.7 /usr/lib/libc_nonshared.a /usr/lib/libssp_nonshared.a )
>>> $ what -q /boot/GENERIC.r283337+9c333ed/kernel
>>> FreeBSD 11.0-CURRENT #4 r283337+9c333ed(isilon-atf): Tue May 26
>>> 21:49:09 PDT 2015
>>
>> Yes you are right, I was looking at the wrong place.
>
> What is actually the perceived problem with having paths in those linker
> scripts?  If you use --sysroot, the libraries are searched relative to
> that sysroot, right?
>
> (And yes, I know our gcc's sysroot implementation is broken.  So please
> fix that instead. :-)

Our version of ports at $work doesn't understand --sysroot, yet. If
it's fixed with --sysroot, great! This is a non-issue. If not, then
this is still a problem...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGHfRMAxMv1L-sDwyRt7=DyRkZx4D1hohPtA%2B-1F786FpEu5-A>