From: "Íñigo López-Barranco" <ilopez@albatros-sl.es>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Udev 172/181 doesn't find ptxdist kernel headers and fails to compile
Date: Thu, 3 May 2012 11:58:13 +0200 [thread overview]
Message-ID: <4FA256B5.5010608@albatros-sl.es> (raw)
In-Reply-To: <20120427111223.GA5566@pengutronix.de>
You are right: SOCK_NONBLOCK and SOCK_CLOEXEC are only available on
kernel >= 2.6.28 & glibc >= 2.9, and the glibc version in my toolchain
(OSELAS 1.99.3) is 2.8.
I'm going to upgrade the toolchain and try again.
Thank you!
--
Íñigo
On 27/04/12 13:12, Michael Olbrich wrote:
> On Thu, Apr 26, 2012 at 03:38:16PM +0200, Íñigo López-Barranco wrote:
>> I'm trying to build ptxdist-2012.04.0 but it fails to compile using
>> both versions of udev complaining about some undeclared defines:
>>
>> src/libudev-monitor.c: In function 'udev_monitor_new_from_socket':
>> src/libudev-monitor.c:153: error: 'SOCK_NONBLOCK' undeclared (first
>> use in this function)
>> src/libudev-monitor.c:153: error: (Each undeclared identifier is
>> reported only once
>> ...
>>
>> Searching in the list's archives found this message with a patch
>> adding the kernel headers path to the udev rules for toolchains
>> without kernel headers (or old ones):
>>
>> http://thread.gmane.org/gmane.comp.embedded.ptxdist.devel/7997/focus=8140
>>
>> I've checked that this is already included in my udev.make file,
>> that I've selected the kernel headers (2.6.39) in ptxdist menu and
>> that SOCK_NONBLOCK and other missing defines are present in the
>> kernel headers, so I don't know what else to check now.
>>
>> The gcc version is 4.3.2 and the platform is x86 (586).
>
> And the glibc version? I think you need support for the NONBLOCK stuff from
> there too.
>
> Michael
>
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-05-03 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 13:38 Íñigo López-Barranco
2012-04-27 11:12 ` Michael Olbrich
2012-05-03 9:58 ` Íñigo López-Barranco [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=4FA256B5.5010608@albatros-sl.es \
--to=ilopez@albatros-sl.es \
--cc=ptxdist@pengutronix.de \
/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