linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev 147 (and above) dependencies
Date: Tue, 17 Nov 2009 09:53:09 +0000	[thread overview]
Message-ID: <200911171053.09453.zzam@gentoo.org> (raw)
In-Reply-To: <2CAE5634D52E194BA393187E0568E1AC040BDA7F@ftrdmel1>

On Dienstag, 17. November 2009, Kay Sievers wrote:
> On Tue, Nov 17, 2009 at 08:46, Matthias Schwarzott <zzam@gentoo.org> wrote:
> > On Dienstag, 17. November 2009, mblanchard.ext@orange-ftgroup.com wrote:
> >> I tried to compile the lastest Udev 147 on a system running linux kernel
> >> 2.6.31 and glibc 2.8. This attempt failed because the SOCK_CLOEXEC
> >> constant is not defined in my glibc header /usr/include/bits/socket.h.
> >> After a small investigation, I found the following: kernel support of
> >> SOCK_CLOEXEC was introduced in the 2.6.27 release. However, the glibc
> >> support was introduced in glibc 2.9. I believe this dependency should be
> >> precised in the Udev README.
> >
> > I think udev-147 even requires kernel 2.6.29 headers, as this is the
> > first release in which bsg.h is exported.
>
> bsg was added in 2.6.23.
>
Yes, and this commit exported it to userspace, so it got installed 
below /usr/include. So 2.6.29 were the first linux-headers to contain bsg.h

commit a229fc61ef0ee3c30fd193beee0eeb87410227f1
Author: Boaz Harrosh <bharrosh@panasas.com>
Date:   Mon Jan 19 10:37:38 2009 +0100
include/linux: Add bsg.h to the Kernel exported headers


Matthias

  parent reply	other threads:[~2009-11-17  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17  7:30 Udev 147 (and above) dependencies mblanchard.ext
2009-11-17  7:46 ` Matthias Schwarzott
2009-11-17  9:34 ` Kay Sievers
2009-11-17  9:53 ` Matthias Schwarzott [this message]
2009-11-17 10:26 ` mblanchard.ext
2009-11-17 10:30 ` mblanchard.ext
2009-11-17 17:11 ` Bryan Kadzban

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=200911171053.09453.zzam@gentoo.org \
    --to=zzam@gentoo.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).