Gdmd compiling error

Ali Çehreli via Digitalmars-d-learn digitalmars-d-learn at puremagic.com
Mon Mar 14 11:13:33 PDT 2016


On 03/14/2016 10:08 AM, Marc Schütz wrote:

 > What does `which gdc` print? If it says something like "which: no gdc in
 > ...", there is a problem with the installation of GDC. Otherwise, you
 > can use the following as a quick workaround:
 >
 >      sudo ln -s `which gdc` /usr/local/bin/gdc
 >
 > The proper solution is to find out why gdmd insists on using that
 > non-existing path instead of relying on $PATH lookup, and fix it.

Apparently, gdmd expects gdc to be in the same directory as itself. Once 
Orkhan finds out where gdc is on the system, the following should work:

$ sudo ln -s 
/home/acehreli/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-gdc 
/usr/local/bin/gdc

Orkhan, replace 
/home/acehreli/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-gdc with the 
gdc binary that you have. e.g. if it's under /usr/bin, then do the 
following:

$ sudo ln -s /usr/bin/gdc /usr/local/bin/gdc

Ali

P.S. I've just installed gdc after downloading it from its download site 
( http://gdcproject.org/downloads ) with the following two commands:

   unxz the_file_you_downloaded
   tar xvf the_file_you_unxzipped

Those commands created the following directory in my case.

   /home/acehreli/x86_64-pc-linux-gnu

That's why my gdc is named 
/home/acehreli/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-gdc above.



More information about the Digitalmars-d-learn mailing list