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=1FZb7R8HCHsVemNnLTMDT9jOQlbZLPOcQ8JMMiJKXpY=; b=P5JxAF3mFVn3mEdvaErT+D8J+HKugWdLfXWK47JQrnULqK+71EBqRPZLhyKWpIXHDp LQ6tl2fyggbLMyXpo5uiGYnzsTE2oUq6jkkgs1DLc1ChZbAX/Wp60pO7jaxRrsmjx8FD H1cixykfPotsvqfE0M/hlPHD3XVOgzLa9o7+9Dczoto6haYonV9fXlvz/GLvmNQSjmkE yR5qWW/TujLW1TZWFAAfM7YXfzKE18qC3sHujHS8VH4A3D2DzC8QXd6nnFczpZ9/0kVs Sc9IQK9r8QqdLK3unpTqjnLkfJeJHvyscJP+6aavDrXvSL0uhmhXfKCzjsUKhzUGfK+Q dq/w== 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=1FZb7R8HCHsVemNnLTMDT9jOQlbZLPOcQ8JMMiJKXpY=; b=bsLwi0V8NZEPpC33XSjeDPKRWUMnWUFNltSMY6thy05oQ0d97mxFA2AF/FoJVtoTXo mLQV1l2bCYt/nJWNsjS0nkhTP/bMacceQyeO0oEQ0aAOw3Ve9491M91jjiRiZ0fqvFbZ 37gq7yefnrrl8f9CPp/jwZFu4vTezcSjM+DNgyAs2I84C64lnaBHOpldOPWxUgeyFpbS rzxcpeZ0FoAWEk2wC9kYgVr9a6QocHOWH4hG3jqQa29HQ4vOYHkIODVsZhkmJAnCns7Y Aw/xbSj894oHBmOxH3oTI9ODl6joOYGPHxgBsI6V36z4fEiCVcWE/4AKmmhLtJ/MuaDM cAxw== X-Gm-Message-State: AFqh2krO3CYBXMVfB1M/QKy/asnu8m/VM8xm3GLNyEBW5Lfbz8ra2SuA kXHJbDNnvv/6NIeQGpEsGnIzzyWVb1LaiRMWjauoIhZE X-Google-Smtp-Source: AMrXdXsaao/KkDI8+SBymWY/SPmuEr9COYADgtRQD2OtNZrj7pYXKGAHbB6mAwDCEB6D+14TWBs1MGBylGAfMjZmceM= X-Received: by 2002:a05:600c:4ca7:b0:3cf:7b68:631 with SMTP id g39-20020a05600c4ca700b003cf7b680631mr2254880wmp.55.1675027023469; Sun, 29 Jan 2023 13:17:03 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <83r0vd78cu DOT fsf AT gnu DOT org> <83o7qh74td DOT fsf AT gnu DOT org> From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" Date: Mon, 30 Jan 2023 00:17:02 +0300 Message-ID: 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 >>> 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. > > It is probably possible to configure different directories for libstdc++ > and libgcc. The native gpp*b.zip packages on ftp seem to do that. I took gcc1030b.zip and its companion gpp1030b.zip as an example: libgcc is under /lib/gcc/djgpp/10, whereas libssp and libstdc++ are under /lib, and my version handles both. > But another benefit of using gcc to invoke the linker, is that additional > default library paths can be added via the specs file. For example, with > my toolchain packages for Debian, linking via gcc will search: > > /usr/i386-pc-msdosdjgpp/local/lib (libraries compiled by user) > /usr/lib/gcc/i386-pc-msdosdjgpp/x.x.x (gcc / libstdc++ libraries) > /usr/i386-pc-msdosdjgpp/lib (libraries installed via package manager) Yes, that's an advantage. > And of course, users will no longer need to set any environment vars to > run dxe3gen. It will just work "out of the box". That wasn't the initial > goal, but I think it's a welcome side-effect. Yes, that's another advantage. The only downside to your patch is that older gcc versions have a problem handling -T on their command line, which is why I had gone back. I don't have a solution for that, buit I honestly haven't tried very much. Eli, DJ: What do you guys think?