From: Hufnus <tonyb@thekrnl.sysdev.org>
To: linux-msdos@vger.kernel.org
Subject: Dosemu 1.3.2 and linux 2.6.7 headers
Date: Tue, 12 Jul 2005 12:07:21 -0800 [thread overview]
Message-ID: <20050712120721.67306d8a.tonyb@sysdev.org> (raw)
Anybody runing 1.3.2 or trying with Linux 2.6 ????
I can compile 1.3.2 with gcc 3.3.4 and Linux 2.4 headers,
and run it on Linux 2.6.7, but it has some keyboard press
problems. The same dosemu.bin works fine with our apps
in 2.4.31, though!
So I tried to compile with Linux 2.6.7 headers, but the make
gets some obsolete warnings and then fails with many parse errors
in /usr/include/linux/mod_devicetable.h related to symbols like
__u32 etc....
Now, if I relink 'ln -sf linux-2.4.31 linux' it still complains
about using -malign-????? is obsolete to use -falign-????? but
it builds fine.
Thanks
TonyB
--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities
|___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers
next reply other threads:[~2005-07-12 20:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 20:07 Hufnus [this message]
2005-07-12 20:21 ` Dosemu 1.3.2 and linux 2.6.7 headers Maciek Stopa
2005-07-12 20:49 ` Hufnus
2005-07-12 20:58 ` Maciek Stopa
2005-07-12 23:05 ` Hufnus
2005-07-12 23:35 ` Bart Oldeman
2005-07-12 23:43 ` Julius Schwartzenberg
2005-07-13 0:15 ` Hufnus
2005-07-13 1:44 ` Bart Oldeman
2005-07-13 4:20 ` Hufnus
-- strict thread matches above, loose matches on Subject: below --
2005-07-13 3:47 Stas Sergeev
2005-07-13 4:36 ` Hufnus
2005-07-13 7:53 ` Bart Oldeman
2005-07-13 15:19 Stas Sergeev
2005-07-13 16:03 Stas Sergeev
2005-07-13 22:26 ` Julius Schwartzenberg
2005-07-14 4:03 Stas Sergeev
2005-07-14 10:01 ` Julius Schwartzenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050712120721.67306d8a.tonyb@sysdev.org \
--to=tonyb@thekrnl.sysdev.org \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox