X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
	s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
	mime-version; bh=6TLT6Ei6G17dDm94eX3yWJ09s0ADYDjYDrh/BQiGiUc=; b=RC/s3LQfyHHt
	bw0QkDXG9EUlcHEmrhvD4djAekQtqPNH5/FOWHQteztBrD0CX6/BOHnDNxMzbel/RtpHI/1Eq/14d
	9lQMcmOxYsd7zEP470e/ByrDzGf6TLottId0QH0nTuCHo+Jj/ZSTKp2fK+I1TEZEBAdG5UqDwCYte
	lUbpPhOZgS1MLDgo93Hro/gUQnTYFCjV5hR+Knwud1iCBuVXzB603LUgBIQwP1oHTyXxWhFvd1gI7
	JlDk4WxPc8Qq4j4W36XLygQjYlPgz5WH7XwyMYK3JcngWuZ0oMSw3DyP4TK+MKskERWrVVmvFrPf5
	jlzl0ibgDe4hDCwoKK85+Q==;
Date: Sat, 28 Jan 2023 09:36:29 +0200
Message-Id: <83ilgraz5u.fsf@gnu.org>
From: "Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
To: djgpp AT delorie DOT com
In-Reply-To:
	<CAA2C=vA-Va7sac2nZX189eweKVCQ1zGAPnQ6T6Yi-noYX-ioZQ AT mail DOT gmail DOT com>
	(djgpp AT delorie DOT com)
Subject: Re: DXE3 with std::vector
References: <edefcfee-d1ce-415a-8d1d-525a660fb0d5n AT googlegroups DOT com>
 <CACuL_+CZm++qhEr7PedDmQaTxjZu9d-rVSw1bgPeist7XZ+dpQ AT mail DOT gmail DOT com>
 <CAA2C=vDPwv5G9DeFKyKFqt39cDDmO4LmDtbtMyoMdRR2xeEkow AT mail DOT gmail DOT com>
 <3b8f674c-bca3-c679-952e-f8ba5af196e7 AT gmail DOT com> <CAA2C=vBptnTAy2TA-pj5JCbAUJMiXkAAoP_xYFZZJ99iB7v9mQ AT mail DOT gmail DOT com>
 <500850be-fd64-3f82-a1e1-929903084e9b AT gmail DOT com> <CAA2C=vA0zXX3Sb49WBzU5g1-8dmO5G5wrb3uT+tLRq2LB0wu5Q AT mail DOT gmail DOT com>
 <3d9271ae-266d-ee7b-853b-984857ced1c8 AT gmail DOT com> <CAA2C=vD6sZpTicPh0xuJ16r76qBZ5BZro6x=9+=Z+P-0f_eRSA AT mail DOT gmail DOT com>
 <f04cd9db-fe76-219c-bacb-47711df559e2 AT gmail DOT com> <CAA2C=vCv_bpM+iinTcreMJD_gv34Rna3jLspiLFfESFuNxOtoA AT mail DOT gmail DOT com>
 <af7fa08a-b074-0a4c-5e2f-99299940e3cc AT gmail DOT com> <CAA2C=vB22rof4HPV_dVPy4tVmsmeDMy4G4r2Vx-_YLwOW6C9ug AT mail DOT gmail DOT com>
 <bbdf1853-5454-93b2-fcf9-2306c6949c86 AT gmail DOT com> <CAA2C=vBDi8gwhVVacnhnP+eufCkMNK4DancpOjnD7ScOWCEF6g AT mail DOT gmail DOT com>
 <83sffvbux1 DOT fsf AT gnu DOT org> <82cff092-6dfe-1dfc-7946-cdb84c44e11b AT gmail DOT com> <CAA2C=vA-Va7sac2nZX189eweKVCQ1zGAPnQ6T6Yi-noYX-ioZQ AT mail DOT gmail DOT com>
Reply-To: djgpp AT delorie DOT com

> From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
> Date: Sat, 28 Jan 2023 00:03:33 +0300
> 
> >>   . the code will no longer heed DXE_LD_LIBRARY_PATH and DJDIR
> >
> > In the vast majority of cases those would point to the global lib
> > directory.
> > That is no longer necessary, gcc will know where to look.
> >
> > In case someone used DXE_LD_LIBRARY_PATH to point to something
> > else, that seems like a strange configuration, was that ever intended to
> > be supported?
> 
> That one was supposed to let ld know where the library dir is.
> If anyone else actually used it for something else, well, as I said,
> they can always use -L/some/path -lfoo as they always could.

Why cannot we tweak the way we compute the command arguments to still
honor these two variables?  It's a simple matter of reusing code that
was already there, and was used for ages, no?

IOW, is there a real reason for removing the code which used the
values of those two environment variables?