public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, christophe.varoqui@free.fr,
	patmans@us.ibm.com
Subject: Re: [ANNOUNCE] udev 006 release
Date: Thu, 20 Nov 2003 07:59:20 +0100	[thread overview]
Message-ID: <20031120065920.GC14930@suse.de> (raw)
In-Reply-To: <20031119234708.GC23529@kroah.com>

 On Wed, Nov 19, Greg KH wrote:

> 	- I've added two external programs to the udev tarball, under
> 	  the extras/ directory.  They are the scsi-id program from Pat
> 	  Mansfield, and the multipath program from Christophe Varoqui.
> 	  Both of them can work as CALLOUT programs.  I don't think they
> 	  currently build properly within the tree, by linking against
> 	  klibc, but patches to their Makefiles to fix this would be
> 	  gladly accepted :)

There is no make install target for the headers and the libs. Both
packages disgree on the location. I use the patch below. Can you make a
decision where the headers should be located?


--- scsi_id/scsi_id.c
+++ scsi_id/scsi_id.c	2003/11/19 21:25:38
@@ -33,7 +33,7 @@
 #include <stdarg.h>
 #include <ctype.h>
 #include <sys/stat.h>
-#include <sys/libsysfs.h>
+#include <libsysfs.h>
 #include "scsi_id.h"
 
 #ifndef VERSION
--- scsi_id/scsi_serial.c
+++ scsi_id/scsi_serial.c	2003/11/19 21:25:42
@@ -31,7 +31,7 @@
 #include <unistd.h>
 #include <syslog.h>
 #include <scsi/sg.h>
-#include <sys/libsysfs.h>
+#include <libsysfs.h>
 #include "scsi_id.h"
 #include "scsi.h"
 

-- 
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG

  reply	other threads:[~2003-11-20  6:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 16:29 [ANNOUNCE] udev 006 release Greg KH
2003-11-19 23:47 ` Greg KH
2003-11-20  6:59   ` Olaf Hering [this message]
2003-11-20 15:25     ` Daniel Stekloff
2003-11-20 17:00       ` Greg KH
2003-11-20  1:12 ` Dave Jones
2003-11-20 16:59   ` 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=20031120065920.GC14930@suse.de \
    --to=olh@suse.de \
    --cc=christophe.varoqui@free.fr \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patmans@us.ibm.com \
    /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