TIP: Click on subject to list as thread! ANSI
echo: fidosoft.husky
to: Maurice Kinal
from: Benny Pedersen
date: 2006-06-28 01:45:22
subject: Hpt and new 64bit compile

Hello Maurice!

25 Jun 06 20:05, Maurice Kinal wrote to Benny Pedersen:

 MK>>> I used 32-bit libs to compile husky stuff.
 BP>> why ?
 MK> Because most of the fido stuff is 16-bit.

keep away from incompatibel software :-)

 MK> Unless you plan to rewrite all the code to compensate for 64-bit 
 MK> addressing etc. then you'll have to stick to the 32-bit libs since the 
 MK> conversions are already there to 32-bit.

good

 MK> For example an int in DOS is 16-bit which is a short in 32-bit whereas a 
 MK> short in 64-bit is 32-bit not 16-bit.

yes a real mess :-)

 BP>> Tobias Ernst says all husky is 64bit clean, but this may have changed 
 BP>> ?
 MK> Really?  I'll have to check.

i still love what Tobias maked or makes if he still do :-)

 MK>>> Also I didn't put any of the husky libs on the system and instead 
 MK>>> have them running and linked in it's own enviroment.
 BP>> show me :-)
 MK> Sure.  Bring some beer when you come.  ;-)

i did not know you where drinking when you code ? :)

 MK> I'll happily write up a 'howto' as to how I did it if you'd like and 
 MK> nobody has an issue with it in this echo.

it would be fine here if its husky related, what i would like is to have
more fidonet software in gentoo portage, since there is none, it would be
good :-)

 BP>> on gentoo all 64bit gcc is multilib unless USE="-multilib"
 MK> Yes but it doesn't matter if both 32-bit and 64-bit libs aren't 
 MK> available on the build system.

show me a linux that runs on 16bit even on 8bit :-)

 BP>> prove this, since i should see this problem as mail hoster when 
 BP>> amavisd unpacks zipped mail attachments, i still have to see problems 
 BP>> in that content
 MK> Try compiling any DOS related source and see what happens.

i just don't have any dos sources so this may be the reason it not a
problem for me :-)

 MK> A good start would be to port mtools or syslinux to pure 64-bit without 
 MK> altering the source.  I'll bet it can't be done.

emerge -av mtools
done :-)

you realy hate me know ?, gentoo have the world of most sources, why not use it ?

 MK>>> I also built a 32-bit unzip in the Fido enviroment just to keep the 
 MK>>> DOS-think people happy but kept the outbound pkts as raw ftn format 
 MK>>> just to play it safe.
 BP>> always good :-)
 MK> For sure. That turned out to be the wisest idea.

i just don't understand why a 32bit unpacker does better then a 64bit dito

 MK>>> Bottomline is that 16-bit apps are a real bugger to port to a pure 
 MK>>> 64-bit system.  Much easier to do to 32-bit then to 64-bit.
 BP>> thats why DOSBOX is good :-)
 MK> Nah!  Don't need no stinkin' DOSBOX!!!

but do we need 16bit anymore ?

 MK>>> Life is good,
 BP>> no 64bit is life :-)
 MK> Actually I am having fun with it.  Managed to port multimedia apps to 
 MK> 64-bit at the expense of breaking all the win32 codecs.  BONUS!!!  
 MK> :-)

hehe athlon64 / opteron makes the fun run both without any problems

 MK> My pci soundcard works.

sounds good ? :-)))


 Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/2.4.20-43_41.rh8.0.at (i686))
* Origin: There is no place like 127.0.0.1 if its not for (2:237/53)
SEEN-BY: 633/267 270
@PATH: 237/53 261/38 123/500 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.