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=gyROLD1auGxum4LM+ZtUapg6vbYfdU2C6csogCUiAT0=; b=RLKO4RusBf7XCqNz6OP8vk7O5P28p0yoz4OFpgBLSOn4svcz7c7noL75lQLYRlhknP r76zpmUjpaU+/Nd2Oe+faVp57cmLUzITCVkZ/Gv7LPbx3rJo3F/R39eJAl/w6Lnh6GY3 1CddxEYZZK6p9rXImn1iOq5Robq+1IVY7NElLM70KyErwpNHuFaJhZHq9lALUQLLj4IL 9XzaTCjM5Xgby894RAdcL5Dcy1JaV9WxF2Y4O4sT+X6q5iy5/myajMVIYzSy7Z12GCZg 7v0LNg6Tl0N4zZ4GlfPYORvdKiEohVugsPzPzO64SQUI13PiD7cBAZO1qHWwlnFI1cUl IjyQ== 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=gyROLD1auGxum4LM+ZtUapg6vbYfdU2C6csogCUiAT0=; b=MgKB/qRCrBlNZz7ch1IjhIlaaSObx+R3/GmcNol2+S2ZH9vlWra5AB1ez/ys/tXp1+ D6nzLOxNGZkn4BlLx1a0nOFAUgF6Vb97TuzkS36CQaEulqNMAi1SFchib6Olg90NuJBT OGYkoxpLFQ2jBKZMtER91ULvpIX0hEGLSjqqpUEzhSRGEHtoRJa3L0az4J1YuSWBQrbo M3z7SA8j1o/lQqNJEZJJwUYkZmQgrZkVyEylBMUctkbCuQdPi9AeEtjvQDXXw8GFOPnN 7WG1NZZJdH9IOB4Z2glK3qnqqkE2bm64bY4wXE4m39b8Nu+8j1OZTQVpjnc7VzxAg7Xr XGAQ== X-Gm-Message-State: AFqh2krbOPSuZ+Unz6JK+rGNOPhStZIQxQY86SpTf5KwuFElRS5pVDPn GF8UyOqZL9d0sPAi+iY2Vmx03Ywm1UlPBUM2WHDmvL/H X-Google-Smtp-Source: AMrXdXvBibUgArs+IlsL8bFOsB/lMd+EM1yJshZVGTzvGMNhyYRzjKQSJ9bN76UoSH/7lKMuKvK4Nxmzps9RfOyvsUY= X-Received: by 2002:a1c:e915:0:b0:3d9:722c:b60c with SMTP id q21-20020a1ce915000000b003d9722cb60cmr2208077wmc.181.1674772922664; Thu, 26 Jan 2023 14:42:02 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <500850be-fd64-3f82-a1e1-929903084e9b@gmail.com> References: <63a56722-21d6-a368-6400-907f0cf9d01c AT gmail DOT com> <3b8f674c-bca3-c679-952e-f8ba5af196e7 AT gmail DOT com> <500850be-fd64-3f82-a1e1-929903084e9b AT gmail DOT com> From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" Date: Fri, 27 Jan 2023 01:42:01 +0300 Message-ID: Subject: Re: DXE3 with std::vector 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 On 1/26/23, J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com] wrote: > On 2023-01-23 05:00, Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com] > wrote: >>>>> Just seems wrong to have to copy >>>>> important libs like that? >>>> That's a shortcoming of dxe3gen with gcc-provided libraries, >>>> needs to be addressed but no one cared (or no one reported >>>> the issue probably.) >>> >>> Any possibility of you being able to generate a patch or can we get >>> it into documentation? >> >> The thing is, dxe3gen invokes ld, not gcc. gcc is a front-end to ld >> and handles any such ugliness behind the scene and doing the same for >> dxe3gen might be a real pain. >> >> If someone other than me can generate solution for this, or at least >> some documentation, it'd be nice. > > Seems stubify does not delete/overwrite the input file if the file > extension > is something other than .exe, so calling stubify isn't so disastrous. > > I have a preliminary patch, attached, untested. > So, you invoke gcc instead of ld, - removal of -X: O-OK, default anyway. - removal of -S: Are you really sure? - removal of -r: Don't think that it'd work. - removal of assembler for import lib generation: Don't think that it'd work. Just tried the patched binary with a dxe build project, it fails as expected: ./dxe3gen -o sndpci.dxe -E _AU_ -U au.o ac97_def.o dpmi_c.o mdma.o pcibios.o sc_cmi.o sc_e1371.o sc_ich.o sc_inthd.o sc_sbl24.o sc_sbliv.o sc_sbxfi.o sc_via82.o tim.o udivdi3.o dxe_tmp.o: linker output file has more than one section