Release very soon

[thelusiv]

OK, I have double-compiling set up properly now, at least more or less and it works to relieve Joe's GCC_4.0.0 not found problem. I still haven't resolved the other problem but have asked the autopackage dev mailing list about it. Also I've run into some problems preventing me from building a 64 bit package which I've asked about. You can test the latest package which is here: http://clemsonlinux.org/~thelusiv/VDrift...al.package

I checked in the most recent updates to the build setup in SVN r1629.

[abs1nth]

Once I get some feedback on the package I may go ahead and tag the release, upload the packages, and post the release story.

so that means i can already start building the mac packages?

[joevenzon]

affirmative... no other code changes expected

[abs1nth]

ok made packages and did some basic testing on ppc&intel macs. should i upload & announce the release or wait until the source release has been made?

[thelusiv]

You can go ahead and write your story as a draft, and once I post the Linux release story I'll un-draft yours too, so they go out at the same time. Make sure to preview your story

I haven't set up the new release on SF.net yet though so hold off on uploading. As far as I can see the release version will be 2007-03-22 so you can go ahead and make the package under that name.

[jpenguin]

Just to give everyone an update, the release is probably going to be Monday or Tuesday.

It's already Thursday, I think the SVN is stable enough. Just bundle it, and release

[gebeleizis]

(chorus) Release, Release, Release
Please, pretty please...

[thelusiv]

Alright folks, I know it's been a long time, but I want to get it right. Joe's still having errors running the game after a successful installation even with the 3-22 package above:

Code:

./games/vdrift/bin/vdrift: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `CXXABI_1.3.1' not found (required by ./games/vdrift/bin/vdrift)

I'm working with the folks on the autopackage-dev mailing list to figure this one out; they've helped a lot in figuring out the other issues. Until this latest package there were issues with gcc 3.x, but those are cleared up now, and only CXXABI problems remain. So close...

And while I'm trying to figure out these issues, I've also got the autopackage tools set up on my new 64-bit machine. After a little struggling I have set up an x86-64 package that may work natively for folks using that platform. I've just uploaded a test package for that too, if you have an x86-64 machine you can test it out. http://clemsonlinux.org/~thelusiv/VDrift...64.package

[abs1nth]

>As far as I can see the release version will be 2007-03-22 so you can go ahead and make the package under that name.

even if the release slips, could you still retain that name? i've already made packages and FTP'ed them to sourceforge ;-)

[thelusiv]

I suppose that's possible, I seriously doubt there will be any changes besides build setup happening before release now, I know of no other serious open bugs.

[thelusiv]

Alright this really may be the final test package! Mike Hearn on the autopackage dev list has helped immensely in figuring out the problems, which turn out to be really kind of obscure...you can read about it here: http://lists.freestandards.org/pipermail...00213.html

It turns out the solution is to compile with gcc 3.4 intead of 4.x, and I've updated the package to reflect these changes. Try it again, it's at the same location: http://clemsonlinux.org/~thelusiv/VDrift...al.package

[thelusiv]

Last night Joe tried out that package and it turns out that it was not actually statically linking *anything* as I thought it had been all along. I think the static linking may be fixed now, it turned out I had to take the "lib" out of the name of the libraries in the list of libs that apbuild should statically link. I've removed the attempt to statically link libstdc++ also as suggested by autopackage devs. I'm still working out an issue where it now seems to be ignoring my CXX2 environment variable, and using the same compiler (g++-3.4) on both passes. Once I fix that I'll get up another testing package.

However...there's another issue. The default VDrift.config has not been updated with new options that have been added since the last version. Also the default car (which is the one selected in the Practice Game and Single Race menus on game start) is set to TL, which is no longer distributed with the minimal data set. It should instead be TL2; but the way it is now, VDrift crashes after trying to load the car that's not there. See the glibc thread for demonstration of this problem. This is a major problem and so I'm afraid we're going to have to change the release date and redo any packages already made (sorry abs1nth!)

3-23 is now the target release date. I'm still working on this and I'm not giving up until it works...I'll check in a new VDrift.config very soon.

[thelusiv]

Another testing package, static linking seems to be done right now, but ldd/readelf doesn't seem to agree. Anyway it's worth trying... http://clemsonlinux.org/~thelusiv/VDrift...al.package

I also checked in changes to some menu files (removed Mouse Options menus), changed the default VDrift.config, and edited options.config to remove some unnecessary entries.

[abs1nth]

i'm ftp'ing the new packages ATM.

had included TL instead of TL2 in the minimal set previously and fixed that too now - good that you pointed out that this changed ;-)

[joevenzon]

thelusiv, your package works for me! you statically linked SDL_gfx, although the other SDL libraries (SDL, SDL_net, SDL_image) plus the GL libraries (GL, GLU) are dynamically linked, but that's probably okay, right?