-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


This is mainly a question for Fred, but I''ll email it to him
separately. But for anyone who is using the x86-64 port of Slackware..

Until Fred releases the next ISO image which will be based off
of Slackware 10.1, would it be safe to say that you could use the 10.0
ISO image he created to get the distro installed, then use swaret to
grab the sources, compiled those, and be up to date as the normal 10.0
or 10.1 tree? I don't see Pat supporting x86-64 anytime soon
(justfiably so), but I also don't think Fred will have the space or
bandwidth to keep the port current outside of ISO images.

so would grabbing the sources after a full install of the
x86-64 bit distro and compiling them give the same effect as using
swaret to grab the packages in the 32-bit world?

BL.
- --
Brad Littlejohn | Email: tyketto@sbcglobal.net
Unix Systems Administrator, | tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! | http://www.sbcglobal.net/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCHSMgyBkZmuMZ8L8RApVOAJ9FIOj5GobP75t3Z+xsvt T2ZAkGTQCg2WAS
KFF7U2KOQYfLyvc8LauafWI=
=+QPh
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, A Guy Called Tyketto dared to utter,
> Until Fred releases the next ISO image which will be based off
> of Slackware 10.1, would it be safe to say that you could use the 10.0
> ISO image he created to get the distro installed, then use swaret to
> grab the sources, compiled those, and be up to date as the normal 10.0
> or 10.1 tree?

It's a good bit more involved then just recompiling source. If it were
that easy I'm sure Pat would have already done so. Fact of the matter
is, two sets of libraries have to be maintained (one for 64-bit
binaries and one for 32-bit bins), some apps just don't compile neatly
for non-x86 archs, etc. Running the default SlackBuilds should work,
but it's only going to work in-so-far as it'll create valid 32-bit
binaries, not optimized 64-bit bins.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCHUoXvgVcFKpJf4gRAuS7AKC1BvR08Rg4OwY+58oeuq JGfERkiwCg35Hg
u8EoT5MRb8rMdShTTo77FBM=
=wqaF
-----END PGP SIGNATURE-----

+Alan Hicks+ wrote:
[snip]
> It's a good bit more involved then just recompiling source. If it were
> that easy I'm sure Pat would have already done so. Fact of the matter
> is, two sets of libraries have to be maintained (one for 64-bit
> binaries and one for 32-bit bins), some apps just don't compile neatly
> for non-x86 archs, etc. Running the default SlackBuilds should work,
> but it's only going to work in-so-far as it'll create valid 32-bit
> binaries, not optimized 64-bit bins.

Not entirely true Running the default SlackBuilds will either work, or
just crash, depending on the program

Building 32-bit binaries requires CFLAGS=-m32
--
Fred Emmott
(http://www.fredemmott.co.uk)

Fred Emmott wrote:
[snip]

Mini-how-to-use-slackbuilds-on-slamd64:

1) Change arch to x86_64
2) Remove any -march and -mcpu flags from CFLAGS
3) Add -fPIC to CFLAGS
4) Pray and run it
5) Patch the program
6) Goto 4

Regards,

--
Fred Emmott
(http://www.fredemmott.co.uk)

+Alan Hicks+ wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, A Guy Called Tyketto dared to utter,
>> Until Fred releases the next ISO image which will be based off
>> of Slackware 10.1, would it be safe to say that you could use the 10.0
>> ISO image he created to get the distro installed, then use swaret to
>> grab the sources, compiled those, and be up to date as the normal 10.0
>> or 10.1 tree?
>
> It's a good bit more involved then just recompiling source. If it were
> that easy I'm sure Pat would have already done so. Fact of the matter
> is, two sets of libraries have to be maintained (one for 64-bit
> binaries and one for 32-bit bins), some apps just don't compile neatly
> for non-x86 archs, etc. Running the default SlackBuilds should work,
> but it's only going to work in-so-far as it'll create valid 32-bit
> binaries, not optimized 64-bit bins.

I also recompiled Slackware for x86_64. The hardest part is getting
initial core of packages set-up (glibc, gcc, binutils, bash, etc) and
booting into the x86_64 mode. Then, it gets easier.

Newer Slackware source packages have <package_name>.SlackBuild scripts.
These are very easy to use. They check your ARCH environment variable
to see what architecture you want to compile the package for. The only
addition that I would make would be '--with-libs=/usr/lib64' for each
configure script. This places libraries into /usr/lib64. In my /usr/lib,
I placed 32bit libc library that I compiled, and then copied 32 bit
libraries from Slackware CD. That gives me a bi-arch Slackware
distribution. Please note that /usr/lib64 is not my idea. Binutils, and
other packages create that directory and populate it. Even X.org creates
and populates /usr/X11R6/lib64 automatically.

Also, use GCC 3.4.x. You won't get all kind of weird compile errors and
crashes. The only problem is that you will have to add some missing
semicolons in case statements in some of the source files.


>
> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFCHUoXvgVcFKpJf4gRAuS7AKC1BvR08Rg4OwY+58oeuq JGfERkiwCg35Hg
> u8EoT5MRb8rMdShTTo77FBM=
> =wqaF
> -----END PGP SIGNATURE-----