All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: jeff millar <wa1hco@adelphia.net>
Cc: git@vger.kernel.org
Subject: Re: Building git on Fedora
Date: Mon, 18 Apr 2005 09:39:17 +1000	[thread overview]
Message-ID: <1113781158.11910.15.camel@localhost.localdomain> (raw)
In-Reply-To: <4262F07D.4050007@adelphia.net>

On Sun, 2005-04-17 at 19:25 -0400, jeff millar wrote:
>     ln -sf /lib/modules/`uname -r`/build/include/linux /usr/local/include/linux
> 
> This fix creates a symlink, on each boot up, in the local include 
> directory that points to the kernel header files. If there's a better 
> way to do this, I'm all ears.

What's wrong with the contents of the glibc-kernheaders package? Can you
file specific bugs if you're having problems?

In the long run, the answer is to convince Linus that we _really_ need
the kernel to have a set of header files defining the ABI which are fit
for public consumption, rather than having a horrid mix of private and
exportable bits throughout the contents of the include/ directory. 

In the meantime, some poor mug has to clean the crap up and try to make
something suitable to live in /usr/include/linux -- and unfortunately at
the moment for Fedora that someone is me :)

Unless git is doing something with kernel-private headers that it
shouldn't, this probably wants to be discussed elsewhere -- most likely
in Bugzilla.

-- 
dwmw2


      parent reply	other threads:[~2005-04-17 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17 23:25 Building git on Fedora jeff millar
2005-04-17 23:35 ` Chris Wedgwood
2005-04-17 23:39 ` David Woodhouse [this message]

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=1113781158.11910.15.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=git@vger.kernel.org \
    --cc=wa1hco@adelphia.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.