On Saturday, 19 September 2015 at 16:44:51 UTC, Laeeth Isharc wrote:
> On Saturday, 19 September 2015 at 15:46:32 UTC, Rinzler wrote:
>> On Saturday, 19 September 2015 at 15:32:33 UTC, Laeeth Isharc wrote:
>>> On Saturday, 19 September 2015 at 10:21:30 UTC, Rinzler wrote:
>>>> On Saturday, 19 September 2015 at 10:17:21 UTC, Jacob Carlborg wrote:
>>>>> On 2015-09-19 12:05, Rinzler wrote:
>>>>>>> what does "which dmd" give you?
>>>>>>
>>>>>> Nothing...
>>>>>
>>>>> And "type dmd | head -n 1"? If that gives you some kind of path, what does then "file <path>" print?
>>>>
>>>> I don't even have a tool called "type"? Should I install it just for testing this?
>>>
>>> He means type ie enter the following line in the console:
>>>
>>> dmd | head -n 1
>>
>> It gives me: -bash: dmd: command not found
>>
>> Now, suddenly and mysteriously, if I type
>>
>> dmd,
>>
>> I get
>>
>> -bash: dmd: command not found .
>>
>> Really strange...
> "
> I had installed `dmd` using `brew` some time ago, and now I was trying to use `dmd` again, but I keep getting the following error:
>
> `dmd: failed to launch executable at /Library/Compilers/dmd2/osx/bin/dmd`.
>
> Even after doing `brew uninstall dmd` and `brew uninstall dub`, I keep getting the same error.
>
> I had already had some problems of linking when I first tried to use it, and I think I had tried to install and uninstall it some times.
>
> Now, if I go under `/Library/Compilers` I have no folder. In my `.bash_profile` file, I have no path related to `dmd` that is being exported.
>
> I have also removed the `dmd` executable and the `dmd.conf` file under `/usr/bin`, but nothing has changed.
>
> How can I remove previous links to `/Library/Compilers/dmd2/osx/bin/dmd`?
> "
>
> After you uninstalled it, how did you reinstall it again ?

I don't remember anymore exactly, but I think that I tried both with the .dmg package downloaded from this website and with brew.

On Saturday, 19 September 2015 at 16:44:38 UTC, Rinzler wrote:
>> Quick point about paths and so on: if you don't understand what's going on, or have just made a change and want to be sure whether it worked, always open a new terminal session and try again. There are caches that can need emptying, environment variables that get inadvertently set etc.
>> I can't count the number of times I've been convinced somethings completely broken only to start a new terminal and find it all makes perfect sense again.
>>
>> Totally simple, obvious advice, I know, but nonetheless always worth repeating.
>
> Thanks for the advice.
>
> By the way, do you know a clean way to manage the installation and eventually the uninstallation of dmd, and all libraries related to D, etc, so that I don't have anymore these kind of problems?

Compilers and tools: If possible let homebrew manage everything. If not feasible, use a separate folder for manually installed tools, don't let them get confused with installations from installers, package managers or system tools.

Libraries: let dub handle them, if possible. If not possible, see above.

On Saturday, 19 September 2015 at 17:44:22 UTC, John Colvin wrote:
> On Saturday, 19 September 2015 at 16:44:38 UTC, Rinzler wrote:
>>> Quick point about paths and so on: if you don't understand what's going on, or have just made a change and want to be sure whether it worked, always open a new terminal session and try again. There are caches that can need emptying, environment variables that get inadvertently set etc.
>>> I can't count the number of times I've been convinced somethings completely broken only to start a new terminal and find it all makes perfect sense again.
>>>
>>> Totally simple, obvious advice, I know, but nonetheless always worth repeating.
>>
>> Thanks for the advice.
>>
>> By the way, do you know a clean way to manage the installation and eventually the uninstallation of dmd, and all libraries related to D, etc, so that I don't have anymore these kind of problems?
>
> Compilers and tools: If possible let homebrew manage everything. If not feasible, use a separate folder for manually installed tools, don't let them get confused with installations from installers, package managers or system tools.
>
> Libraries: let dub handle them, if possible. If not possible, see above.

Ok, thanks, I will try to follow those advices.

On 2015-09-19 12:21, Rinzler wrote:

> I don't even have a tool called "type"? Should I install it just for
> testing this?

What? "type" is a shell builtin.

-- 
/Jacob Carlborg

On 2015-09-19 17:32, Laeeth Isharc wrote:

> He means type ie enter the following line in the console:
>
> dmd | head -n 1

No, "type" is a command, a shell builtin, that's why it was inside the quotes.

$ type type
type is a shell builtin

-- 
/Jacob Carlborg