On Fri, Dec 20, 2019 at 04:26:41PM -0500, Ryan Stone wrote:
> I've noticed that on head, if I directly execute rtld to run an
> executable, AT_EXECPATH contains the path to rtld on head (on
> 12.0-RELEASE it will contain nothing). This is causing me a problem
> because clang uses AT_EXECPATH to pr
On Fri, 20 Dec 2019 at 16:26, Ryan Stone wrote:
>
> I've noticed that on head, if I directly execute rtld to run an
> executable, AT_EXECPATH contains the path to rtld on head (on
> 12.0-RELEASE it will contain nothing). This is causing me a problem
> because clang uses AT_EXECPATH to preferentia
Isn’t rtld’s behavior here correct? It’s really Clang which is doing
something quite odd.
On Fri, Dec 20, 2019 at 13:27 Ryan Stone wrote:
> I've noticed that on head, if I directly execute rtld to run an
> executable, AT_EXECPATH contains the path to rtld on head (on
> 12.0-RELEASE it will conta
I've noticed that on head, if I directly execute rtld to run an
executable, AT_EXECPATH contains the path to rtld on head (on
12.0-RELEASE it will contain nothing). This is causing me a problem
because clang uses AT_EXECPATH to preferentially locate where it's
installed, which it uses to locate it
On Fri, Dec 20, 2019 at 10:15 AM Konstantin Belousov
wrote:
>
> On Fri, Dec 20, 2019 at 09:51:15AM -0800, Ryan Libby wrote:
> > On Fri, Dec 20, 2019 at 9:31 AM Konstantin Belousov
> > wrote:
> > >
> > > On Fri, Dec 20, 2019 at 09:24:00AM -0800, John Baldwin wrote:
> > > > On 12/19/19 12:06 PM, R
On Fri, Dec 20, 2019 at 09:51:15AM -0800, Ryan Libby wrote:
> On Fri, Dec 20, 2019 at 9:31 AM Konstantin Belousov
> wrote:
> >
> > On Fri, Dec 20, 2019 at 09:24:00AM -0800, John Baldwin wrote:
> > > On 12/19/19 12:06 PM, Ryan Libby wrote:
> > > > On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrot
On Fri, Dec 20, 2019 at 9:31 AM Konstantin Belousov wrote:
>
> On Fri, Dec 20, 2019 at 09:24:00AM -0800, John Baldwin wrote:
> > On 12/19/19 12:06 PM, Ryan Libby wrote:
> > > On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
> > >>
> > >> In the interest of supporting newer versions of GCC for
On Fri, Dec 20, 2019 at 09:24:00AM -0800, John Baldwin wrote:
> On 12/19/19 12:06 PM, Ryan Libby wrote:
> > On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
> >>
> >> In the interest of supporting newer versions of GCC for a base system
> >> toolchain, I've renamed the external GCC packages fro
On 12/19/19 12:06 PM, Ryan Libby wrote:
> On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
>>
>> In the interest of supporting newer versions of GCC for a base system
>> toolchain, I've renamed the external GCC packages from -gcc
>> to -gcc6. These are built as flavors of a new devel/freebsd-g
