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; c=relaxed/relaxed;
        d=gmail.com; s=20210112;
        h=to:subject:message-id:date:from:references:in-reply-to:mime-version
         :from:to:cc:subject:date:message-id:reply-to;
        bh=ZyZ+0Ixc1QNl71B00lITXLWiO+yz/9EolSOBIGjbGqs=;
        b=WG07cv1oYunhyqhBwcKEzH/V0tlQaqpGB8bD52ejpL8TrsaaFox8Wg1eaPrsu+3FBg
         TVhS+UcRi9CUZXzM67JAh/tFCy6KPRSHWSa+vjZp2aO+3BzZL0bbrSXnmPUctXHbJWit
         wgTSqEp5hEtkVXg27R9i3wQ+Za3+p2AbrzrS/3BfQ5Pdff0Vz4XOROderV6P7wQ5KjqF
         V8myW82uAkMu5kTGEl9pLZwjy7tkx7+HvnSCrBHQB1j3+QrTt9lDxXhYlnsXz5+94eph
         IFrlZBKBlpA4/mw8z8Kq9FSNV1vGNmv99E0VP3icr2xKvg9edIkQSRnG5socfZ2wL1bc
         6/gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=to:subject:message-id:date:from:references:in-reply-to:mime-version
         :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
        bh=ZyZ+0Ixc1QNl71B00lITXLWiO+yz/9EolSOBIGjbGqs=;
        b=AlPHFWlQ/vdbH7FUd5vjwWNE5gylRKzz99CjcQrmVLGdykzSgW8soUctjahiBnHIyZ
         Adx8IhoYnZjalOFGt6YR2Hpii3fPca2BWjtKmIp3s6XvA2bjslIf4f6DfMDVWk3mv5mx
         1Io8ZjPX+4w7oVfHWQ5ooR0hk/+FEKXYj2pWivcWgPvB23dvfZ2Z+Sfq2FTejLOoySCY
         HI4Cb5NtWxE+hwndgnmTrw+yQXgzDLkuPN+e++2poFOkecvRSQRNLl3JvwAeUkyCWzFO
         AJPmMwB+WxyAMDhC/ndBbR/Pm72CDnXzfjIU95qruKZWmUppA/G+B5Jy1/5H0KCF2DEx
         SDNg==
X-Gm-Message-State: AFqh2kqLEYNYIMMMbDfrwfFUTsFEgPkUnv4EVg+M24hTJ+agP0wOXXzx
	U7HLW8vWb7N0FJfRtcha6RtV+eEHNvwldYboiT83Hd3K
X-Google-Smtp-Source: AMrXdXvht9ZFZPO248yCUl6ZBdXKqSPMJiT7nHebJIAywnXDQAgztWp7VUJwUZtFUfw2jVQM/GbdFW565V0/9HJMLS4=
X-Received: by 2002:a05:600c:5403:b0:3db:2fd:46b with SMTP id
 he3-20020a05600c540300b003db02fd046bmr2137298wmb.180.1675005616892; Sun, 29
 Jan 2023 07:20:16 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <83o7qh74td.fsf@gnu.org>
References: <d67303fd-c302-82cc-bb0d-d1a21640d66f AT gmail DOT com>
 <CAA2C=vDYkF13NYPP_EXGMwzrjhLj2vEq68+-uYPfZOXpqWVRfQ AT mail DOT gmail DOT com>
 <83r0vd78cu DOT fsf AT gnu DOT org> <CAA2C=vCCYsgtbQ5wsgbS3S4G7N+H5zi5DxCyVZLSkEKrSpifMw AT mail DOT gmail DOT com>
 <83o7qh74td DOT fsf AT gnu DOT org>
From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Date: Sun, 29 Jan 2023 18:20:15 +0300
Message-ID: <CAA2C=vDT10ZGfa3Mi2x0syvoT44Q3nfgcMfOwMZF=dM+ruL5OA@mail.gmail.com>
Subject: Re: [PATCH v3] dxe3gen: invoke ld/as via gcc
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset="UTF-8"
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

>> >> How about the following suggestion?
>> >
>> > Is this really needed?  IOW, can it really happen that the compiler
>> > fails to find libgcc unless explicitly told to look in the right
>> > directory?
>>
>> gcc can, but ld can not: my suggested patch is not on top of JW's patch
>> it is against cvs where we invoke ld, not gcc. (Remember that the whole
>> purpose of JW's patch is that dxe3gen can find libgcc automatically w/o
>> any user effort..)
>
> So it's an alternative patch?

Yes

>  If so, what do you suggest to do with
> libstdc++, which AFAIU was the original motivation for the change?

Aren't all gcc-provided versioned libraries residing in the same dir?
My patch just relies on that.