public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Dosemu 1.3.2 and linux 2.6.7 headers
Date: Wed, 13 Jul 2005 19:19:32 +0400	[thread overview]
Message-ID: <42D53104.3090703@aknet.ru> (raw)

Hello.

Bart Oldeman wrote:
>> Maybe add the proper headers to the
>> dosemu source tree as we did before?
> The question is which headers?
I think some of them can be located if
you symlink the kernel headers and try
to compile. Of course it is not guaranteed
to be all of them, but better than nothing.
The thing is that the source tree of dosemu
already contains a lot of the "problematic"
headers (you added most of them anyway:).
We can either keep adding to it, or remove
it entirely. Right now it is there, yet it
doesn't contain the sufficient amount of
headers to get the thing compiled on 2.6,
so basically it is useless. I still have
the hopes it can be entirely removed but...
not today:) (i.e. we really have to check
about the slackware, I guess)


             reply	other threads:[~2005-07-13 15:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 15:19 Stas Sergeev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-14  4:03 Dosemu 1.3.2 and linux 2.6.7 headers Stas Sergeev
2005-07-14 10:01 ` Julius Schwartzenberg
2005-07-13 16:03 Stas Sergeev
2005-07-13 22:26 ` Julius Schwartzenberg
2005-07-13  3:47 Stas Sergeev
2005-07-13  4:36 ` Hufnus
2005-07-13  7:53 ` Bart Oldeman
2005-07-12 20:07 Hufnus
2005-07-12 20:21 ` 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

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=42D53104.3090703@aknet.ru \
    --to=stsp@aknet.ru \
    --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