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:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=8iOAutSsoOmGkRMG30RxA+hKZ8vpm/tszYKPrU+bLxg=; b=QXZp4D8bp2H/IpqOfKPiXQGgmIqIR13iRqYr+N91SLhSyIM8MkSXriK9DwNI4sL7gH HkWVoSbiULkQxJOstvbd87kQCRwkXfVcslm1GP2PCVxjSvQpfqpZtFq9We7EIj4pihb7 YBrkh0NUWre7h47CiwqdlxlNsDurTaQVkdaPAQWbKf/nAhdMLjWZRhkDNeJPS9CJDwXc ynbfcCA5OA8dxcE4OBNgMk9RrWgmgFGRfBR2lrwGlJ1gFDqAdv/F0KuUwg2tXOp9cfAY dPf0oxFiR+esACskxGdK+eOW8w7Mi3IxVWm+1zha+okI2KW1L2BFNpAaa8ZkT5hOW1Rf EbzA== 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:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=8iOAutSsoOmGkRMG30RxA+hKZ8vpm/tszYKPrU+bLxg=; b=nKk0q7/hIJQDbgbMaFSi7R9F1BBJdxydq/cFzl5NcXT/toridfx+M2cRzxstOmvso7 zz3XJPjd0PtPlSNRDgvrPlVVBwxMz3SL9ulpTRz6OwjQbWJg+ksCoQ3a7BNPUMonOhd/ JswtMiBcayAlR1kZIwUNuZfssns5Hu51WA+cXlxKJtCEDL2XQYnSZOL90vBDho649w3X 6aSXRZ5Fg6MvEhWibHXhiiYYbCxUjuz8w9eOgQxn6+Y4ABLk4UWMfwwH4xCJSe5fq1M3 fHx0ynL74w8Les1TvSMsWWmUNIXNf6xZ7FwMb4qh7qgmmRnwnHUNNfxfEzwV1X1Y6+6y z1RQ== X-Gm-Message-State: AO0yUKUzEQZGI9nauoU+fI+Yrf1qvrQ8GRTaB5fnIUYfvAkc5t9QxPww f6yWXTATYab6eiEnYcBJfL0J6Y7XdIGAHQ== X-Google-Smtp-Source: AK7set/Xs89mPgyLtw0UCDMmeawIDPn6Te9zfWx0NHCndrTtADzg0vGAzyujPEhJV6V6FUfNb0FKQA== X-Received: by 2002:aa7:cd65:0:b0:4a0:e415:d39f with SMTP id ca5-20020aa7cd65000000b004a0e415d39fmr10136767edb.41.1674924378135; Sat, 28 Jan 2023 08:46:18 -0800 (PST) Message-ID: <673bbaa0-5a0d-25be-1f1b-724856ee4f0b@gmail.com> Date: Sat, 28 Jan 2023 17:46:17 +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 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> Content-Language: en-US From: "J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]" In-Reply-To: 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 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.