[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0911050057280.1469@artax.karlin.mff.cuni.cz>
Date: Thu, 5 Nov 2009 01:05:23 +0100 (CET)
From: Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
To: Valdis.Kletnieks@...edu
cc: Martin Nybo Andersen <tweek@...ek.dk>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
"Ryan C. Gordon" <icculus@...ulus.org>,
Måns Rullgård <mans@...sr.com>,
linux-kernel@...r.kernel.org
Subject: Re: package managers [was: FatELF patches...]
> Walking $PATH is even worse - if it finds a /usr/local/bin/ld, it's a pretty
> damned good guess that it's there *because* it's not the /bin/ld that the
> system shipped with. So why should it use it?
If it finds /usr/local/bin/ld it's because the admin installed it there
--- and he installed it there because he wants it to be used. So it's OK
to use it.
Anyway, if you have both /usr/bin/ld and /usr/local/bin/ld, you are in a
pretty unpleasant situation because different programs search for them in
a different order and you never know which one will be used. (i.e. what if
./configure scripts prepends /usr/local/bin to $PATH ... or if it prepends
/usr/bin? who knows - no one can check all ./configure scripts. These
scripts do crazy things just because it worked around some flaw on some
ancient Unix system).
Mikulas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists