Trying to compile ETeng 0.3

(cheesy) #1

I am trying to compile ETeng with lower glibc version, because I tried to load the mod on gameservers.com and it fails with error message stating that it cannot find glibc 4.x, which makes sense because their servers use older glibc.

I would like to get this re-compiled but have an endless supply of errors (more than I should post in a thread). I have been using debian etch 4.0 which has glibc 2.3 for about 5 years, and this is compatible with what gameservers.com uses.

I am probably just compiling it wrong. Should I be using scons for this? Also, I installed the latest nasm so I don’t think that is the issue.

(please do not try to derail my thread, because I bite)

ETeng source
http://mygamingtalk.com/forums/files/file/20-eteng-source/

(cheesy) #2

here is the error I am getting on both debian etch and mint 11…

scons: *** [build/release/dedicated/splines/math_angles.o] Error 127

(Radegast) #3

ETeng 0.3 compiled on Debian 6 with glibc 2.11.3: http://mirror.etlegacy.com/eteng-0.3-lin.tar.gz

Hope this works. However, I would really recommend you to try ET:Legacy when it gets to a stable version.

(morsik) #4

Or you can use etlegacy git now which is the best option now. It works for now without any problem, and we are working on it still.
ETeng developer joined us, so all ETend features/security fixes will be ported to ET:Legacy, and probably no more ETeng will be released.

(cheesy) #5

[QUOTE=Radegast;398990]ETeng 0.3 compiled on Debian 6 with glibc 2.11.3: http://mirror.etlegacy.com/eteng-0.3-lin.tar.gz
Hope this works. However, I would really recommend you to try ET:Legacy when it gets to a stable version.[/QUOTE]
Thank you. Testing now. It seems to be working, however since gameservers is in charge of the command line, I can’t be sure they made the switch. Whats a good way to verify this binary is loaded? I see nothing about it in the logs.

@ Morsik
I hope I am wrong, but I think you are indirectly asking me to switch my servers to 2.60b, away from 2.55+, and remove my servers from the 2.55 master list right? That would kill all my business. It would be like quitting my job and taking a bus to the east coast and hoping for the best.

I like solutions such as ETeng, because it provides a backwards compatible solution, that does not discriminate against the protocol.

but if I am wrong, and it supports my 2.55 players, and keeps it on the same master list…let me know :slight_smile:

(Radegast) #6

Sorry, I have no idea how Gameservers hosting works, so I can’t help you.

You Americans use the word discriminate way to often. At first I thought we could make ET:L backwards compatible and it seemed an easy task to do so, but in reality it has so many drawbacks that it’s not worthwhile. We will make ET:L servers visible to 2.55 clients, but show them a link where to download ET:L 2.70 installer upon connecting.

If there is any way I can help you or your users to migrate to 2.70 then I’ll be more than happy to.

I just wanted to explain to you what’s the situatation with ET:L, I won’t derail you topic any further.

(morsik) #7

@cheesy: erm… why switching to 2.60 proto would kill your business? I don’t understand. Please tell us some good arguments why you need to stay with 2.55 because we just can not understand :\

And, if you know if your binary is working, just check first ling of logs - there is build date.

(cheesy) #8

ok…but remember you asked for it. It is not my goal to argue 2.55 versus 2.60b, but every time one asks for compatibility, they are led into debate.

Why would a server owner stick with 2.60b?

  1. Because 2.55 works
  2. Because my 2.55 players are not asking to get on 2.60b
  3. Because 2.55 players rarely (if ever) complain about exploit problems
  4. Because 2.60b players complain about the same problems 2.55 players do (etkey,guid,pb,graphics,hunkmegs,vista compatibility)…etc
  5. Because (3) of my servers are on the 2.55 master list, and I would like to keep them there
  6. While 2/3 of the servers are on 2.60b master list, about half the “players” are on 2.55 list
  7. Because 2.60b list is full of servers running omnibots, and full of etpro player types
  8. Because WolfET.exe points to 2.55 list by default, therefore is always being refreshed with new players
  9. Because WolfET does not auto patch like some games do, thus 2.55 list will be around forever
  10. Because I honestly never seen any of my players forced into 2.60b for any reason other than wanting to play on etpro, or mods that intentionally require it.
    (I got more if needed)

Listen man, 2.60b is great! I wish ET auto-patched directly to it when players installed the game. But that is just not the reality. Unless that little file named “WolfET.exe” disappears from the internet, there will always be 2.55. That being said, it should be supported. Sadly, many people are stuck on “patch…patch…patch” but do not understand the big picture.

(morsik) #9
  1. players don’t have to. But admins (like you) could. There’s high possibility that every server can be crashed by anyone. But we have to do some tests still…
  2. etkey,guid,hunkmegs problems are already solved, and vista/7 compability will be.
  3. i don’t see point in wanting to be seen on 2.55 list if you’ll have 2.60 proto
  4. so change that (-;
  5. we want to make autoupdater so clients and servers will stay with always latest version.
    also we wanted people just to do simple update from old clients. If client will connect from old 2.55, then he’ll get info about download new version, maybe even some button? It will be not much. Less than 5M - it’s much less than many maps out there!

BTW. What mod do you use on your server?

(cheesy) #10

I totally agree on everything ETL is trying to do (patches, etkey, crash fixes…etc). This is a nice project. However I am worried about the compatibility issue.

I always think in terms of new players, not as an ET vet and server owner. Lets assume we only support 2.60b with ETL, and lets think long-term. People start connecting to these servers, a little at a time, they get some sort of offer to upgrade, and they do…thats great.
Then a few server owners make the switch and put ETL on, and so now we have a few less servers on the 2.55 list…no problem.

Problem: the community is going to shrink

Example:
Incomes a new player, he just turned 14, its his birthday, and he wants to celebrate by playing a free game on his PC. This is where the problem begins…

New player downloads WolfET.exe
New player connects to 2.55 list…
New player sees very few servers with hardly anyone playing…
New player says screw this and disconnects and downloads a different game

We are better off having two protocols/lists that are partially active (like now) than having a dead 2.55 list, and a partially active 2.60b list.

Ideally this would be a better solution:

  • Figure out a way to merge lists
  • Have a server that supports all protocols (i.e., 2.55+)
  • Screw mods that dont want to be backwards compatible (i.e., etpro which is old now)

If this happened, then we could force a client upgrade and it does not impact the community (much like Call of Duty and other games).
Anything less is futile.
But since this is probably not possible, I say support all client versions (unconditionally).

(Shownie) #11

You don’t have to worry that much about new players. All links at Splash Damage has been changed and are now latest patch FULL installers on all OS. Hopefully most new players come by this site to download Wolf: ET (:

(morsik) #12

New player downloads WolfET.exe 2.55 because first Goolgle result gives that. So we must (fortunaletly or not) change that.
And we thought about supporting all protocols - now we support both, but we really think about dropping that and deny permanently 2.55 clients.

And yes. Community is going to shrink, that’s why we should merge it to use one newer version.

(cheesy) #13

Results of a quick search…

Wolf E T260 (257.8M)
http://magics-territory.com/et/wolfenstein%20game/WolfET260.exe
Magics Territory Wolfenstein Game - Wolfenstein: Enemy Territory (2.60/Windows) , Filesize 258M
(magics-territory.com)

Wolfet (257.8M)
http://dl.127001.org/games/wolf_et/wolfet.exe
Index of /games/wolf_et - wolfet.exe
(dl.127001.org)

Wolf E T 2 60b Custom (253.4M)
http://www.enemy-territory.fr/dl/win32/WolfET_2_60b_custom.exe
Télécharger Wolfenstein : Enemy Territory - Version plus récente (253 Mo)
(www.enemy-territory.fr)

Wolf E T (257.8M)
http://files.awesome-dudes.de/misc/wet/windows/WolfET.exe
Index of /misc/wet/windows - WolfET.exe
(files.awesome-dudes.de)

Wolf E T (257.8M)
http://downloads.eicher.tv/enemy-territory/win32/WolfET.exe
Index of /enemy-territory/win32 - WolfET.exe
(downloads.eicher.tv)

Wolf E T (257.8M)
http://downloads.hennecke-online.net/et/WolfET.exe
Index of /et - WolfET.exe
(downloads.hennecke-online.net)

Wolf E T (257.8M)
http://grow-room.co.uk/public/WolfET.exe
tgr’Public Downloads - WolfET.exe
(grow-room.co.uk)

Wolf E T (257.8M)
http://iostream.info/dl/et/WolfET.exe
Index of /dl/et - WolfET.exe
(iostream.info)

Wolf E T (257.8M)
exe software file
pomac.netswarm.net - wolfET.exe
(pomac.netswarm.net)

Wolf E T (257.8M)
exe software file
Monster Force • View topic - Enemy Terrirtory Client - http://www.monsterforce.net/ET/WolfET.exe
(www.monsterforce.net)

Wolf E T (257.8M)
exe software file
+Fk- & .pFk’ : Wolfenstein Enemy Territory • Afficher le sujet - Wolfenstein : Relancer la section ou pas ? - EDIT: Lien de téléchargement : http://et.fkclan.fr/dl/WolfET.exe
(et.fkclan.fr)

Index von ./etfiles/et/win/ - WolfET.exe Gesamtgrösse: 270.0 MB 2007-Jul-06 257.8 MB
(feierabendsoldiers.tlinet.de)

Wolf E T (257.8M)
exe software file
Castle Wolfenstein: Enemy Territory download on Free Games Headquartes.com - Click here
(freegamesheadquarters.com)

Wolf E T (257.8M)
exe software file
AbsolutelyFreeware - DOWNLOAD (Local Server)
(www.absolutelyfreeware.com)

Wolf E T (257.8M)
exe software file
team -=[KDM]=- :: Quelqu’un a du baygon ? :: -
(www.team-kdm.org)

Wolf E T (257.8M)
exe software file
Index of /pub/games/idgames/idstuff/et/win32 -
(gamers.org)

Wolf E T (257.8M)
exe software file
Magics Territory Wolfenstein Game - Wolfenstein: Enemy Territory (Windows) , Filesize - 258M
(magics-territory.com)

Wolf E T
exe software file
Index of /pub/games/idgames/idstuff/…
(gamers.org)

2.55 forever !

oh but two of them are 2.60b custom… :slight_smile:

(morsik) #14

So what? In your opinion we can’t change anything because Google says that? ;>
And oh. You didn’t said what search query you used. And you must remember that theese are your results. Mine are different and new players will have different results too.

Of course, it’ll be hard with that, but we will try.

(cheesy) #15

Oh no, you can change what ever you want. I am not saying that. My only point is, that trying to force 2.60b is a failed stratagy over the years. There is just too much going against it.

My other point is, it is always better to maintain backwards compatibility. If not, the desired results may backfire, and possibly as a result of another project.

Its friendly, honest advise. Nothing more.

(morsik) #16

We have a lot backward compabitily now with 2.60b and there is really no reason to stuck with 2.55.
We have many security fixed, guid support (we’re working about master auth-server with guids etc). Generally that security fixes are the best reason to update ET. For both client and server.

Backward compability is good until it is secure. Using old client/server is not secure at all.
Oh BTW, If you still use ET 2.55, probably you still use Windows 98 and MS Office 2000? :stuck_out_tongue_winking_eye:

(cheesy) #17

Lol Morsik…you funny guy. No im using Windows 7 64bit and Office 2010, and I help manage IT for a large 500+ user environment.
That being said, I love “change”…but only when there is a plan for success.

Sorry if my honesty pisses you off.

Good luck to ETL dev team :slight_smile:

(cheesy) #18

hmmm…well gameservers did not add the file the first time, but now they did. here is the results on that file Radegast gave me…

./eteng.x86: /lib/libc.so.6: version GLIBC_2.7' not found (required by ./eteng.x86) mlds.sh: Server Exited mlds.sh: To exit loop hit CTRL-C mlds.sh: Sleeping for 15 seconds mlds.sh: Loop Restarting now mlds.sh: To exit loop hit CTRL-C mlds.sh: Starting Server usage: kill [ -s signal | -p ] [ -a ] pid ... kill -l [ signal ] ./eteng.x86: /lib/libc.so.6: versionGLIBC_2.7’ not found (required by ./eteng.x86)
mlds.sh: Server Exited
mlds.sh: To exit loop hit CTRL-C

Its ok, nevermind, I will try to get this thing compiled, and/or modify to make it compile

This is probably a stupid question, but will ET:Legacy support glibc old enough to run on gameservers.com?

(Radegast) #19

uh, that’s some ancient stuff on that server, but then again I run Gentoo with all the bleeding edge packages installed, so for me even a 2 month old release is quite old. Anyway, I recompiled ETeng for you with GLIBC linked statically into the binary which is generally not a good idea, but hopefully it will work: http://mirror.etlegacy.com/eteng-0.3-lin-static.tar.gz

The better option would be to get the same distribution they are using at Gameservers running under Virtualbox and compile it there (yes, you must use scons). Obviously I am not going to waste my time doing that for you with ETeng, but if you ever decide to migrate to ET:L, I’ll gladly help you out.

(morsik) #20

@cheesy: no problem, you didn’t pissed me off (-;

But back to topic (ETeng)… i read that it’s compatible only with 2.60b ;D
Anybody can confirm that?