Re: Fine granularity of control over libgcc* search paths

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Nov 8, 2023 at 1:21 AM R jd via Gcc-help <gcc-help@xxxxxxxxxxx> wrote:
>
> Where, [The Evasive Library Paths] = -L/usr/lib/gcc/x86_64-linux-gnu/11
> -L/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu
> -L/usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib -L/lib/x86_64-linux-gnu
> -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib
> -L/usr/lib/gcc/x86_64-linux-gnu/11/../../..
>
> It is [The Evasive Library Paths] that I am trying to get fine control
> over. It seems that these are just automatically inserted because we are
> linking with -lgcc which makes total sense - but I need to have full
> control over it and may want to change it. The rest of the command line for
> *collect2* is understandable and modifiable since I can match it up with
> the relevant SPEC file. Only these evasive library paths are causing me a
> lot of wasted hours.
>
> I was looking at *LINK_COMMAND_SPEC* (
> https://gcc.gnu.org/onlinedocs/gcc-5.2.0/gccint/Driver.html) as a potential
> work around, but I thought that, since it is already late, I would just ask
> on here.

Are you aware of --sysroot? This is probably what you actually want.




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux