Re: LDSCRIPTS

[John Pierce <john dot w dot pierce at gmail dot com>]

> Linker scripts are not meant to be modified by end users.  They should
> only be modified by toolchain developers.

I guess you could say that I am a toolchain developer (for my own
system), as I build gnu/linux from sources.
 
> This is in contrast to /etc/ld.so.conf which may need to be modified by
> end users when configuring a system.

If my understanding is correct /etc/ld.so.conf is for already
compilied programs looking for their shared libs.

So (btw, thanks for the url to doc) the linker is for linking libs to
objects. I addressed the modification issue below, however if I were
to put libs in nonstandard locations could I again modify the scripts
to reflect?

> Having said that, deleting non-existent directories from a linker script
> should be safe, but it probably won't do anything, because the linker
> won't use that script unless you specify special linker commands, which
> you shouldn't be doing either.  

If I did do this will the linker know it was modified? Are you saying
that if I did the linker will not use the script?

>If you really don't want those
> directories in there, you should be modifying the binutils sources to
> support an x86_64 single-lib system, so that the linker will have the
> desired search dirs built in from the start.

I have built my system to be single lib (64bit modified to be put in
/lib /usr/lib).

Is there a way to modify the configure to be only single lib? 
I only found one occurance in the source for lib64 dealing with
x86-64. And that was in (binutils source)/ld/configure.host.

>  But then you probably
> shouldn't be doing that either, as that may cause other problems later
> on, unless you are willing to deal with those other problems.

The problems I did experience were easily fixed.

I also un