DMD travis-ci problems with new GDC toolchains

[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.

>> * Append the toolchain location to PATH instead of prepending
>
> The goal of the activate scripts is to switch the current 
> compiler, that includes hiding a system wide installation of 
> dmd, so this wouldn't work.

That's what I expected.

>> * Add the location to the toolchain libstdc++ to 
>> LD_LIBRARY_PATH
>
> Sounds like a reasonable solution to me, link with what you use 
> for compiling.
> We're already setting up LIBRARY_PATH and LD_LIBRARY_PATH for 
> the selected version.
> https://github.com/dlang/installer/blob/92315cdf58b32178f2c4865db87123d433f45406/script/install.sh#L575
>
> In fact this looks like an incompatibility of the install.sh 
> scripts with your new multilib gdc (using lib32/lib64 instead 
> of lib).

I didn't know install.sh already sets the variables. So this is 
probably the best solution for now. This should also did the 
libatomic problem.