From: Sam Ravnborg <sam@ravnborg.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Arador <diegocg@teleline.es>, linux-kernel@vger.kernel.org
Subject: Re: buggy include path?
Date: Wed, 19 Feb 2003 16:32:31 +0100 [thread overview]
Message-ID: <20030219153231.GA970@mars.ravnborg.org> (raw)
In-Reply-To: <20030218153919.16d41430.rddunlap@osdl.org>
On Tue, Feb 18, 2003 at 03:39:19PM -0800, Randy.Dunlap wrote:
> Can the -Idirname be made more complete, e.g. by using
> $TOPDIR or $MODLIB ... me wonders.
> Or would that just be duplicating the default behavior?
> Anyone?
That would make moving a kernel tree requiring a recompile due to usage
of absolute paths.
Sam
next prev parent reply other threads:[~2003-02-19 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 23:29 Arador
2003-02-18 23:39 ` Randy.Dunlap
2003-02-19 15:32 ` Sam Ravnborg [this message]
2003-02-18 23:47 ` Arador
2003-02-19 15:33 ` Sam Ravnborg
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=20030219153231.GA970@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=diegocg@teleline.es \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®