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:references:to:from :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=WhhUB7LZWsYXVRde1KhfoSffhq9UhjIJEnA5sKLJLYk=; b=SUOVg15vYCWtLYsbE21LIU8ps7o9ZIdW82ZFp56drS6tTlDbNSglXKJGMKSppVggU9 4lstfHJcZgzkHBSfOBhWvDmF0pOIcF0Gich/BYjFIuczCURNrMlu1mHnHmU5B6Ug62Ay 1gifUFUOhQSaHRIbNu+mFTvPJBm1pM8w7Bvqr/aTuSyXAfSrjcNRv0+O2bbrA0VbKyeT gyzJQI5rcCYOh5CEJojpoEumgSiJzSHTH/3LCzttzn0N3p4sHFNCb8GNJzLhLIcLzDpG ij71PTVdKFnVWWlSGtQGot7wLgecD9pzPHpKbXy5X8eWiMRliLLV6Owdc1nmDSl51She eY+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:references:to:from :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=WhhUB7LZWsYXVRde1KhfoSffhq9UhjIJEnA5sKLJLYk=; b=O/++ezit2se14L7LkaYkm+EnUgYShtX7sLgLeGe6NkQJ4bBoIZyLVaB9Qk2xVJTzfh 7hYERqghykIYmvXVcaKi5P3ZhNj2K3rNJeD4tp2VjfvBG+zp97iPXcjQWNPQb8gvQVip Q7CscPqPP3dxkSZaf0hayDZjWozGhuz5uApwgDIZTyvXdcwE+GBzEyne1uR/nic+3tUG Ie20M5XYg8i7s3CXjF5h7qzbJXHylSOAvFcgXLnzmM/6eN8tzxoYAOaKVlkWpPCSfGXG WjRK34uAL4rofdPNMqshglpt4fu4mTJnmmxF7MnZA5S7q7yX5CnLRgtD91bvHAH3Ur6N CjgA== X-Gm-Message-State: AFqh2kpKDefOQ8JAgw6BBEsvXiUyhCuMQic7WN96kB8cCBWjUp+hYgdl 5izq5X1wMs6bDnrc2dADfhPBk57ZtNu12A== X-Google-Smtp-Source: AMrXdXsd3+ZgYlyCg66n46xwjw8e2ufjb95Md5vuAscZ7MMVSuRdAxJa1n7L1A33g/ug3M75EJBqFA== X-Received: by 2002:a05:6402:528b:b0:49e:28c1:9375 with SMTP id en11-20020a056402528b00b0049e28c19375mr47293757edb.10.1674925304683; Sat, 28 Jan 2023 09:01:44 -0800 (PST) Message-ID: Date: Sat, 28 Jan 2023 18:01:44 +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 From: "J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]" To: djgpp AT delorie DOT com References: <83sffvbux1 DOT fsf AT gnu DOT org> <83mt63azwi DOT fsf AT gnu DOT org> <835ycravjo DOT fsf AT gnu DOT org> <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> In-Reply-To: <673bbaa0-5a0d-25be-1f1b-724856ee4f0b@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com On 2023-01-28 17:46, J.W. Jagersma wrote: > On 2023-01-28 15:12, Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com] wrote: >> OK, patch reverted, >> >>>> As for documentation, is the following good? Better wording? >>> >>> The text is fine, but the markup could be improved: >>> >>>> +@item >>>> +Linking to gcc-provided libraries like libgcc may need special care, >>> >>> libgcc should be in @file >>> >>>> +because the linker may have no idea where libgcc.a is. One solution >>> >>> libgcc.a likewise >>> >>>> +to that when using a makefile is, retrieving the libgcc directory and >>>> +combining it with -L before -lgcc: >>> >>> "-L" and "-lgcc" are command-line options, so the suitable markup for >>> them is @option. >> >> Documentation patch is applied as >> https://www.delorie.com/bin/cvsweb.cgi/djgpp/src/dxe/dxegen.txi.diff?r1=1.9&r2=1.10 >> >> Thanks. > > I don't really like this "solution", it just makes it the user's problem. > > How likely is it that someone uses the latest version of dxe3gen, but is > somehow stuck with such an ancient (nearly 25 years old) version of gcc? At > some point you'll just have to say, for gcc < X, use dxe3gen Y. > > For DXE_LD_LIBRARY_PATH, that can be added easily as -L dir, and won't break > anything. But not having this set should not be an error. > > For DJDIR, there is only one valid place it can point to, and gcc already knows > where to find it. I don't think a native gcc even works without DJDIR set. So > it doesn't make sense to also parse it in dxe3gen. Also, with removing DXE_LD_LIBRARY_PATH, the concern was that it could break existing makefiles. But now the accepted solution is... to break existing makefiles? That logic is hard to follow.