From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Cc: jmerkey@timpanogas.org
Subject: Re: aha152x driver build broken 2.5.1-pre2
Date: Tue, 27 Nov 2001 14:42:08 -0700 [thread overview]
Message-ID: <20011127144208.B6048@vger.timpanogas.org> (raw)
In-Reply-To: <20011127144016.A6048@vger.timpanogas.org>
In-Reply-To: <20011127144016.A6048@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Tue, Nov 27, 2001 at 02:40:16PM -0700
Linus,
Sorry. Did not see your post on this subject.
Jeff
On Tue, Nov 27, 2001 at 02:40:16PM -0700, Jeff V. Merkey wrote:
>
>
> See attached. Build broken in 2.5.1-pre2 for the aha152x drivers.
> Reporting undelcared functions.
>
> Jeff
>
> make all_targets
> make[3]: Entering directory `/usr/src/linux/drivers/scsi'
> ld -m elf_i386 -r -o scsi_mod.o scsi.o hosts.o scsi_ioctl.o constants.o scsicam.o scsi_proc.o scsi_error.o scsi_obsolete.o scsi_queue.o scsi_lib.o scsi_merge.o scsi_dma.o scsi_scan.o scsi_syms.o
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DAHA152X_STAT -DAUTOCONF -c -o aha152x.o aha152x.c
> aha152x.c: In function `aha152x_detect':
> aha152x.c:1352: `io_request_lock' undeclared (first use in this function)
> aha152x.c:1352: (Each undeclared identifier is reported only once
> aha152x.c:1352: for each function it appears in.)
> make[3]: *** [aha152x.o] Error 1
> make[3]: Leaving directory `/usr/src/linux/drivers/scsi'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux/drivers/scsi'
> make[1]: *** [_subdir_scsi] Error 2
> make[1]: Leaving directory `/usr/src/linux/drivers'
> make: *** [_dir_drivers] Error 2
prev parent reply other threads:[~2001-11-27 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 21:40 Jeff V. Merkey
2001-11-27 21:42 ` Jeff V. Merkey [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=20011127144208.B6048@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=jmerkey@timpanogas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®