Ethanagor wrote:Alright, sorry for posting so many questions. This should be the last one, and I can delete all of them when I am done if necessary.
No need, and I think these have all been good "basic questions". If you're having trouble getting through all these compilation steps, other people will probably run into the same problems.
Ethanagor wrote:I used a different mirror to download Cygwin, and it worked perfectly. I compiled the program. However, when I try to run the executable I get an error message stating that cygwin1.dll is missing...
Yup, so far so good -- the cygwin1.dll error is normal behavior if you're not running the program through the Cygwin terminal window. You can think of cygwin1.dll as kind of a reference encyclopedia for your compiled program, to allow your Windows system to behave more like Linux.
A little more detail: Windows has a PATH variable, which is just a chunk of text that lists all the folders that Windows should look through when it can't find something. When you open the Cygwin terminal, the PATH variable is temporarily modified to include the folder that your cygwin1.dll is in -- which theoretically will prevent that error.
Other "command prompt" links will do the same kind of thing. For example, if you download the free Visual Studio Community or Express
from Microsoft, you'll get a "Visual Studio Command Prompt" link installed. If you then tried to do a Visual Studio compilation from a Cygwin command prompt, or a standard Windows command prompt, you'd get errors because Windows wouldn't know where the Visual Studio compiler and all its required library files were.
(I'd say don't try Visual Studio yet -- I might see if I can compile slmake with it, and write up a quick walkthrough. But I don't see the segmentation fault you're running into, so that might not solve your problem in any case.)
Ethanagor wrote: ... and when I try to run it through the command line as described in your forum post I get an error stating "Segmentation fault (core dumped)". What am I doing wrong?
Now you've gotten beyond my (rather limited) experience with Cygwin, I'm afraid. It's not supposed to do that, of course, and I don't know why it's happening on your system.
One experiment that might be worth trying: put a copy of cygwin1.dll in the same folder with the executable you compiled
, and see if you can then run the program starting from a regular command prompt. You can get to a standard Windows command prompt by searching using your Start bar for cmd
Has anyone else run into this kind of segmentation-fault error, trying to run a Cygwin-compiled slmake? I'm not sure what troubleshooting steps to suggest next.