Re: eudist.mak: No such file or directory
- Posted by jimcbrown (admin) Jan 06, 2013
- 1244 views
This is odd. You say that mw32/eudist-build/ does not exist/is not created, yet make appears to cd into it correctly. (If the directory didn't exist, then make should have errored out, explicitly stating that reason.)
Also, you have EUPHORIA=1 in your config.gnu, but there's no attempt to call eui to generate mw32/eudist-build/main-.c ... either EUPHORIA is getting unset or set to 0, or else main-.c already exists.
Yes correct i have created them, because i was getting errors trying to compile euphoria.
Ok. Now the errors make sense. (For future reference, stating that you did this in the begining would have helped a lot.) To debug the real issue, we'd need to remove the fake make-.c and eudist-build, and retry the build.
However, the failure to build eudist is probably caused by the issue with eui.exe - the newly built eui.exe is used to build the tools (starting with eudist).
So, what probably happens: make tried to call the new eui to build eudist, eui didn't do anything, and make errored out because eui failed to create make-.c and eudist.mak
It remains unclear why eui.exe is failing. (I wonder if it is just eui, or if euiw and euc and eub and eubw also have issues.) But it might be necessary to use a 4.1 binary to build 4.1 (I don't know the last time anyone has successfully built 4.1 witha 4.0 binary).
I don't remember when it last worked without errors.
But anyway thank to you and matt for looking into this
I will abandon any further atempt trying to build eu.
When should we expect the next release?
Currently, there are no release dates for 4.0.6 or 4.1.0
4.1.0 has been held up indefinitely (I think at least roughly half a year).
At this point in time, I feel very pessimistic - in the entire time that 4.1.0 has been held up, no visible progress has been made in getting the issues responsible fixed. A holdup of 2 or 3 more years feels realistic to me.
4.0.6 will probably come along in a few months (or at most a year) - whenever someone feels that we've released enough bug fixes to 4.0.5 to warrant a new release.
