From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - program to query all device attributes to build a rule
Date: Tue, 20 Jan 2004 14:07:00 +0000 [thread overview]
Message-ID: <20040120140700.GA23410@suse.de> (raw)
In-Reply-To: <20040118063050.GA22137@vrfy.org>
On Sun, Jan 18, Kay Sievers wrote:
> Hi,
> here is a small program to query all attributes of a device and
> print these in the udev key format. It may help to get the keys to
> define a rule.
I get link errors without this patch.
make 'EXTRAS=extras/scsi_id extras/udevinfo' USE_LOGúlse USE_KLIBC=true STRIP=/bin/true
Maybe I should build it against glibc.
--- udev.bk/extras/udevinfo/Makefile 2004-01-18 15:50:58.000000000 +0100
+++ udev-013/extras/udevinfo/Makefile 2004-01-20 15:02:53.000000000 +0100
@@ -1,5 +1,6 @@
PROG=udevinfo
LD=$(CC)
+override SYSFS= -L../../libsysfs -lsysfs
OBJS=udevinfo.o
all: $(PROG)
@@ -8,7 +9,7 @@ clean:
rm -f $(PROG) $(OBJS)
$(PROG): $(OBJS)
- $(LD) $(LDFLAGS) -o $(PROG) $(CRT0) $(OBJS) $(SYSFS)
+ $(LD) $(LDFLAGS) -o $(PROG) $(CRT0) $(OBJS) $(SYSFS) $(LIB_OBJS) $(ARCH_LIB_OBJS)
me:
cd ../..; make EXTRAS=extras/udevinfo
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÃœRNBERG
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
prev parent reply other threads:[~2004-01-20 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 6:30 [PATCH] udev - program to query all device attributes to build a rule Kay Sievers
2004-01-18 13:59 ` Kay Sievers
2004-01-19 19:47 ` Greg KH
2004-01-20 14:07 ` Olaf Hering [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=20040120140700.GA23410@suse.de \
--to=olh@suse.de \
--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).