From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [announce] scsi_id release 0.2
Date: Sun, 07 Dec 2003 19:59:15 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107083409800863@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107081173918885@msgid-missing>
On Sun, Dec 07, Patrick Mansfield wrote:
> On Sun, Dec 07, 2003 at 04:38:02PM +0100, Olaf Hering wrote:
> > On Fri, Dec 05, Patrick Mansfield wrote:
> >
> > > Version 0.2 of scsi_id is available at:
> > >
> > > http://www-124.ibm.com/storageio/scsi_id/scsi_id-0.2.tar.gz
> >
> > What is $(DEBUG)? It is used by klibc and replaced by true/false.
>
> I use it to compile with -g.
>
> i.e.:
>
> # make DEBUG=-g
> cc -DSCSI_ID_VERSION=\"0.2\" -g -Wall -c -o scsi_id.o scsi_id.c
> cc -DSCSI_ID_VERSION=\"0.2\" -g -Wall -c -o scsi_serial.o scsi_serial.c
> cc -o scsi_id scsi_id.o scsi_serial.o -lsysfs
>
> The udev DEBUG value does not get passed down to the extras, so the
> scsi_id build under udev should be OK.
It does. make EXTRAS=extras/scsi_id will pass DEBUG˙lse/true if
defined.
> Is it breaking your build? If so I'll just remove it.
Yes, just try to build a udev debug binary.
I need also this patch because gcc decides that a printf("\n"); could be
done with a putchar, which is not defined for some reasons.
--- extras/scsi_id/Makefile.orig 2003-12-07 15:05:33.000000000 +0100
+++ extras/scsi_id/Makefile 2003-12-07 15:14:09.000000000 +0100
@@ -27,7 +27,7 @@ INSTALL_DATA = ${INSTALL} -m 644
# Note some of the variables used here are set when built under udev, and
# otherwise might not be set.
-override CFLAGS+=-DSCSI_ID_VERSION=\"$(SCSI_ID_VERSION)\" $(DEBUG) -Wall
+override CFLAGS+=-DSCSI_ID_VERSION=\"$(SCSI_ID_VERSION)\" -Wall -fno-builtin
PROG=scsi_id
SYSFS=-lsysfs
Greg has the new scsi_id already merged into the bk repo.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&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 prev parent reply other threads:[~2003-12-07 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 15:38 [announce] scsi_id release 0.2 Olaf Hering
2003-12-07 19:42 ` Patrick Mansfield
2003-12-07 19:59 ` Olaf Hering [this message]
2003-12-07 20:38 ` Patrick Mansfield
2003-12-12 14:27 ` Rask Ingemann Lambertsen
-- strict thread matches above, loose matches on Subject: below --
2003-12-05 23:18 Patrick Mansfield
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-107083409800863@msgid-missing \
--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).