All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Arnvid Karstad <arnvid@karstad.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems compiling 2.4.7 with DAC960
Date: Mon, 30 Jul 2001 08:31:53 +0200	[thread overview]
Message-ID: <20010730083153.B1981@suse.de> (raw)
In-Reply-To: <20010730073901.A59C.ARNVID@karstad.org>
In-Reply-To: <20010730073901.A59C.ARNVID@karstad.org>

On Mon, Jul 30 2001, Arnvid Karstad wrote:
> Hiya,
> 
> I can't seem to be getting 2.4.7 to compile on one of our boxes.
> I get this error:
> 
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.7/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686    -DEXPORT_SYMTAB -c DAC960.c
> DAC960.c: In function `DAC960_ProcessRequest':
> DAC960.c:2771: structure has no member named `sem'
> make[3]: *** [DAC960.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.7/drivers/block'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.7/drivers/block'
> make[1]: *** [_subdir_block] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.7/drivers'
> make: *** [_dir_drivers] Error 2
> [root@x linux]# 
> 
> I get the same error when trying to compile it as a module..
> Is it broken, or is something else broken?

General hint: search the archives before posting, maybe someone else
already did and someone just might have posted a fix. This subject has
come up several times now :-)

But -> get 2.4.8-pre2, it includes updates to DAC960 to make it work
with the new completion interface.

-- 
Jens Axboe


      reply	other threads:[~2001-07-30  6:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30  5:48 Problems compiling 2.4.7 with DAC960 Arnvid Karstad
2001-07-30  6:31 ` Jens Axboe [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=20010730083153.B1981@suse.de \
    --to=axboe@suse.de \
    --cc=arnvid@karstad.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.