Building wine on Slackware64
Hello,
As you all probably know, the initial version of Slackware64 didn't support the gcc multilib option and thus compiling of 32-bit based applications was impossible out of the box. I thought that I will end up with the chroot solution, but then I've spotted the Slackware64 changelog update (the 25th of May), which could save me from the chroot. But again compiling wine with updated packages failed and there's still the '--disable-multilib' option specified when asking compiler: Code:
gcc -m32 -v Best Regards, A. |
Re: Building wine on Slackware64
You may need a few extra items. Run over to http://www.slamd64.com/download and in particular check out the slamd64/slackware64-current directory. There are a number of packages for the a, d, l, n, x series. From the readme:
Quote:
|
best news ever (Enemy Territory on 64 bit desktop)!
tnx Fred, youdaman! :D an' tnx also to beowulf have let us know :) finally I can install slack64 at home. |
Just tried a compile after adding the compatibility libraries on Fred's site. I got the following error in the config.log created in the slackbuild build directory.
Quote:
I would appreciate it if someone could suggest a way to overcome this. samac |
Quote:
Quote:
|
Wow great to see those packages from Fred. Will try.
|
pwc101
I have upgraded to these packages and the error message you see is with those packages and the entirety of Fred's work. samac |
Quote:
|
You still have to specify x86_64 (not i486) as the $ARCH, even though you are building 32bit binaries by adding "-m32" to gcc.
Eric |
Quote:
I managed to get it to build by not using the slackbuild with Code:
PKG_CONFIG_LIBDIR=/usr/lib/pkgconfig ./configure --prefix=/usr samac |
Quote:
The new gcc and binutils used in conjunction with the compatibility libraries on Slamd's site, work with the wine.Slackbuild when x86_64 is used as the $ARCH. No other modification is required to the slackbuild. Thanks Eric. samac |
Building 64-bit, and still getting errors...
Quote:
configure: error: C compiler cannot create executables IT SEEMS I FINALLY DID GET RID OF IT. Read below: All of these are set as well: --build="x86_64-slackware-linux" --host="x86_64-slackware-linux" --target="x86_64-slackware-linux" CC="gcc -m64" CFLAGS="-march=x86_64 -fPIC" I just found out that "-march=x86_64 -fPIC" is incorrect. It needs to be set here as x86-64 Once I changed that, I was able to finally run configure without further errors. I just want anyone who reads this to see that multilib is still disabled: Target: x86_64-slackware-linux Configured with: ../gcc-4.3.3/configure --prefix=/usr --libdir=/usr/lib64 --enable-shared --enable-bootstrap --enable-languages=ada,c,c++,fortran,java,objc --enable-threads=posix --enable-checking=release --with-system-zlib --disable-libunwind-exceptions --enable-__cxa_atexit --enable-libssp --with-gnu-ld --verbose --disable-multilib --target=x86_64-slackware-linux --build=x86_64-slackware-linux --host=x86_64-slackware-linux And that's with the latest version of gcc (reinstalled just to make sure). /pub/packages/slapt-get/./slackware64/d/gcc-4.3.3-x86_64-4.txz Even with finally getting configure to run (after all of these failed attempts), it is still obvious here that the build won't be multilib. CORRECTION REQUIRED: --enable-multilib has to set in configure for every build. Shingoshi |
That --disable-multilib has nothing to do with the fact that gcc would not "support" a multilib environment. It only means that the gcc build will not produce the 32bit compilers, only the 64bit compilers. There is a difference!
If you look at the gcc.SlackBuild which Fred Emmott published as part of his 32bit compatibility set for Slackware64 at ftp://anorien.warwick.ac.uk/slamd64/.../gcc-compat32/ you will see that he uses "--enable-multilib" which will result in the 32bit compilers being built. The extra binaries that get produced are the only effect from adding "--enable-multilib". It was stated nowhere that slackware64 would be able to compile 32bit software out of the box. You will need to install additional packages. Eric |
Quote:
Regards, -Drew |
but Fred has published it already with sources and slackbuilds on his site, the link of a mirror is over here :)
or you mean you would like to see it moved on slackbuilds.org? |
I need to be certain here...
Quote:
Thanks for the explanation. Since the Slackware64 gcc was created with --disable-multilib, does that mean any of the following is true: We cannot create... 1.) A new 64-bit compiler with multilib? .........Can we (re)build our own 64-bit compilers to build 32-bit compilers? 2.) The additional packages that are required for 32-bit builds? 3.) Applications for 64-bit which are multilib? Shingoshi |
You can build all of those with just the tools available in Slackware64. Or, if that is too much work, you install the packages which Fred Emmott already compiled and for which I posted the URL several times already... he did not use anything else than a bare slackware64.
Eric |
Alien Bob,
Thanks again. I just needed the first part of your answer. I already knew where the Slamd64 tools were. I just wanted to make that we can build them ourselves from scratch. Thanks, Shingoshi |
Quote:
This, of course, is not meant to take anything away from the great work that Fred has done. Regards, -Drew |
Will Slackware64's gcc (and any other relevant packages) ever be built with --enable-multilib, so that users won't have to (re)build their own gcc (and other packages as well) in order to build 32-bit compilers/packages?
Shingoshi |
sorry Shingoshi but Bob told you already, you don't have to build anything "in order to build 32-bit compilers/packages" :)
Quote:
|
It was simply a matter of independence...
Quote:
To be certain, this is a new situation: Quote:
Shingoshi Edit: As I sometimes do, I made a mistake and omitted two words. They are shown in quotation marks above. I knew the current packages were compiled on Slackware64. That has been clearly repeated. What I intended to know was whether that situation is (ongoing) to continue into the future. |
Quote:
Eric |
All times are GMT -5. The time now is 05:47 AM. |