I don't know which glest version I checked out, but I think it is 0.3.0 trunk (I used the command svn co https://glest.codemonger.org/svn/repos/gae/trunk glest)
I'm sorry, I'm still thinking CVS. What I meant was the trunk. Please check out
https://glest.codemonger.org/svn/repos/gae/branches/0.3 or
https://glest.codemonger.org/svn/repos/gae/branches/0.2.x. There is currently work going on in both branches. If you want a more stable release, grab
https://glest.codemonger.org/svn/repos/gae/tags/0.2.11. If I understand svn correctly, I think that the "trunk" would be the state from the last time we merged it (which would have been long ago). Maybe we should remove it? I'm not certain really, maybe we should just be merging back into the trunk when we release stable? Anybody know what the best practices is for this?
My gcc-version is 4.3.3, my glibc-version is 2.9-12.2
Adding the line
CPPFLAGS += -D_XOPEN_SOURCE=600
gives me
oops, I'm sorry, I'm thinking Makefile (I should have tested it myself before posting it). Just add a space and a semi-colen to what I gave you so it looks like this:
CPPFLAGS += -D_XOPEN_SOURCE=600 ;
if ! $(top_builddir)
{
top_builddir = $(TOP) ;
}
top_srcdir = $(TOP) ;
.
.
.
Alternately, you can edit Jamconfig and find the first instance of CPPFLAGS += (it appears multiple times
) and add "-D_XOPEN_SOURCE=600" to it. I'm not even 100% certain this will fix the problem, I read that I'm supposed to #include <features.h> when using this but maybe that's included internally by glibc's headers, I'm not sure. Either way, I would like to know if it fixes it and just generally make sure that it will either compile or the configure script will fail telling you what it needs.
ft-jam gives me the same errors (plus when I compile ft-jam, it gives me a warning about an implicit declaration of a built-in function) - and if ft-jam worked, boost-jam should work too because this is based on that.
Can you please post the errors you get with boost-jam and ft-jam? I can probably reproduce it myself, but it would be helpful if you have that info handy. Thanks!
[/quote