Awesome!

On Fri, Aug 3, 2012 at 10:25 AM, Mike James <foo@bar.com> wrote:

Well, I installed "by hand" on windows, as I did for the previous
releases and nothing links anymore.
Then, at home, the same for linux. I did the exact moves/copies I did
for 2.057, 2.058 and 2.059 and I never had this problem before.

So now, all my DMD installs are broken :) What was changed in this release exactly?

What Jonathan, what do you mean by old .di files? I never create any .di

On 8/3/12, Philippe Sigaud <philippe.sigaud@gmail.com> wrote:
> On Fri, Aug 3, 2012 at 10:25 AM, Mike James <foo@bar.com> wrote:
>
> Well, I installed "by hand" on windows, as I did for the previous releases and nothing links anymore.

Not even a simple void main()? Usually when I upgrade I have to recompile all my dependencies of a project because otherwise it won't link.

On Fri, Aug 3, 2012 at 7:22 PM, Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:
> On 8/3/12, Philippe Sigaud <philippe.sigaud@gmail.com> wrote:
>> On Fri, Aug 3, 2012 at 10:25 AM, Mike James <foo@bar.com> wrote:
>>
>> Well, I installed "by hand" on windows, as I did for the previous releases and nothing links anymore.
>
> Not even a simple void main()? Usually when I upgrade I have to recompile all my dependencies of a project because otherwise it won't link.

No, not even void main().

And the .deb never worked for me, nor the windows installer, nor dvm (downdload files, but never change the links since 2.057 and never call the correct compiler).

Sigh. That'll be a nice evening...

On 03-Aug-12 20:57, Philippe Sigaud wrote:
> On Fri, Aug 3, 2012 at 10:25 AM, Mike James <foo@bar.com> wrote:
>
> Well, I installed "by hand" on windows, as I did for the previous
> releases and nothing links anymore.
> Then, at home, the same for linux. I did the exact moves/copies I did
> for 2.057, 2.058 and 2.059 and I never had this problem before.
>
> So now, all my DMD installs are broken :) What was changed in this
> release exactly?
>

> What Jonathan, what do you mean by old .di files? I never create any .di

If you (like I did) just extract zip over your dmd installation this could lead to unpleasant surprise as some  files should be now deleted yet new compiler will happily pick up old ones and get to a link error.

Just obliterate your previous installation before setting up new one :)

-- 
Dmitry Olshansky

On Fri, Aug 3, 2012 at 7:48 PM, Dmitry Olshansky <dmitry.olsh@gmail.com> wrote:

> If you (like I did) just extract zip over your dmd installation this could lead to unpleasant surprise as some  files should be now deleted yet new compiler will happily pick up old ones and get to a link error.
>
> Just obliterate your previous installation before setting up new one :)

sudo apt-get obliterate dmd
sudo apt-get reinstall-by-hand dmd

It worked!

I don't remember having to do that before. I'll try that on Windows.

A big thanks!

On 2012-08-03 14:47, Jordi Sayol wrote:

> https://github.com/D-Programming-Language/installer/blob/master/linux/dmd-completion
>
> It's based on "d-completion.sh" at https://github.com/Lutger/d_utils

How about that. It should absolutely be bundled with the .zip.

-- 
/Jacob Carlborg

Al 03/08/12 21:22, En/na Jacob Carlborg ha escrit:
> On 2012-08-03 14:47, Jordi Sayol wrote:
> 
>> https://github.com/D-Programming-Language/installer/blob/master/linux/dmd-completion
>>
>> It's based on "d-completion.sh" at https://github.com/Lutger/d_utils
> 
> How about that. It should absolutely be bundled with the .zip.
> 

dmd deb and rpm packages include it, but this script do not works out of the box. bash-completion package must be installed, and the script should be placed in a specific folder.
-- 
Jordi Sayol

On 2012-08-03 22:27, Jordi Sayol wrote:

> dmd deb and rpm packages include it, but this script do not works out of the box. bash-completion package must be installed, and the script should be placed in a specific folder.

Unfortunately those packages don't work on Mac OS X :) . I have the bash completion package installed via macports.

-- 
/Jacob Carlborg

On Friday, August 03, 2012 18:57:29 Philippe Sigaud wrote:
> On Fri, Aug 3, 2012 at 10:25 AM, Mike James <foo@bar.com> wrote:
> 
> Well, I installed "by hand" on windows, as I did for the previous
> releases and nothing links anymore.
> Then, at home, the same for linux. I did the exact moves/copies I did
> for 2.057, 2.058 and 2.059 and I never had this problem before.
> 
> So now, all my DMD installs are broken :) What was changed in this release exactly?
> 
> What Jonathan, what do you mean by old .di files? I never create any .di

druntime does. There was some shuffling around with that this release. Most of druntime no longer creates .di files anymore but rather just copies over the .d files. I don't know exactly what the deal is with core.memory and core.bitop, but there were issues with them if the imports directory wasn't properly cleaned out (and druntime's makefile's clean target didn't clean it out properly for a bit there), resulting in errors along the lines of what the OP reported. It probably ended up with a .di and .d file next to each other, but I'm not sure. I suspect that the Windows installer fails to remove the old stuff if you don't uninstall first, so you end up with a bad install if you don't uninstall first, but I don't know.

- Jonathan M Davis