eternal-lands-1.4.0 is released today and the version presently in Portage can not connect to their servers any more. Reproducible: Always
Hmmm, their current cvs doesn't build on my amd64 and they have not provided a source tarball - again. I'm also away for a month, leaving in 3 hours so don't expect a quick fix from me. Maybe the games team can fix this whilst I'm away.
Created attachment 121103 [details] el ebuild
Created attachment 121105 [details] el-data ebuild
A bump seems to work fine for the most part on amd64. The only issue was a collission warning on: /usr/share/games/eternal-lands/languages/en/books/sedicolis_riseandfall.xml Maybe it is just my install - obviously that file should be part of eternal-lands-data. Obviously you'll need to tarball the latest cvs - I'd attach mine but I'm guessing a dev would prefer to obtain it directly from the source. Also, the subdirectory in the install zip changed names (again), so eternal-lands-data needs a tiny patch. Also - I removed the createdir patch. I'm not sure if it is needed or not any longer, but it doesn't apply cleanly so something will need to be done with it if it is kept. I attached my ebuilds. I'm an amd64 AT so if you need anything on this arch let me know...
(In reply to comment #1) > Hmmm, their current cvs doesn't build on my amd64 and they have not provided a > source tarball - again. > Hmm - I'd be happy if they even tagged the official release version in cvs so that I'm not just hoping that HEAD even works...
Ebuild is missing sdl-image dependency.
*** Bug 181315 has been marked as a duplicate of this bug. ***
Created attachment 122635 [details] eternal-lands-1.4.0.ebuild (In reply to comment #6) > Ebuild is missing sdl-image dependency. > Fixed this (untested). The web site says that it also depends upon "OpenAI", but I couldn't find such a package. Also, a major problem, they don't appear to have created a tag for 1.4.0 in cvs!! I'm going to post on their forum and see what I can come up with. Daniel
The dependency is on OpenAL, not OpenAI.
Created attachment 122657 [details] eternal-lands-1.4.0.ebuild Now working ebuild with support for map-editor. Still need eternal-lands-data ebuild (I'm using the pre-compiled package for the data dir now). Needs patch (to follow) (In reply to comment #9) > The dependency is on OpenAL, not OpenAI. Yea, I figured that out a bit later.
Created attachment 122659 [details, diff] patch to Makefiles for 64-bit compatibility patch goes in ./files
tarball at http://www.javamonger.org/files/elc_140.tar.bz2. This is actually the HEAD as of today (June 20, 2007). Unfortunately, they haven't created a tag for any 1.4.0 release even though this is what the server is running. This "snapshot" works well enough although I've seen a few minor quirks (+xp messages appear too high above head, etc).
Created attachment 122663 [details] eternal-lands-data-1.4.0.ebuild Uses current data from GNU/Linux pre-compiled full install. Music has not changed since 1.3.3 (using same data file for that). New binary for data at http://el.beplacid.com/downloads/el_linux_install_140.zip.
There's a minor problem with the ebuild. It's not creating the icon for the client when map-editor is enabled. Any ideas on this anybody? I'll mess with it some (this is my 1st ebuild).
Created attachment 122917 [details] eternal-lands-1.4.0.ebuild As per discussion at http://www.eternal-lands.com/forum/index.php?showtopic=35164, I have grabbed sources from Sun Jun 3 19:02:15 UTC 2007 and calling them a final release (even though they never tagged it and probably wont). There was apparently a few patches later that day that effected Windows, but it wont effect the GNU/Linux distro. [code] cvs -d:pserver:anonymous@cvs.elc.berlios.de:/cvsroot/elc login cvs -z3 -d:pserver:anonymous@cvs.elc.berlios.de:/cvsroot/elc co -D 'Sun Jun 3 19:02:15 UTC 2007' elc map_editor [/code] and tarballed them and uploaded to http://www.javamonger.org/files/eternal-lands-1.4.0.tar.bz2. I used Gentoo standard versioning conventions, breaking away from the elc_xxx.tar.bz2 convention, since they aren't putting out tarballs anyway.
These should be ready to go. Perhaps somebody can independently test them and we can get them pushed? (I don't even have privileges to change the bug status)
I somehow can't compile el using atatched ebuilds and source from comment #12 Error is: g++ -march=i686 -mtune=pentium4 -pipe -O2 -DDATA_DIR=\"/usr/share/games/eternal-lands/\" -DLINUX -DELC -Dcached-virtuals -Dcollision-protect -Ddistlocks -Dparallel-fetch -Dsandbox -Dsfperms -Dstrict -Dunmerge-orphans -DAFK_FIX -DALPHA_ACTORS -DATI_9200_FIX -DAUTO_UPDATE -DCOUNTERS -DCUSTOM_LOOK -DCUSTOM_UPDATE -DEYE_CANDY -DFONTS_FIX -DFUZZY_PATHS -DIDLE_FIX -DMASKING -DNEW_ACTOR_ANIMATION -DNEW_ALPHA -DNEW_E3D_FORMAT -DNEW_FRUSTUM -DNEW_TEX -DNOTEPAD -DOPTIONS_I18N -DSFX -DSIMPLE_LOD -DUSE_INLINE -DZLIB -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/libxml2 -fno-strict-aliasing -c -o cal3d_wrapper.o cal3d_wrapper.cpp <command line>:1:7: warning: missing whitespace after the macro name <command line>:1:10: warning: missing whitespace after the macro name <command line>:1:9: warning: missing whitespace after the macro name <command line>:1:8: warning: missing whitespace after the macro name /usr/include/cal3d/springsystem.h:52: error: expected ‘,’ or ‘...’ before ‘-’ token make: *** [cal3d_wrapper.o] Error 1 make: Leaving directory `/var/tmp/portage/games-rpg/eternal-lands-1.4.0/work/eternal-lands-1.4.0/elc' i have installed cal3d-0.11.0-r1 (without 16bit-indices) gcc version 4.1.2 (Gentoo 4.1.2)
ops sorry for spam sources are from comment #15
(In reply to comment #18) Very curious indeed! This is caused by the collision-protect FEATURE (in /etc/make.conf). It replaces an occurrence of the word "collision" with "-protect", leading to the above error. For now, I'll put something in the ebuild that looks for this and blows up on it rather than this strange error. I'm also somewhat clueless on the "missing whitespace after the macro name" warning as well, but at least it's not (from what I can tell) interfering with the build. To see what I mean, run the emerge, change to the source directory (under tmp/portage, etc) and run the last command changing the output file to a ".i" instead of ".o" and add "-E" as an option (so gcc will output the preprocessed file). Thanks for the help on this Jetchko.
Created attachment 124600 [details] eternal-lands-1.4.0.ebuild Checks for collision-protect FEATURE and blows up if it's on. This is a work-around for some strange/stupid/wierd/mysterious problem that causes an instance of the word "collision" to be replaced by "-protect" on line 52 of /usr/include/cal3d/springsystem.h.
I saw that something goes wrong because of FEATURES environment variable used from both portage and el makefiles, but didn't find what exactly is problem. Now, when problem is known i think i have better fix for that how about adding these 2 lines at end of src_unpack() ? sed -i -e 's:FEATURES:EL_FEATURES:' elc/make.defaults sed -i -e 's:FEATURES:EL_FEATURES:' elc/Makefile.linux that way environment variables does not got messed up
I no longer have the time or motivation for this, sorry. Anyone want to become a dev to manage it?
Hello, version 1.5.0 is out, 1.4.0 cannot connect to server anymore.
Yup - I have a working ebuild for it (minus sound), but you can't actually build it with the version of glext.h that comes with eselect-opengl. I already filed a bug to update that, and then I'll open a new bug for el 1.5. Let me know if you need the ebuild anyway (takes some manual effort to get it working due to the glext.h issue) - I can send it to you. This bug should probably get closed since I don't think we want to mix 1.4 and 1.5. And long term I'll probably end up maintaining el - I'm working on becoming a dev...
Note - I created bug 201161 to track v1.5. I think this bug can be safely closed out.
Should've used this bug. *** This bug has been marked as a duplicate of bug 201161 ***
(In reply to comment #26) > Should've used this bug. > > *** This bug has been marked as a duplicate of bug 201161 *** HAH! No kidding. Even worse, I don't think that my ebuild (1.4) ever got put into the tree. I'm not playing anymore, so if somebody else gets a working 1.5 ebuild, I hope it actually makes it into the tree before it's antiquated by a new version on the server.
