* Steve Ellcey:
> I am not sure, but my guess is that it is because I am building
> binutils (including ld) using --with-sysroot.
That could be the case. I guess there are two conflicting use cases for
sysroots, one where you want to mangle run-time paths to confine things
to the sysroot, and on
On Thu, 2019-10-10 at 15:38 -0300, Tulio Magno Quites Machado Filho wrote:
>
> > Let me first describe what I do now:
> >
> > configure/build BINUTILS with --prefix=${X} --with-sysroot=${X}
> > configure/build an initial GCC (all-gcc all-target-libgcc) with
> > --prefix=${X} --with-sysroot=${
Steve Ellcey writes:
> I have a question about building a toolchain that uses (at run time) a
> dynamic linker and system libraries and headers that are in a non-standard
> place.
>
> I just noticed the IBM --with-advance-toolchain option and I would
> like to replicate it for aarch64.
>
> Let me
On Thu, 2019-10-10 at 18:41 +0200, Florian Weimer wrote:
>
> * Steve Ellcey:
>
> > I would like these used by default so I took some ideas from
> > --with-advance-toolchain and used that to automatically add these options
> > to LINK_SPEC (see attached patch). I can compile and link a program wi
* Steve Ellcey:
> I would like these used by default so I took some ideas from
> --with-advance-toolchain and used that to automatically add these options
> to LINK_SPEC (see attached patch). I can compile and link a program with
> this setup, but when I run the program I get:
>
> % ./x
> Inconsi
On Thu, 2019-10-10 at 10:49 +1030, Alan Modra wrote:
> On Wed, Oct 09, 2019 at 10:29:48PM +, Steve Ellcey wrote:
> > I have a question about building a toolchain that uses (at run
> > time) a
> > dynamic linker and system libraries and headers that are in a non-
> > standard
> > place.
>
> I h
On Wed, Oct 09, 2019 at 10:29:48PM +, Steve Ellcey wrote:
> I have a question about building a toolchain that uses (at run time) a
> dynamic linker and system libraries and headers that are in a non-standard
> place.
I had scripts a long time ago to build a complete toolchain including
glibc t
I have a question about building a toolchain that uses (at run time) a
dynamic linker and system libraries and headers that are in a non-standard
place.
I just noticed the IBM --with-advance-toolchain option and I would
like to replicate it for aarch64.
Let me first describe what I do now:
confi
