This is the mail archive of the binutils@sourceware.cygnus.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Change default location of DJGPP's ld scripts


   From: "Mark E." <snowball3@bigfoot.com>
   Date: Thu, 9 Sep 1999 20:29:23 -0400

   i386-pc-msdosdjgpp would turn into something like i386-pc-~.1 in plain DOS. This 
   will force ld to fall back to its internal linker script.

I don't understand just what you are saying here.  If the linker can
use its internal linker script, it does so.  It only uses the external
linker script if there is no appropriate internal script.  That is,
the linker never falls back to the internal linker script.  The fall
back is the other way around.

   Also, the path assumes that everyone builds their own binutils. But DJGPP users 
   typically use the official port rather than rolling their own. So including the 
   target alias in the path is somewhat redundant. Please consider this patch which 
   deletes the target alias from the default linker script  path for DJGPP only.

We don't put target_alias in the tooldir path because we expect
everybody to build their own binutils.  I'm not sure what you mean by
that.  We put target_alias there so that you can build several linkers
with different targets but the same prefix and exec_prefix.

I don't see why removing target_alias is the answer.  The answer would
seem to be using something which DOS can cope with.  Perhaps on DOS we
should simply truncate the name.

gcc uses target_alias when it finds programs like the assembler and
linker.  gcc and the binutils cooperate in that regard.  Does this
work on DOS?  Perhaps people are simply required to put those programs
on their PATH.

Ian

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]