public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mogens Valentin <monz@danbbs.dk>
To: dougg@torque.net
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [ANNOUNCE] sdparm 0.92
Date: Wed, 25 May 2005 20:07:02 +0200	[thread overview]
Message-ID: <4294BEC6.30005@danbbs.dk> (raw)
In-Reply-To: <42949D2E.5020309@danbbs.dk>

Mogens Valentin wrote:
> Douglas Gilbert wrote:
> 
>> Mogens Valentin wrote:
>>
>>> Douglas Gilbert wrote:
>>>
>>>> Mogens Valentin wrote:
>>>>
>>>>> Douglas Gilbert wrote:
>>>>>
>>>>>> With sg_start (in the sg3_utils package) I have tried
>>>>>> to spin up and down an ATA disk inside a USB enclosure
>>>>>> without success. The same command on a USB connected
>>>>>> CD/DVD combo drive did work.
>>>>>>
>>>>>> Could you try sg_start on your USB external enclosure
>>>>>> which I assume contains an ATA disk rather than a
>>>>>> SCSI (SPI) disk and report if it works?
>>>>>
>>>>> Sure. Got it, compiled, but got the error:
>>>>>   .../usr/include/scsi/sg.h /usr/include/scsi/scsi.h
>>>>>   /usr/include/stdint.h   sg_lib.h sg_cmds.h llseek.h
>>>>>   gcc: cannot specify -o with -c or -S and multiple compilations
>>>>>   make: *** [sgp_dd.o] Error 1
>>>>>
>>>>> I could only find  -o  and  -c  in the makefiles around line 95.
>>>>>
>>>>> Slack 9.1 / 2.6.10 from sources.
>>>>
>>>> Could you try the sg3_utils-1.15.tgz beta at the
>>>> top of http://www.torque.net/sg [in the news section].
>>>> Hopefully that cures the compile problem.
>>>
>>> Nope, but it changes the error. You changed the makefile exactly as I 
>>> tried it, removing '-c' in line 95.
>>> This results in missing header files compiles:
> 
>>> ...
>>> creating sg_dd
>>> gcc  -g -O2 -Wall -W -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 
>>> -D_REENTRANT -c sgp_dd.c ...
>>> .../usr/include/stdint.h sg_lib.h sg_cmds.h llseek.h
>>> gcc: compilation of header file requested
>>> gcc: compilation of header file requested
>>> ...
>>> make: *** [sgp_dd.o] Error 1
>>>
>>>
>>> Forgot to mention I have gcc version 3.2.3, FWIW..
>>> It's not exactly an uncommon problem; I googled a bit :p
>>> I haven't pinpointed the problem as yet, but found comments (from 
>>> compiling other apps) that it could be either a gcc versioning 
>>> problem, a problem with -I or -D switches, or simply a Makefile problem.

Dear oh dear!  Forgot to tell you I did:
   make clean; make dep; make

Doing just  make clean; make  did the job. Sorry about the problems.
Still,  make dep  ought to work :p

Doesn't change the fact that either my Prolific interface or the disk 
doesn't support the needed scsi modes..

-- 
Kind regards,
Mogens Valentin


      reply	other threads:[~2005-05-25 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 11:12 [ANNOUNCE] sdparm 0.92 Douglas Gilbert
2005-05-23 20:06 ` Bill Davidsen
2005-05-24 23:49 ` Mogens Valentin
2005-05-25  1:40   ` Douglas Gilbert
2005-05-25  2:42     ` Mogens Valentin
     [not found]       ` <429466EC.3080801@torque.net>
     [not found]         ` <429478C2.3000003@danbbs.dk>
     [not found]           ` <429480F9.6050802@torque.net>
2005-05-25 15:43             ` Mogens Valentin
2005-05-25 18:07               ` Mogens Valentin [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=4294BEC6.30005@danbbs.dk \
    --to=monz@danbbs.dk \
    --cc=dougg@torque.net \
    --cc=linux-scsi@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