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

Re: [MiNT] broken LD



On Thu, Apr 06, 2000 at 03:08:55PM +0300, Martin-Éric Racine wrote:
> On 2000-4-6, Frank Naumann <fnaumann@freemint.de> wrote:
> 
> > As the search of crt0.o has nothing todo with the linker it's
> > useless to try to replace the linker.
> 
> Incorrect.  When a tool reports an error, replacing this tool is 
> the first and most obvious course of action.

I hate to say that but you are right here. ;-)

The compiler driver gcc always passes an absolute file name for crt0.o to
the linker.  It should check itself if that file really exists.

> > Right, my egcs and 2.8.1 are relocated to /usr/local as /usr
> > is reserved for rpm maintained packages.
> 
> Please do not impose your personal choices on others. 
> 
> /lib:/usr/lib:/usr/local/lib
> 
> and
> 
> /usr/m68k-atari-mint/lib:/usr/local/m68k-atari-mint/lib 
> 
> are all valid path choices and should all be supported always.

Tell that the gcc developers and they will contradict you.  If you
configure gcc to install in /usr/local then /usr/local will be the general
prefix used.  If you install in /usr, then /usr will be the general
prefix.

If you don't build gcc yourself but install a precompiled binary you are
stuck with the personal decision of the person who built gcc for you.  If
you don't like that decision you can either make arrangements in your
environment (read the gcc docs for more information) or you have to get
along with soft links (nobody hinders you to make /usr/local/lib a soft
link to /usr/lib).

> > Do you checked your environment?
> 
> There is nothing wrong with my environment.  Undocumented,
> inconsistant, hard-coded paths in GCC ports were the problem.

They are all documented in the gcc info files.

The info files also document how to override the hard-coded paths.  And
common sense and the manpage of any standard cc will also show you why
hard-coded paths for a compiler system are a must.

Former gcc ports were worse here, that's right.  They used undocumented,
and Atari specific environment variables to modify the compiler search
paths.  Frank's port is far better because it only uses the documented
features.

Ciao

Guido
-- 
http://stud.uni-sb.de/~gufl0000/
Send your spam to president@whitehouse.gov and your replies to
mailto:guido at freemint dot de