linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Stekloff <dsteklof@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 006 release
Date: Thu, 20 Nov 2003 15:25:34 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106934246810725@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106925954815986@msgid-missing>

On Wednesday 19 November 2003 10:59 pm, Olaf Hering wrote:
>  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?


As a note, the package sysfsutils that contains libsysfs installs the headers 
into /usr/include/sysfs. Are we going to have conflicts since udev has its 
own private libsysfs statically included? Should the extra programs build off 
udev's libsysfs, since they are included with the package? Or, should they 
require a shared libsysfs from sysfsutils? If udev is to have its own static 
edition of libsysfs, perhaps it'd be best if it didn't install headers and 
the extras either used its static version or required the shared libsysfs to 
be installed.

Thanks,

Dan


> --- 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"



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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

  parent reply	other threads:[~2003-11-20 15:25 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  1:12 ` Dave Jones
2003-11-20  6:59 ` Olaf Hering
2003-11-20 15:25 ` Daniel Stekloff [this message]
2003-11-20 16:59 ` Greg KH
2003-11-20 17:00 ` 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=marc-linux-hotplug-106934246810725@msgid-missing \
    --to=dsteklof@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).