From: "Jürg Billeter" <j@bitron.ch>
To: linux-hotplug@vger.kernel.org
Subject: udev-076 and klibc
Date: Wed, 30 Nov 2005 20:41:47 +0000 [thread overview]
Message-ID: <1133383307.3907.4.camel@juerg-pd.bitron.ch> (raw)
Hi
Requiring glibc's byteswap seems to break the build of volume_id with
klibc 1.1.1 (klibc doesn't provide byteswap.h)
http://kernel.org/git/?p=linux/hotplug/udev.git;a=commit;hˆbe7e8887e9284666b7844bb0faa84fbb699fb2
Regards,
Jürg
--
Jürg Billeter <j@bitron.ch>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&opÌk
_______________________________________________
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 reply other threads:[~2005-11-30 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 20:41 Jürg Billeter [this message]
2005-11-30 23:17 ` udev-076 and klibc Kay Sievers
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=1133383307.3907.4.camel@juerg-pd.bitron.ch \
--to=j@bitron.ch \
--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).