dmd with Gentoo linux not working

jicman · Joined: 22 Dec 2004 Posts: 298 Location: Rochester, NY

I am getting the error message:

mulo 01:02:26-> dmd
-bash: /h/jicman/bin/dmd: cannot execute binary file

and it's setup as an executable:

mulo 01:02:49-> ls -l bin/dmd
-rwxr-xr-x 1 jicman users 1029633 Dec 14 01:03 bin/dmd*

Has any one successfully run dmd from linux? If so, any tricks to get it to work? I followed the instructions and everything seems ok, but I don't think the binary file is ok for Gentoo.

thanks.

josÃ©

larsivi · Posted: Thu Dec 23, 2004 8:25 am Post subject:

It works for me on Gentoo... Didn't do anything special, I think.

Btw, I don't think this is the right group for the question.

JJR · Joined: 22 Feb 2004 Posts: 1104

Yes, this topic should probably be moved to "General."

To answer the question. I've been running dmd under x86-based Gentoo Linux for quite some time. Are you using x86-based Gentoo? The only reason I can think that it doesn't work out of the box is if you are trying to run dmd on a powerpc based Gentoo (or some other cpu).

Oh wait a minute....

It looks like you are trying to run dmd from the command prompt without specifing the full pathname. On linux systems, unless the current path has been entered into the PATH environment variable, you can't run an executable even if you are currently in it's directory. Perhaps that's your problem?

Thus:

JJR · Joined: 22 Feb 2004 Posts: 1104

On further investigation. What I said above doesn't seem to apply to your problem. The error message you show tends to indicate that dmd is found, but Bash doesn't know what to do with the executable. Oh well....

Carlos · Joined: 19 Mar 2004 Posts: 396 Location: Canyon, TX

Maybe what you need to do is "chmod ugo+x dmd". Ditto for the other executables in dmd/bin

jcc7 · Joined: 22 Feb 2004 Posts: 657 Location: Muskogee, OK, USA

andersRson · Joined: 30 Dec 2004 Posts: 1

try using the ebuilds, find them in bugzilla at http://bugs.gentoo.org/show_bug.cgi?id=48136, see the last attachment.
If you don't know how to use ebuilds not in portage, do it like this:
*Create a directory to use as your portage overlay directory. In this you put ebuild files that is not in official portage for some reason. It should have the same structure as the /usr/portage directory, but only for the files that you actually want to be there. Like the ebuilds for gdc and phobos, for instance.
add the line PORTDIR_OVERLAY="/path/to/your/directory" to /etc/make.conf.
*Create the directories 'dev-lang/gdc' and 'dev-libs/phobos' in the overlay directory and copy the files from bugzilla into the respective directory.
*do
#ebuild dev-lang/gdc/gdc-0.9.ebuild digest
and
#ebuild dev-libs/phobos/phobos-0.9.ebuild digest
in the overlay directory to let portage check them out.
Now, you should be able to emerge them as usual.

Workaphobia · Joined: 24 Jun 2004 Posts: 17

I don't think you need to do anything funky to get it to work, just try adding it to your $PATH variable.
export PATH=$PATH:/pathtodmdhere
I'm not exactly sure what the difference is between export and set, but I think that's the one I see used for this sort of thing.

Without changing $PATH, I think using the syntax ./dmd worked for me when I wanted to run an executable.
_________________
"Nifty News Fifty: When news breaks, we give you the pieces."