All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre <pierre42d@9online.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem compiling udev 146
Date: Tue, 03 Nov 2009 13:30:48 +0000	[thread overview]
Message-ID: <4AF03088.4070301@9online.fr> (raw)
In-Reply-To: <4AEEEBCC.9030908@9online.fr>

Stephan Raue wrote:
> Am 02.11.2009 17:36, schrieb Pierre:
>> Stephan Raue wrote:
>>> you need openat functions in your libc, what libc you use?
>>
>> glibc 2.2.5
>> seems a bit old yes.
>> what minimum version is required ?
>>
>> Best regards,
>>
> i think 2.8 but i dont know this exactly

Ok I finally managed to upgrade my glibc to version 2.10.

But I now have another problem :

# make
make --no-print-directory all-recursive
Making all in .
   CC     extras/hid2hci/extras_hid2hci_hid2hci-hid2hci.o
In file included from extras/hid2hci/hid2hci.c:31:
/usr/include/linux/hiddev.h:40: error: parse error before "__u32"
/usr/include/linux/hiddev.h:42: error: parse error before "devnum"
/usr/include/linux/hiddev.h:43: error: parse error before "ifnum"
/usr/include/linux/hiddev.h:44: error: parse error before "vendor"
/usr/include/linux/hiddev.h:45: error: parse error before "product"
/usr/include/linux/hiddev.h:46: error: parse error before "version"
/usr/include/linux/hiddev.h:47: error: parse error before "num_applications"
/usr/include/linux/hiddev.h:51: error: parse error before "__u32"
[...]


-- 
Pierre.


      parent reply	other threads:[~2009-11-03 13:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 14:25 Problem compiling udev 146 Pierre
2009-11-02 14:40 ` Stephan Raue
2009-11-02 16:36 ` Pierre
2009-11-02 16:43 ` Stephan Raue
2009-11-02 16:57 ` Marco d'Itri
2009-11-02 17:34 ` Bryan Kadzban
2009-11-03 13:30 ` Pierre [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=4AF03088.4070301@9online.fr \
    --to=pierre42d@9online.fr \
    --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.