I have a dual Opteron w/ AMD-8111 chipset, I need help (a mini-howto) on
how to compile my kernel (2.4.23 on Slack 8.1 and 9.1), and later some
utilities, to support the full 64-bit of the CPUs.

Can I use the standard gcc, or do I have to create a cross-compiler for
the x86_64? If so, anyone know how to do this in Slack?

Trygve Selmer wrote:
> Can I use the standard gcc, or do I have to create a cross-compiler for
> the x86_64? If so, anyone know how to do this in Slack?
>
The kernel compile includes code for the Opteron family of processors,
to make your kernel AMD64 happy.

Setting your CFLAGS environment variable before compiling will pass the
necessary parameters to gcc when it compiles. Example:

--- start script ---
#!/bin/bash

CFLAGS="-m64"
configure
make

--- end the script ---

Setting the CFLAGS to -m64 tells gcc to compile for 64 bits.
You'll need to read the man page for GCC to get into more detail. The
only other options found by me are:
-march=athlon/-march=athlon-4/-march=athlon-xp/-march=athlon-tbird

I'm not sure which is for the x86_64. This should get you started at least.

Jason Dumler

Jason Dumler wrote:
> Trygve Selmer wrote:
>
>> Can I use the standard gcc, or do I have to create a cross-compiler
>> for the x86_64? If so, anyone know how to do this in Slack?
>>
> The kernel compile includes code for the Opteron family of processors,
> to make your kernel AMD64 happy.
>
> Setting your CFLAGS environment variable before compiling will pass the
> necessary parameters to gcc when it compiles.

Thanks Jason, but I'm having problems with gcc-2.95.3. Maybe it's time
to upgrade to gcc-3.2.3.

Trygve

Trygve Selmer wrote:
> Jason Dumler wrote:
>
>> Trygve Selmer wrote:
<snip>
>>
> Thanks Jason, but I'm having problems with gcc-2.95.3. Maybe it's time
> to upgrade to gcc-3.2.3.
>
> Trygve
>

Sorry, no suggestions for 2.95.3. I'm pretty sure you could compile the
kernel with 64 bit stuff, and the kernel functions would be optimized
for the Opteron, since that's in the code, but I don't *think* your
compiler will optimize anything for 64 bits. I could be wrong.

I've been using 3.2.1/3.2.2 for awhile, and so far, so good. Just make
sure if you compile your kernel with gcc version X, you compile any new
modules (say for VMWare), you use the same compiler, even if it's older.
You can get some very Winbloze like behavior if you don't. :-)

Jason Dumler

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Sat, 27 Dec 2003 11:18:26 -0500, Jason Dumler <dumlerjason_bugger_spam@netscape.net> wrote:
> Sorry, no suggestions for 2.95.3. I'm pretty sure you could compile the
> kernel with 64 bit stuff, and the kernel functions would be optimized
> for the Opteron, since that's in the code, but I don't *think* your
> compiler will optimize anything for 64 bits. I could be wrong.

You're definitely not going to be able to compile Opteron stuff with
2.95.3. No way, no how. :-)

Of course, regular x86 will run fine under the Opteron.

--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/7hHVhm6KEoOOAe0RAqlBAKDsitDPtO8KPDhDnKTonSYOBXb46w CggsHi
o6e/B7MIh0Ko4YGj+YuWoXw=
=O+qo
-----END PGP SIGNATURE-----

AthlonRob wrote:
> On Sat, 27 Dec 2003 11:18:26 -0500, Jason Dumler <dumlerjason_bugger_spam@netscape.net> wrote:
>
>>Sorry, no suggestions for 2.95.3. I'm pretty sure you could compile the
>>kernel with 64 bit stuff, and the kernel functions would be optimized
>>for the Opteron, since that's in the code, but I don't *think* your
>>compiler will optimize anything for 64 bits. I could be wrong.
>
> You're definitely not going to be able to compile Opteron stuff with
> 2.95.3. No way, no how. :-)
>
> Of course, regular x86 will run fine under the Opteron.

I know, but it would be nice to use the 64-bit cpu in 64-bit mode :-)

I'm considering installing Suse 9.0 (x86_64 version), then trying to
build slack-packages of the compiler, libc, etc. If sucessful, we may
have the start of a Slackware x86_64 release.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Sun, 28 Dec 2003 10:47:19 +0100, Trygve Selmer <trselmer@start.no> wrote:
> I'm considering installing Suse 9.0 (x86_64 version), then trying to
> build slack-packages of the compiler, libc, etc. If sucessful, we may
> have the start of a Slackware x86_64 release.

Try doing it LFS style from an x86-64 distro and you might end up with
something *very much* like Slackware. That way the library versions
would match up perfectly.

Sounds like a great idea. :-)

--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/7xZ+hm6KEoOOAe0RAs7WAJ4352i/R1YQ7qO669Z6I81JORiCTQCgrYHu
bT+cZmlyq4MxKLzsbQaM5qw=
=mT7Q
-----END PGP SIGNATURE-----