From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: PATCH: drop symbolink link to kernel headers
Date: Thu, 22 Jan 2004 17:31:11 +0000 [thread overview]
Message-ID: <20040122173111.GI14310@kroah.com> (raw)
In-Reply-To: <5701.1074622084@www46.gmx.net>
On Thu, Jan 22, 2004 at 06:24:02PM +0100, Svetoslav Slavtchev wrote:
> > On Tue, Jan 20, 2004 at 07:08:04PM +0100, Svetoslav Slavtchev wrote:
> > > Hi,
> > > the attached patch removes the need from a symbolik link to kernel
> > headers
> > > when compiling against klibc.
> > > if KERNEL_DIR is not specified it looks for kernel headers
> > > in /usr/src/linux( of course you could change it to /lib/modules/`uname
> > > -r`/build )
> >
> > It's a nice idea, but is it really needed?
>
> well, i could always patch it :-)
> and may be other packagers too,
> but i think it's a good idea
Ok, how about defaulting to /lib/modules/`uname -r`/build instead.
Also, you don't have to check if KERNEL_DIR is set before trying to set
it yourself. Make will handle this properly.
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-22 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 18:08 PATCH: drop symbolink link to kernel headers Svetoslav Slavtchev
2004-01-21 23:53 ` Greg KH
2004-01-22 0:40 `
2004-01-22 1:51 `
2004-01-22 3:42 ` Dave Dodge
2004-01-22 17:06 ` linas
2004-01-22 17:24 ` Svetoslav Slavtchev
2004-01-22 17:28 ` Greg KH
2004-01-22 17:31 ` Greg KH [this message]
2004-02-03 0:52 ` Greg KH
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=20040122173111.GI14310@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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 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.