From: Matti Aarnio <matti.aarnio@zmailer.org>
To: George Bonser <george@gator.com>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: 2.4.3 aic7xxx wont compile
Date: Fri, 30 Mar 2001 12:05:01 +0300 [thread overview]
Message-ID: <20010330120501.P23336@mea-ext.zmailer.org> (raw)
In-Reply-To: <CHEKKPICCNOGICGMDODJOEHOCJAA.george@gator.com>
In-Reply-To: <CHEKKPICCNOGICGMDODJOEHOCJAA.george@gator.com>; from george@gator.com on Thu, Mar 29, 2001 at 11:19:22PM -0800
On Thu, Mar 29, 2001 at 11:19:22PM -0800, George Bonser wrote:
> Just tried to build 2.4.3, got:
>
> make[6]: Entering directory
> `/usr/local/src/linux/drivers/scsi/aic7xxx/aicasm'
> gcc -I/usr/include -ldb1 aicasm_gram.c aicasm_scan.c aicasm.c
> aicasm_symbol.c -o aicasm
> aicasm/aicasm_gram.y:45: ../queue.h: No such file or directory
> aicasm/aicasm_gram.y:50: aicasm.h: No such file or directory
...
> `/usr/local/src/linux/drivers/scsi/aic7xxx/aicasm'
> ...
> Looks like something's missing here. Had 2.4.2 patched to 2.4.3-pre7, backed
> out pre7 and applied 2.4.3.
Yes, "-I." from gcc flags.
The sad part is that people have been patching right and left to get
that monster utility to compile because the dependencies say that it
must be used to remake the AIC sequencer binary image; which image is
perfectly ok except of its timestampts due to patching process.
Sources from a tarball never get to this, because Linus has suffered
the episode of patching it in, and compiling once -> timestamps are
such that the resulting binary (ok, hex version of it) is newer than
the source.
There are two bugs in those aic7xxx/aicasm makefile(s):
- Missing that -I. parameter for ${CC}
- Having any sort of dependency from sequencer's images
hexified binary (which the driver includes) to its source.
While mr. Gibbs is right that it makes a lot of sense to supply
the entire tool-chain to generate all generated parts of the aic7xxx
driver, nobody should be forced to do the compilation, or then
'make mrproper' should throw away the hexified sequencer code...
Compiling of the sequencer source should be *some* make target in
that driver directory, but not any of which normal users will
encounter at any time. That is, not a dependency target !
Very few people need to go poking at the sequencer source, and
they should manage to take a bit more complicated approach, than
'make bzImage' or 'make modules' to achieve that.
(i.e.: cd drivers/scsi/aic7xxx;make XYZ)
/Matti Aarnio -- presenting own opinnions, obviously
next prev parent reply other threads:[~2001-03-30 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 7:19 George Bonser
2001-03-30 9:05 ` Matti Aarnio [this message]
2001-03-30 15:09 ` Justin T. Gibbs
2001-03-30 17:35 ` Jeff Garzik
2001-03-30 17:40 ` Justin T. Gibbs
2001-03-30 18:01 ` Jeff Garzik
2001-03-30 23:13 ` Miles Lane
2001-04-02 23:27 ` Alan Cox
2001-03-30 10:01 ` Jeff Garzik
2001-03-30 15:08 ` Justin T. Gibbs
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=20010330120501.P23336@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=george@gator.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®