From: Jens Axboe <axboe@suse.de>
To: Sir Ace <chandleg@wizardsworks.org>, linux-scsi@vger.kernel.org
Subject: Re: Compile problems in 2.4.20 (fwd)
Date: Wed, 22 Jan 2003 08:57:12 +0100 [thread overview]
Message-ID: <20030122075712.GV20780@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301211409340.27041-100000@wizardsworks.org>
On Tue, Jan 21 2003, Sir Ace wrote:
>
> I am attempting a compile of linus's tree of 2.4.20 on hppa platform
> linux. I am getting the error below. I'm not a developer, but after
> looking at the code, it really isn't defined anywhere that I could find.
>
> make[2]: Entering directory `/usr/src/linux-2.4.20/drivers/scsi'
> make all_targets
> make[3]: Entering directory `/usr/src/linux-2.4.20/drivers/scsi'
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
> -D__linux__ -pipe -fno-strength-reduce -mno-space-regs
> -mfast-indirect-calls -mdisable-fpregs -ffunction-sections -march=1.1
> -mschedule=7200 -nostdinc -iwithprefix include
> -DKBUILD_BASENAME=scsi_merge -c -o scsi_merge.o scsi_merge.c
> scsi_merge.c: In function `__count_segments':
> scsi_merge.c:225: warning: implicit declaration of function `page_to_phys'
> scsi_merge.c: In function `initialize_merge_fn':
> scsi_merge.c:1198: `PCI_DMA_BUS_IS_PHYS' undeclared (first use in this
> function)scsi_merge.c:1198: (Each undeclared identifier is reported only
> once
hppa hasn't been updated to support the required functions to do direct
io to highmem pages. bug the hppa developers :)
--
Jens Axboe
prev parent reply other threads:[~2003-01-22 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 22:09 Compile problems in 2.4.20 (fwd) Sir Ace
2003-01-22 7:57 ` 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=20030122075712.GV20780@suse.de \
--to=axboe@suse.de \
--cc=chandleg@wizardsworks.org \
--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