All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: scsi_lib.c undefined symbol
Date: Mon, 03 Sep 2001 16:43:38 +1000	[thread overview]
Message-ID: <16485.999499418@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 03 Sep 2001 00:19:17 -0400." <3B9304C5.4070006@lycosmail.com>

On Mon, 03 Sep 2001 00:19:17 -0400, 
Adam Schrotenboer <ajschrotenboer@lycosmail.com> wrote:
>I have gotten this a couple times w/ other versions of the kernel, but 
>this is 2.4.9-ac6. (2.4.8-ac12 worked, but that may be a fluke)
>
>gcc -D__KERNEL__ -I/mnt/hda3/kernel/2.4.9-ac6/linux/include -Wall 
>-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer 
>-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 
>-march=athlon  -DMODULE -DMODVERSIONS -include 
>/mnt/hda3/kernel/2.4.9-ac6/linux/include/linux/modversions.h   -c -o 
>scsi_lib.o scsi_lib.c
>scsi_lib.c: In function `__scsi_end_request':
>scsi_lib.c:379: `queued_sectors_Rc37b18c1' undeclared (first use in this 
>function)

User error.  scsi_lib.c comes from 2.4.9-ac6 but include/linux/blkdev.h
is still at base 2.4.9.  Your patches did not apply clean, start from a
fresh source tree and retry.  blkdev.h must contain queued_sectors, it
must not contain max_segments.


      parent reply	other threads:[~2001-09-03  6:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03  4:19 scsi_lib.c undefined symbol Adam Schrotenboer
2001-09-03  4:49 ` Keith Owens
2001-09-03  6:43 ` Keith Owens [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=16485.999499418@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=ajschrotenboer@lycosmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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.