From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: udev - changing libsysfs header file location
Date: Tue, 17 Feb 2004 21:32:33 +0000 [thread overview]
Message-ID: <20040217133233.A11743@beaverton.ibm.com> (raw)
Hi Greg -
The location of the libsysfs headers is different when building with udev
versus building against the installed sysfsutils.
Can you bk mv the libsysfs header files to the same subdirectory as seen
after installing sysfsutil? And then apply patch being sent as a followup
email.
That is, move the headers located under udev libsysfs to libsysfs/sysfs.
This would avoid problems with extras programs that want to build with and
without udev, for example scsi_id ;-)
To clarify here's the current scsi_id hack, it will not always work right
when building udev without klibc, as it will either pick up the locally
installed versions of /usr/include/sysfs/libsysfs.h, or if sysfsutils is
not installed fail compilation:
#ifdef __KLIBC__
/*
* Assume built under udev with KLIBC
*/
#include <libsysfs.h>
#else
#include <sysfs/libsysfs.h>
#endif
-- Patrick Mansfield
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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:[~2004-02-17 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 21:32 Patrick Mansfield [this message]
2004-02-18 0:04 ` udev - changing libsysfs header file location Greg KH
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=20040217133233.A11743@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--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).