From: "D. Bahi" <dbahi@enterasys.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] 2.4 series include path confusion
Date: Tue, 21 Dec 2004 20:54:07 -0500 [thread overview]
Message-ID: <41C8D3BF.6070609@enterasys.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
so, trying to build 3rd party tools against the UML kernel headers and run into
things like "can't find sysdep/ptrace.h"
poking around a bit - i wonder why there are headers under the arch/um/include
directory when we have a perfectly good seperate include/asm-um area to play in?
things that want to build against a set of kernel headers shouldn't know about the
arch, right? they should be able to follow UML include paths that are setup during
the build stage that does the soft linking of asm and such.
unimportant compared to the scope of 2.6 work i understand, but i thought i'd
bring it up and see if you think i'm way off my rocker or if i have a point.
thank you all for keeping at it.
--
db
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next reply other threads:[~2004-12-22 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 1:54 D. Bahi [this message]
2004-12-29 17:49 ` [uml-devel] 2.4 series include path confusion Blaisorblade
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=41C8D3BF.6070609@enterasys.com \
--to=dbahi@enterasys.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.