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=pMW65pAd67opqAjI13blATFV5FsFeZCMmMZShn3+pE8=; b=ioVR6UsA1ow8Sd/V+CymH1O2yKhrJbMLaKu0oPK7A+EnmrwPVojWV1hnx9ws30OIxo wwHdlx9XDH9/ghF0Vr4eoSL0S2PyNV3rstkT0i51DZBR3jckl5Y4ammOaITJJC38H1aZ gW9YNHSgCjVPSIp1F+ZAehSrLxzgh8AZkka5/M/hvW6BeAumlyPmIthENZP4b+JbTaJE peiMJCMeESgOMQpj8rlsHO7ipBYdoweCj1ZqgBXEaJBZa6oqKlCLps2uPrr+wolC0fuo PwIaHgIiJ69moi7fX3QNwVWYGLPCfALyNk2eosppJU894lFL+uQglFADidZK9sg2ZgZo 9SxQ== 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=pMW65pAd67opqAjI13blATFV5FsFeZCMmMZShn3+pE8=; b=tmIhuHi9YMhEo3Cjj7RjI7gEg9Sqynej1gv2KRx8pnrsMmXGOngE0R7KzArBYkkxkO DtsdnhVGrj7TYatOM5qKJNluzUcTKQBaYRLDnMgExEYaXnessZEnBxdFpPEO/+o4BAiM yTScfTXFe4qUzui0sTFfW1vg3CTSEBDoOnw4sotcoRQoutwm7e3Me5hwBPC7BZrDM3+t AKwnFLJlQDxVetXQYkKBbR2FTSsj4lNaODfVwP0S0Gr0AEEkcaxMTJPLdM2Vjb2g3f6I O66n3cCa3LVjCJGYUBLchp9iPbQ60P9lHsHUrwu9+4wJpUZ4OkRSXTzFjvrGMAOBRwMk r9Mw== X-Gm-Message-State: AFqh2kphy1RVQ9WNDtRvgiZEmEDuxWCZbfAPYdW6ttxLrxTEsHkyxeNp AjVz9CaqMD7sND1u1HNt+YdL8IhsywgGcHzY7OAoVzPD X-Google-Smtp-Source: AMrXdXtk6wflKtvBLyofVr1xGf7WxMmlTxNC0ALrAN06PdV3K2LTgQjF7OrrPM03RgmNiHsA0Tdjy8CvMs1uh6gxbUc= X-Received: by 2002:a05:600c:1d25:b0:3da:fa8a:8511 with SMTP id l37-20020a05600c1d2500b003dafa8a8511mr1399751wms.185.1674446449664; Sun, 22 Jan 2023 20:00:49 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <3b8f674c-bca3-c679-952e-f8ba5af196e7@gmail.com> References: <63a56722-21d6-a368-6400-907f0cf9d01c AT gmail DOT com> <3b8f674c-bca3-c679-952e-f8ba5af196e7 AT gmail DOT com> From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" Date: Mon, 23 Jan 2023 07:00:48 +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 >>> Maybe. I'll give that a try tonight. The only difference from what >>> I'm doing now is I'm doing DXE_LIBS /before/ the OBJECTS. >> I'd like to hear the result. Remember that >> dxe3gen --show-unres xxx.dxe >> will output the missing symbols in the dxe. > > Yes, this is exactly the problem. So, apparently, you must do > -l AFTER $(OBJECTS) otherwise it does not > work. Good to see that it now works. Just looked at dxe3gen documentation, and it says: Usage: dxe3gen [-o output.dxe] [options] [object-files] [ld-options] or: dxe3gen -1 output.dxe symbol input.o [input2.o ... -lgcc -lc] that 'ld-options' is always at the end which includes any link libs. So, the order of arguments _is_ important. >>> 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.