hi all,
i want to compile glibc 2.3.2 ( the last release ) for my athlon CPU , as it
is built for i486 by default .

Is still have a default slackware 9.1 .

My first try would be to recompile the "a" packacges ( Linux base ).
then follow the alphabet ... , with changing the CFLAGS into each slackbuild
file by -march=athlon-tbird .

Is that the best thing ?

In the "d" directory ,
for the binutils build ,
If look into the Slackbuild file ,i see some options like :
[...]
--enable-targets=i486-slackware-linux,i486-slackware-linux-gnulibc1,i486-slackware-linux-gnuaout
[...]
If i already compiled my system for athlon , will those "i486-xxx" options
have to be changed ? what by ?

Thanks for your help .
--
http://mrakotom.free.fr

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

On 2003-12-05, Rakotomandimby <mrakotom@free.fr> rambled:

>
> Is that the best thing ?

Seems a reasonable plan.

Might want to have a look at www.linuxfromscratch.org
for some tips on compiling stuff.

>
> In the "d" directory ,
> for the binutils build ,
> If look into the Slackbuild file ,i see some options like :
> [...]
> --enable-targets=i486-slackware-linux,i486-slackware-linux-gnulibc1,i486-slackware-linux-gnuaout
> [...]
> If i already compiled my system for athlon , will those "i486-xxx" options
> have to be changed ? what by ?
>

I think it would be best to change those i486s to i686s

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

iD8DBQE/0HMVoOMCLVDeF1sRAkb3AJ9QiG1G64bq0UR/wIMgQPzeEI+bYgCgz7pz
IVU4EvGlrNkVLRzevEbAxxU=
=MSY4
-----END PGP SIGNATURE-----

Billy Watt <newsspam@cjwatt.plus.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

pgp trash troll delete

> On 2003-12-05, Rakotomandimby <mrakotom@free.fr> rambled:

> >
> > Is that the best thing ?

> Seems a reasonable plan.

> Might want to have a look at www.linuxfromscratch.org
> for some tips on compiling stuff.

Do they have tips on the correct and responsible use of pgp? Did
you know, for example, that nothing in this posting warrants the
use of pgp?

But of course you did. You're a pgp trash troll.

We ask that you refrain from using pgp in postings that do not
warrant it.

cordially, as always,

rm

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

On Fri, 05 Dec 2003 12:41:12 +0100, Rakotomandimby <mrakotom@free.fr> wrote:
> i want to compile glibc 2.3.2 ( the last release ) for my athlon CPU , as it
> is built for i486 by default .

It's actually optimized with -mcpu=i686 -march=i486, if my memory serves
me correctly. I've been thinking I need to fsck the damned thing here
lately. It seems to be losing data.

> Is still have a default slackware 9.1 .

Ok.

> My first try would be to recompile the "a" packacges ( Linux base ).
> then follow the alphabet ... , with changing the CFLAGS into each slackbuild
> file by -march=athlon-tbird .

Well, now you're getting ahead of yourself. You said you wanted to
recompile glibc optimized for your CPU, you didn't mention all that
other stuff. IMO, having gone down the optimization road more times
than I care to count, optimizing the little itty bitty packages on your
system is wasted time. Hit glibc, hit gcc, hit X, and the KDE shit.
But ls? dd? cat? slocate? Naw, don't bother. They aren't worth it.

> Is that the best thing ?

I'd just be careful - remember that optimizations can and do cut in to
stability, and can sometimes un-optimize things for speed. Athlon-TBird
is a pretty safe optimization target, though. It seems the GCC devs
like AMD. I think AMD likes them, though, too... which helps. :-)

> In the "d" directory ,
> for the binutils build ,
> If look into the Slackbuild file ,i see some options like :
> [...]
> --enable-targets=i486-slackware-linux,i486-slackware-linux-gnulibc1,i486-slackware-linux-gnuaout
> [...]
> If i already compiled my system for athlon , will those "i486-xxx" options
> have to be changed ? what by ?

Boy, I dunno about that target stuff, I've never played with it. I hate
to dodge a question like this - but - are you sure you really want to
even recompile binutils? I mean, as I stated above, it's not like we're
dealing with the most CPU intensive things out there, yanno.

My two cents, anyway....

--
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/0MwChm6KEoOOAe0RAiQeAKDJ2BkDuS3MktVqWEzttdJ6uT0W/QCeJWxL
a/l6tnQMMr9rFfkMQKgOFYU=
=uIF8
-----END PGP SIGNATURE-----

AthlonRob wrote:


> It's actually optimized with -mcpu=i686 -march=i486, if my memory serves
> me correctly.

Yep sorry . the binutils were 486-ed, not glibc .

> But ls? dd? cat? slocate? Naw, don't bother. They aren't worth it.

OK . If yu tell it , i trust you .
thank you for giving you opinion . :-)

> My two cents, anyway....

With Paypal ? ;-)
( just kidning ...)

--
http://mrakotom.free.fr

"AthlonRob" <junkmail@axpr.net> wrote in message
news:9ehqqb.ino.ln@dsl-gervais-88.web-ster.com...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> NotDashEscaped: You need GnuPG to verify this message
>
> On Fri, 05 Dec 2003 12:41:12 +0100, Rakotomandimby <mrakotom@free.fr>
wrote:
> > i want to compile glibc 2.3.2 ( the last release ) for my athlon CPU ,
as it
> > is built for i486 by default .
>
> It's actually optimized with -mcpu=i686 -march=i486, if my memory serves
> me correctly. I've been thinking I need to fsck the damned thing here
> lately. It seems to be losing data.
>
> > Is still have a default slackware 9.1 .
>
> Ok.
>
> > My first try would be to recompile the "a" packacges ( Linux base ).
> > then follow the alphabet ... , with changing the CFLAGS into each
slackbuild
> > file by -march=athlon-tbird .
>
> Well, now you're getting ahead of yourself. You said you wanted to
> recompile glibc optimized for your CPU, you didn't mention all that
> other stuff. IMO, having gone down the optimization road more times
> than I care to count, optimizing the little itty bitty packages on your
> system is wasted time. Hit glibc, hit gcc, hit X, and the KDE shit.
> But ls? dd? cat? slocate? Naw, don't bother. They aren't worth it.
>
> > Is that the best thing ?
>
> I'd just be careful - remember that optimizations can and do cut in to
> stability, and can sometimes un-optimize things for speed. Athlon-TBird
> is a pretty safe optimization target, though. It seems the GCC devs
> like AMD. I think AMD likes them, though, too... which helps. :-)
>
> > In the "d" directory ,
> > for the binutils build ,
> > If look into the Slackbuild file ,i see some options like :
> > [...]
>
> --enable-targets=i486-slackware-linux,i486-slackware-linux-gnulibc1,i486-s
lackware-linux-gnuaout
> > [...]
> > If i already compiled my system for athlon , will those "i486-xxx"
options
> > have to be changed ? what by ?
>
> Boy, I dunno about that target stuff, I've never played with it. I hate
> to dodge a question like this - but - are you sure you really want to
> even recompile binutils? I mean, as I stated above, it's not like we're
> dealing with the most CPU intensive things out there, yanno.
>
> My two cents, anyway....

I optimised a mates box for athlon (indeed, I've optimised my own for 686),
You can safely change the -mcpu and -march options which will compile it for
the specified cpu and architecture, but if you change the target as soon as
you upgrade the package almost nothing will work. If you want to change the
target AFAIK you have to go the linuxfromscratch route

Martin

"Neo" <neo@nospam.come-to-chat.com> wrote in message
news:3fff91ca$0$18032$cc9e4d1f@news.dial.pipex.com ...
>
> "AthlonRob" <junkmail@axpr.net> wrote in message
> news:9ehqqb.ino.ln@dsl-gervais-88.web-ster.com...
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > NotDashEscaped: You need GnuPG to verify this message
> >
> > On Fri, 05 Dec 2003 12:41:12 +0100, Rakotomandimby <mrakotom@free.fr>
> wrote:
> > > i want to compile glibc 2.3.2 ( the last release ) for my athlon CPU ,
> as it
> > > is built for i486 by default .
> >
> > It's actually optimized with -mcpu=i686 -march=i486, if my memory serves
> > me correctly. I've been thinking I need to fsck the damned thing here
> > lately. It seems to be losing data.
> >
> > > Is still have a default slackware 9.1 .
> >
> > Ok.
> >
> > > My first try would be to recompile the "a" packacges ( Linux base ).
> > > then follow the alphabet ... , with changing the CFLAGS into each
> slackbuild
> > > file by -march=athlon-tbird .
> >
> > Well, now you're getting ahead of yourself. You said you wanted to
> > recompile glibc optimized for your CPU, you didn't mention all that
> > other stuff. IMO, having gone down the optimization road more times
> > than I care to count, optimizing the little itty bitty packages on your
> > system is wasted time. Hit glibc, hit gcc, hit X, and the KDE shit.
> > But ls? dd? cat? slocate? Naw, don't bother. They aren't worth it.
> >
> > > Is that the best thing ?
> >
> > I'd just be careful - remember that optimizations can and do cut in to
> > stability, and can sometimes un-optimize things for speed. Athlon-TBird
> > is a pretty safe optimization target, though. It seems the GCC devs
> > like AMD. I think AMD likes them, though, too... which helps. :-)
> >
> > > In the "d" directory ,
> > > for the binutils build ,
> > > If look into the Slackbuild file ,i see some options like :
> > > [...]
> >
>
> --enable-targets=i486-slackware-linux,i486-slackware-linux-gnulibc1,i486-s

> lackware-linux-gnuaout
> > > [...]
> > > If i already compiled my system for athlon , will those "i486-xxx"
> options
> > > have to be changed ? what by ?
> >
> > Boy, I dunno about that target stuff, I've never played with it. I hate
> > to dodge a question like this - but - are you sure you really want to
> > even recompile binutils? I mean, as I stated above, it's not like we're
> > dealing with the most CPU intensive things out there, yanno.
> >
> > My two cents, anyway....
>
> I optimised a mates box for athlon (indeed, I've optimised my own for
686),
> You can safely change the -mcpu and -march options which will compile it
for
> the specified cpu and architecture, but if you change the target as soon
as
> you upgrade the package almost nothing will work*. If you want to change
the
> target AFAIK you have to go the linuxfromscratch route
>
> Martin

*Slight change... I meant to say if you compile glibc (and probably other
core system libraries) and change the target the above will happen