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=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=TBSSdIwu4kGnfwJzT6vHPgdAqk/l+5nWzA1ISPepGaI=; b=jwlLnCTCkca+PcES0BxPiwm5uB9k4PNl5Hc5YwUJrJWwOL2WPOsdv2MtvX23r9O8Xf kumS18L9YHez1jPC43UvkBvhDunalQaxllcFzBX8TTlVMLKbuFTc4EdwN/IfCQ1irL08 +UP1dZQH7mPBMoh3mpIHn9UYONFb/KcNrPmoKK4IAv+3LAX8T3z5DvXnaz1VraCA9vHx xDDbdUCIrWds+PYDk9gW0xDRbGHhooowJZIIqiiFKiWA1KBRbFbFDU0LLPhXj4nsXe/N uRYPcf++n80ubvdEEKZS0M0uCM1nNeyAtFmamWuTi2p4cVsnL/y5FN23uVvifo5irfRs YcBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=TBSSdIwu4kGnfwJzT6vHPgdAqk/l+5nWzA1ISPepGaI=; b=H/qWkk+XwnVJjDc9NPlK3kT0QuC+dtfVO0Go48a7Ch701lDxaTw/G5X1QkVbiD/Y1o l9bmW9ieIZqke1Libyt1GNwgQDHf3CeVUi6XOHkwJL2YeSM7pcX912VE+/jilMCKxs32 D4PAggMdJZdywnZWtONAgc2pQ5tzl7EmypNNW9+rqZKpuFTFL+thMDTsI/7s3LOr6OIl c+LTfJ/Ri8CeWIFLJM+8nRye6hlnTPlDjpylHpWmaYQGilKhkbuB2Cm6700FwXRgw8mx l2kuKrIuSqNCYC4m9QHiKzbe54qH3juX02ZuzT5XQ74aJxmvvezD3qc/Daawki69fRTj IJoA== X-Gm-Message-State: AFqh2kpMJa22yikKR6trHUquL/6YacZ6UxekMVVaSpts1UPDbFcPlyc8 DUtuT67TuYJSH6WHXY5Ul7m6WpnJCwdf4A== X-Google-Smtp-Source: AMrXdXv3kDjFwS/Uyi2HGvdmzYHhl/KE9DOJ08/+5ePHbRt0UNLEPh51C3iCL1WXTxuYrV5wrw2Y2A== X-Received: by 2002:aa7:cc81:0:b0:47e:eaae:9a5b with SMTP id p1-20020aa7cc81000000b0047eeaae9a5bmr45414174edt.42.1674939086389; Sat, 28 Jan 2023 12:51:26 -0800 (PST) Message-ID: <5720fbf2-e95d-4e76-9806-5381df0883e2@gmail.com> Date: Sat, 28 Jan 2023 21:51:25 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: DXE3 with std::vector Content-Language: en-US To: djgpp AT delorie DOT com References: <83zga39fil DOT fsf AT gnu DOT org> <83v8kr9bye DOT fsf AT gnu DOT org> <83lelmakwk DOT fsf AT gnu DOT org> <83h6waaium DOT fsf AT gnu DOT org> <83fsbuahj9 DOT fsf AT gnu DOT org> <673bbaa0-5a0d-25be-1f1b-724856ee4f0b AT gmail DOT com> <15bba6fc-1b9a-f709-7c7b-2fa3f133d5bb AT gmail DOT com> <834jsaa77b DOT fsf AT gnu DOT org> <8257bbce-b49a-f36c-1fc8-17cf6b5aa83f AT gmail DOT com> <83wn568lyh DOT fsf AT gnu DOT org> From: "J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]" In-Reply-To: <83wn568lyh.fsf@gnu.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 On 2023-01-28 21:04, Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com] wrote: >> Date: Sat, 28 Jan 2023 19:12:06 +0100 >> From: "J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]" >> >>> No, in a native installation libgcc and libstdc++ are in a directory >>> different from libc. We just didn't support linking against those two >>> libraries because AFAIU it was never needed by anyone, definitely in >>> the case of libstdc++. >> >> On my end, libc and libstdc++ are in %DJDIR%\lib\. But I see libgcc is in >> %DJDIR%\lib\gcc\djgpp\12\. > > libgcc should be in a version-specific directory under either lib/gcc > or lib/gcc-lib. libstdc++ is normally also in that subdirectory, I > don't know why you have it in lib. It is version-specific, so cannot > be in the general lib directory. That would indicate a problem (?) with the recent gpp*b.zip packages then. From 4.7.4 on, they all come with libstdcxx.a in lib/. >> It is probably possible to configure gcc/libstdc++ to place these in any >> arbitrary location. I think it's best if dxe3gen and makefile writers have no >> knowledge of a user's particular configuration, and simply leave it to gcc to >> figure it out. > > Yes, that's true. No argument there. I'm just saying that if someone > has some unusual (read: crazy) non-standard configuration, where > libraries can be found via these two environment variables, we > shouldn't break those unusual configurations. If you think it should be kept, then I won't object too much. A duplicate -L entry indeed does no harm. I'm just saying it's completely redundant - native gcc will not work with an invalid DJDIR, and it will always put %DJDIR%/lib in the default library path.