Re: DMD travis-ci problems with new GDC toolchains

2016-12-31 Thread Iain Buclaw via Digitalmars-d
On 25 December 2016 at 20:25, Johannes Pfau via Digitalmars-d wrote: > Happy holidays everybody, > Happy New Year. > when testing the new GDC releases we found several problems with the > travis-ci autotester. Travis-CI uses the quite old GCC 4.6 as a system > GCC

Re: DMD travis-ci problems with new GDC toolchains

2016-12-27 Thread Johannes Pfau via Digitalmars-d
On Tuesday, 27 December 2016 at 04:17:31 UTC, Martin Nowak wrote: On Sunday, 25 December 2016 at 19:25:40 UTC, Johannes Pfau wrote: This is not place to post bug reports. It was only by chance that I read it. Sorry, but I thought some idea gathering before fileing a report could be useful.

Re: DMD travis-ci problems with new GDC toolchains

2016-12-26 Thread Martin Nowak via Digitalmars-d
On Sunday, 25 December 2016 at 19:25:40 UTC, Johannes Pfau wrote: This is not place to post bug reports. It was only by chance that I read it. Better file a Bugzilla Ticket, and notify the author of related tools/scripts. Since noone can monitor everything surrounding D, mailing the author

Re: DMD travis-ci problems with new GDC toolchains

2016-12-26 Thread Jacob Carlborg via Digitalmars-d
On 2016-12-25 20:25, Johannes Pfau wrote: There's also a related issue with libatomic: In order to support 128bit operations in core.atomic GDC has to link libatomic. libatomic is not available on ubuntu 12.04... An alternative could be to use Docker to run a later version of Ubuntu, if

DMD travis-ci problems with new GDC toolchains

2016-12-25 Thread Johannes Pfau via Digitalmars-d
Happy holidays everybody, when testing the new GDC releases we found several problems with the travis-ci autotester. Travis-CI uses the quite old GCC 4.6 as a system GCC and the oldest GCC version supported by GDC is 4.8. As the install.sh scripts prepends the downloaded toolchain to the PATH