Hey Benny!

Apr 23 02:38 07, Benny Pedersen wrote to Maurice Kinal:

 MK>> make CC="gcc -m64" CFLAGS="-Os -march=amd64 -fPIC"

 BP> -m64 is needed ?

Not usually but it doesn't hurt either.

 BP> amd64 gentoo defaults to -m64

So does my clean 64-bit gcc.

 BP> -Os why optimize on size ?

I like small.  :-)

 BP> gcc have problems on some size optimizing on 64bit 

I have yet to see that as a problem.  Everything runs fast on the dual core
pentium d em64t with -Os and march=nocona.

 BP> i am unsure about -fPIC but if it works :-)

I've had to do that with a few shared libs and that fixed those.

 BP> one should realy start makeing the gentoo ebuilds for husky :)

I have a tar gzipped archive.  I don't do ebuilds.  Should work on any
em64t.  I used to have an amd64 optimized one but I gave up on amd after
getting nothing but grief about firmware crap.  I cpu's are okay but can't
say I am too fond of am2 motherboards and their lack of choice about
chipsets.  Too many poorly manufactured motherboards in amd64 land.  I gave
up in disgust.

 BP> and default have husky 64bit lib in the build not just lib, a amd64 
 BP> is fully 32bit and 64bit capeble hardware so both can work at the 
 BP> same time if one needs it :-)

I don't bother.  Either one or the other.  I have a special gcc compiler
for pure 32-bit builds on the 64-bit machine.  Worked out great!  I
optimize for 486 using that and that way can still run my older 486 and it
is right up to date and in sync.  Best idea I ever had.  :-)

 BP> windows vista 64bit is a good example on what happens when rules is 
 BP> not followed ...

Have yet to see it.  I never bothered with MS anything ever since DOS on a
386.  Even back then I ran IBM's DOS with a c and fortran compiler just to
keep in sync with unix world as best as I could at the time.  Later on
Linux came along and solved that problem nicely.  Never saw anything decent
come out of MS so I never needed to bother with any of that.  Have you?

Life is good,
Maurice

--- Msged/LNX 6.2.0