Skip to contentSkip to conversation

Compilation options used in the binary distribution

DISCUSSION Javier Tarifa 2 participants 3 messages Jan 20, 2009 – Jan 21, 2009

lore
Share & tools
lore
#0 lore raw

I'd like to know exactly how was compiled the binary distribution that you get when you download dosemu-1.4.0-bin.tgz.
I've done a little change to the terminal code and when I a run a program with my own compiled version, the program dies saying something about too many users when I have more than one dosemu running it. But when I use the binary distribution this doesn't happen, I can have multiple dosemus using it without problems. Can someone help me?

#1 lore raw
Quoted 8 lines · Javier Tarifa

I'd like to know exactly how was compiled the binary distribution that you get when you download dosemu-1.4.0-bin.tgz.
I've done a little change to the terminal code and when I a run a program with my own compiled version, the program dies saying something about too many users when I have more than one dosemu running it. But when I use the binary distribution this doesn't happen, I can have multiple dosemus using it without problems.
Can someone help me?

Signature · 17 lines
You want run multiple dosemus under one user account? Then maybe will
be usefull start individual instances with unique "-o logfile" log file
specification (instead of default "~/.dosemu/boot.log"). Or You can
specify log/debug filespec in individual .dosemurc files with option
"$_debugout = "filespec".

Although I use and have dosemu 1.4 compiled for several Fedora distributions,
and it works fine when simultaneously run couple of them from one user,
even without specifying different boot.log file - they all use implicit
one (lsof says)(it's smut way, but dosemus curiously works)

You can too look for my build options in RPM .spec files at:

http://hanzlici.cz/packages/fedora/dosemu/

Regards,
Franta Hanzlik
#2 lore raw

Ok, I finally got it. For some strange reason, changing target_bits from auto to 32 in the file compiletime-settings solved the problem (this was on a 64 bits fedora)