Skip to content

Conversation

@Bobo1239
Copy link

@Bobo1239 Bobo1239 commented Sep 4, 2017

@dlang-bot
Copy link
Contributor

Thanks for your pull request, @Bobo1239! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.

Some tips to help speed things up:

  • smaller, focused PRs are easier to review than big ones

  • try not to mix up refactoring or style changes with bug fixes or feature enhancements

  • provide helpful commit messages explaining the rationale behind each change

Bear in mind that large or tricky changes may require multiple rounds of review and revision.

Please see CONTRIBUTING.md for more information.

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

@Bobo1239
Copy link
Author

Bobo1239 commented Sep 4, 2017

Not really sure how we want to handle this. Versions higher than 5.2.0 (currently 5.4.0 and 6.3.0) are only available with the new url format but the new format additionally requires specifying the D language version (e.g. 4.8.2 -> 4.8.2+2.064.2) which would break current users of the script. I don't know if there's some place where we could query the corresponding D version.
btw: ftp://ftp.gdcproject.org/LATEST is for some reason 4.8.5 instead of 6.3.0.

@MartinNowak
Copy link
Member

So far @ibuclaw has taken care of releasing stable gdc versions for those installers, so there is no new version/url format, just some releases were provided especially for the installer.
Last time I asked him he didn't intend to update that to the version on the website.
Also the gcc version didn't always increase in the past, last step was from 4.9.3+2.066.1 to 4.8.5+2.068.2.
Let's see whether 6.3.0 is something for broader adoption.

@MartinNowak
Copy link
Member

Will work on this with Iain soon on the GDC side.

@lindt
Copy link

lindt commented Apr 16, 2018

6.3.0 is released, but gdc still cannot be installed via install.sh

@CyberShadow
Copy link
Member

@ibuclaw Any news?

@Bobo1239
Copy link
Author

@CyberShadow I'm currently unsure what the future of GDC looks like as it was upstreamed to GCC. According to the article it should become available in GCC 9.1 (end of Q1'2019).

@CyberShadow
Copy link
Member

OK, so distros will presumably package it then as part of the family of gcc packages.

What about Windows? Is the expectation on the Win32/POSIX toolkits (Cygwin/MSys2 etc.) to do the same?

@PetarKirov
Copy link
Member

Also, AFAIK, for the next 1-2 years the GDC in GCC svn will be based a dmd-cxx (~2.076 - static foreach) , while GDC master is based on a weekly dmd port, though @ibuclaw should correct me if I am wrong.

@PetarKirov
Copy link
Member

PetarKirov commented Nov 25, 2018

Actually, GDC's inclusion in GCC has no effect on the matter at hand, as the whole point of the script is to allow you to install any compiler version, on any OS, which is especially useful in a CI setting.

@ibuclaw
Copy link
Member

ibuclaw commented Nov 26, 2018

Strictly speaking, official releases are the only ones that matter. Anything that is earlier than gcc-9 should be ignored.

@PetarKirov
Copy link
Member

PetarKirov commented Nov 26, 2018

Official or not, the question is how someone can test a project against GDC based on e.g. DMD 2.083, 2.082 and 2.080? For LDC this would be simply install.sh ldc-1.13, install.sh ldc-1.12 and install.sh ldc-1.10.

@ibuclaw
Copy link
Member

ibuclaw commented Nov 26, 2018

There won't be a gdc release based on any of those versions. Will likely be 2.089 or 2.090 the next if dmd continues its rough time based release cycle.

I'll leave binaries up to distributions to make, as how gcc integrates varies per OS due to local patches, configure options, etc.

@AndrewEdwards
Copy link
Contributor

@ibuclaw where do we sit with this? GDC is has officially been in GCC for a while now. Can we move forward with this or can it completely abandoned? Not sure @Bobo1239 is even interested in what happens here anymore since. Hoping that he's still lurking around the community though.

What I would like to know is if there is any plan, now or ever, to see this to completion? If there isn't, there's no pint in keeping this request open. If there is, please state your timeline so that I can know when to reach out.

@ibuclaw
Copy link
Member

ibuclaw commented Sep 8, 2020

@ibuclaw where do we sit with this? GDC is has officially been in GCC for a while now. Can we move forward with this or can it completely abandoned?

Old binaries have been archived off, though old links still work.

Personally, I prefer to leave binary releases to the package maintainers of various distributions. If someone wants to take any of the CI scripts/infrastructure for gdc and use it to make binary packages out of, then be my guest and raise a pull request to add that functionality.

how someone can test a project against GDC based on e.g. DMD 2.083, 2.082 and 2.080?

This question makes little sense as gcc and dmd release versions are mutually exclusive (there is no double-barrelled versioning).

@AndrewEdwards
Copy link
Contributor

CC: @PetarKirov @MartinNowak @CyberShadow

@Bobo1239, based on @ibuclaw's comments, there will be no packaging of GDC outside of the official GCC release. If we still intend to install GDC via the install.sh script, the DMD release management team will need to package and host the binaries themselves.

Should you choose to accept this responsibility, then this pull request remains valid. Otherwise, it will not be supported and, therefore, should be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants