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:

So is it possible to compile wine with the latest slackware64 update?

Best Regards,
A.

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:

Enjoy.

best news ever (Enemy Territory on 64 bit desktop)!
tnx Fred, youdaman!

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.
As you can see from the bold entries the slackbuild has been overruled by gcc. I specified --libdir=/usr/lib in the slackbuild, and i486 as the architecture, it also shows that it is not allowing multi-lib.

I would appreciate it if someone could suggest a way to overcome this.

samac

Hasn't this been fixed in slackware64-current?Emphasis mine.

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

Ah, fair enough then. Sorry, can't help further.

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

OK Eric I will try that as my next experiment.

I managed to get it to build by not using the slackbuild with although this gave me quite a few errors on first startup.

samac

WORKED

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

No matter what I do, I can't get rid of this:
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

...and my hope is that the folks who are figuring out how to do that will graciously make their work available at Slackbuilds.org.

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?