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=fdm6bk9ArgOQInkXnSOWrJjVcfol6zWZojwDqLbYwRc=; b=FsV4iypAK2zY
	h7zdsVbh6v9BJW4KGJiIEtodG8ZvyPsu//yB5Ah6LdwjrmMulLQf04FpkNDaE7YUbHI6BpmNEToA4
	5T+TJ6Zx8MA7TeVwt+WAbfTPjjrtL1xQemuUXdrfUfeiolXQr1uJcBZ/CVRVGaF9znLaI3zM+EDAr
	dK2Bu3xeEK2wTp1yPHPjp9joKH4Skxg+qID+Q1W8Txf4BEfNWb3OJkDygOJn+ThrNLFJ9n4waDKqp
	ojflMnXJhC4SkmmI6JFccStCaUnZhT0FdbX+CJYbC8oUf81RoBmVYsnFcDrBKMez723qJxoQNoxqM
	fnkfg3a/5yD0v6tjZOLcyw==;
Date: Sat, 28 Jan 2023 21:57:30 +0200
Message-Id: <83y1pm8mad.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: <ff678ac2-ffd0-4f06-07eb-f5ad50dab84b@gmail.com>
	(djgpp AT delorie DOT com)
Subject: Re: DXE3 with std::vector
References: <edefcfee-d1ce-415a-8d1d-525a660fb0d5n AT googlegroups DOT com>
 <CAA2C=vAuq+O2gRRM--E0YAPy6D1pLgcP2r0-4+sCLis=kwGYzA AT mail DOT gmail DOT com>
 <83mt63azwi DOT fsf AT gnu DOT org>
 <CAA2C=vByQZVnfkF_0UX+4p+rcm8uTehwSnM9hSHW-m=Dc4HBtw AT mail DOT gmail DOT com>
 <835ycravjo DOT fsf AT gnu DOT org>
 <CAA2C=vCauV7VviJ2L+us_4KOgH8TYgEkVtn17hyBxDH5YuddRA AT mail DOT gmail DOT com>
 <83zga39fil DOT fsf AT gnu DOT org>
 <CAA2C=vCPF_OJkxGxqhQNue0K4j0WQ302GdYSncQydM_EN2kjuA AT mail DOT gmail DOT com>
 <83v8kr9bye DOT fsf AT gnu DOT org>
 <CAA2C=vCWL4XJaXstSouW5uUdQt2nyX6jTGxBH+Z6cX+=Te4F5Q AT mail DOT gmail DOT com>
 <83lelmakwk DOT fsf AT gnu DOT org>
 <CAA2C=vBGAd9mET8PH8wSL1dgoARKSEKMyYa7Whc0iWky2BaZ3A AT mail DOT gmail DOT com>
 <CAA2C=vDFaieGgM=PicuE1yTA1WLH6iQF1e2m4d0NCmQ-syUSbg AT mail DOT gmail DOT com>
 <83h6waaium DOT fsf AT gnu DOT org>
 <CAA2C=vA9oS-V1r2D1J=0thzeebzusLTs10HsVdt7jxu0=BAw=w AT mail DOT gmail DOT com>
 <83fsbuahj9 DOT fsf AT gnu DOT org>
 <CAA2C=vAY_VaS4c43pTXz1aAh4sFpHf=_hEiJPmtuZijL4UM2Cg AT mail DOT gmail DOT com>
 <673bbaa0-5a0d-25be-1f1b-724856ee4f0b AT gmail DOT com>
 <f790820b-f07f-8b09-fa18-fa3c57d0824f AT gmail DOT com> <835ycqa809 DOT fsf AT gnu DOT org> <ff678ac2-ffd0-4f06-07eb-f5ad50dab84b AT gmail DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Date: Sat, 28 Jan 2023 19:09:56 +0100
> From: "J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
> 
> > Are there any fundamental problems that would preclude invoking GCC
> > instead of ld (so that your case is supported), but still have the -L
> > switch added to the GCC command line, whose argument is derived from
> > DXE_LD_LIBRARY_PATH or from DJDIR if those are set?  IOW, can we have
> > the code work as you wanted when these two variables aren't set, but
> > add the additional -L switch when they are?
> 
> Sure, that should be possible.  Starting from the patch I submitted earlier,
> simply adding DXE_LD_LIBRARY_PATH via -L will achieve that.

Good.

> For DJDIR, again, having it set to anything other than the djgpp install
> location is *always* user error.  Many things rely on this, and to me it
> doesn't seem very useful to support invalid configurations in dxe3gen.

Once again: adding one more -L switch to a compiler command line
cannot possibly do any harm.