GDC with D frontend 2.081.2

Johannes Pfau nospam at example.com
Wed Aug 29 06:31:51 UTC 2018


Am Tue, 28 Aug 2018 10:19:46 +0200 schrieb Daniel Kozak:

> On Tue, Aug 28, 2018 at 8:40 AM Eugene Wissner via
> Digitalmars-d-announce <
> digitalmars-d-announce at puremagic.com> wrote:
> 
>> On Tuesday, 28 August 2018 at 06:18:28 UTC, Daniel Kozak wrote:
>> > On Mon, Aug 27, 2018 at 7:55 PM Eugene Wissner via
>> > Digitalmars-d-announce < digitalmars-d-announce at puremagic.com>
>> > wrote:
>> >
>> >> On Monday, 27 August 2018 at 17:23:04 UTC, Arun Chandrasekaran
>> >> wrote:
>> >> > 1. It would be good to print the DMD frontend version with `gdc
>> >> > --version`. It is helpful in reporting bugs. LDC does this.
>> >> >
>> >> Unfortunately it doesn't seem to be possible. GCC doesn't allow to
>> >> change --version output:
>> >> https://bugzilla.gdcproject.org/show_bug.cgi?id=89
>> >>
>> >>
>> > This is not true, right now on archlinux if you type gdc --version it
>> > will display d frontend version
>> > https://bugzilla.gdcproject.org/show_bug.cgi?id=89#c1
>>
>> Is it set with --with-pkgversion? The same information will be
>> displayed for gcc and g++ then. It is not always desirable if you ship
>> the compiler as a whole (with libtool etc).
>>
>>
> Yes and no. It is set with  --with-pkgversion but it is only for gdc.

But this only works as you build gdc and gcc separately. I.e. for gdc, 
you build gcc+gdc, then throw away everything but gdc related 
executables. Then you compile gcc with different --with-pkgversion for 
the gcc package.

However, this has the problem that your gcc executable now does not 
properly forward .d files to gdc as that build did not have --enable-
languages=d. The supported way to do this is build all gcc based 
compilers at once. But then you can't use --with-pkgversion as it will 
apply to all compilers.

-- 
Johannes


More information about the Digitalmars-d-announce mailing list