Re: ver. 4.0 WIN98 Binaries

new topic     » goto parent     » topic index » view thread      » older message » newer message

From the very latest svn, here is the entire tree including prebuilt binaries (in eu40\source which need to be copied over to eu40\bin)

http://malcom.unkmar.com/eu40.zip

Binaries, source, includes, docs, demos, etc

bernie said...
jimcbrown said...
bernie said...

The program crashs during the parse of a large program and I don't know

where it is crashing; all I get is the above error.

Ok, if it works fine for small programs (like buzz.ex) then you may have found a bug. :)

Do you have the svn source directory checked out? If you do, please test your program with int.ex and report back what happens.

bernie said...


The problem is that the binary zip file was suppose to be SVN 1159.

The binaries inside the zip file were SVN 1160.

Hopefully this is fixed now. Not that it should make a difference.

bernie said...


Therefore I have no idea what SVN include files were used to compile
the binaries; I have been always using the SVN include files that match
the binaries SVN and not had any problem.

Why not build the binaries yourself?

bernie said...


What you don't seem to realize is that it is IMPORTANT that if you compile
binaries that the SVN of the binaries MUST match the SVN of the include
files because I can not guess what include files were used.

If I use newer or older include files I will get error's because
of feature changes and bug fixes.

In general this is true, but having mismatched include files should never cause the interpreter itself to crash. Not with a segfault.

One possible solution is simply to zip up the entire svn checkout tree after the binaries are built. Then you have both the includes and the binaries, as well as the source used to build them.

bernie said...

The easiest solution is to please make new WIN98 binaries using the
same SVN include files.

My understanding is that this is always the case. The issue was with revget.ex but the includes and the source code used to build the binaries were in fact at the same revision.

jim said...

One possible solution is simply to zip up the entire svn checkout tree after the binaries are built. Then you have both the includes and the binaries, as well as the source used to build them.

Please, then someone has to do this so I can get around the problem.

I can not build my self if I have no binaries that work.

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu