public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Olaf Hering <olh@suse.de>
Cc: linux-scsi@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [announce] scsi_id release 0.2
Date: Sun, 7 Dec 2003 11:42:42 -0800	[thread overview]
Message-ID: <20031207114242.A29572@beaverton.ibm.com> (raw)
In-Reply-To: <20031207153802.GA6700@suse.de>; from olh@suse.de on Sun, Dec 07, 2003 at 04:38:02PM +0100

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.

Is it breaking your build? If so I'll just remove it.

The scsi_id debug logging via the "-v" or when DEBUG is set is always
enabled - it outputs to syslog LOG_DEBUG when called from udev, or via
stderr when used via the command line. (Though the klibc strerror() only
prints the errno value, making for some odd error messages.)

-- Patrick Mansfield

  reply	other threads:[~2003-12-07 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05 23:18 [announce] scsi_id release 0.2 Patrick Mansfield
2003-12-07 15:38 ` Olaf Hering
2003-12-07 19:42   ` Patrick Mansfield [this message]
2003-12-07 19:59     ` Olaf Hering
2003-12-07 20:38       ` Patrick Mansfield
2003-12-12 14:27       ` Rask Ingemann Lambertsen

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=20031207114242.A29572@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olh@suse.de \
    /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