Re: Compiling RC2 on Windows: failed
- Posted by jimcbrown (admin) Dec 12, 2010
- 1167 views
Due to the innmediate responses from developers, this might be seen as a bit out-dated. Anyway, I think there are a couple of things that worth being clarified.
I guess you have EUDIR set. So configure.bat sees EUDIR and defaults to -with-euphoria.
You need to manually run configure with the -without-euphoria option.
I already run configure with and without --without-euphoria option and the result is the same.
However, what you might not understand is that one cannot build Euphoria with only a C compiler and linker as your tool set. This is because a lot of Euphoria is written in Euphoria itself and only some portions of it are written in C.
In order to build Euphoria, one must have either a working Euphoria interpreter plus a C compiler and linker.
What you might not understand is that if you (the developer) put an option --without-euphoria in configure.bat, that means without euphoria (interpreter). If that's not the case, please remove the option from configure help.
After investigating the cause of the bug, we've discovered that it's a bug in the build process that --without-euphoria is essentially being ignored. This is only a problem for the Windows watcom build, because of its separate build system. (As far as we know, using MinGW to build the pretranslated sources should work, but no one has tested this, so it is possible we have more bugs lurking in that area as well.)
This bug is really hard to fix, and since the plan is to drop the current watcom build system and go with a unified one, we've decided that it's not worth the effort. So for windows, you will need to have a working Euphoria interpreter in order to compile Euphoria. This is a bug, but it will probably not be addressed until after 4.0 is released, unless one of the devs figures out a quick fix in the meantime or someone else fixes it and submits a patch.
For me not being able to compile Euphoria is a serious problem. Please note that this is not the first time I tried to do it. A few days ago, I submitted a bug request for the same reason. I downloaded eubins r4511 and source r4511 and failed. I remembered you pointing me going backwards to another revision and then upgrading to another... all of which had nothing to do with which I was informing because I was trying to compile from a clean installation.
That was a real problem with eubins that you found. It's been fixed now, in part thanks to your efforts.
I could add more examples like receiving error messages while running code with the interpreter, telling about asserts failing and pointing me to .c source files that have nothing to do with what I was doing.
If I don't submit every problem I encounter is because I use Euphoria neither for production nor have any project in mind using it, though I like to do it since I think Euphoria has a great potential. Just playing with it for fun but a fun that is resulting not so funny.
You don't have to submit bug reports for every bug you find. Time is valuable and writing bug reports all the time is probably not the most exciting thing in the world.
Still, every bug report you find and submit helps. Even if we find that a bug is invalid or won't fix, having the ticket at least documents the situtation for the benefit of future users. And, most bug reports that are filed turn out to be real bugs that need to be fixed. I want to say on behalf of the developers that your efforts are important and appreciated.
