> The sad part is that there has been a fix for this "problem", supplied
> by the author of the driver, for well over a month that everyone seems
> to ignore.
I've not had a patch from the author to apply so I've not applied anything.
Alan
-
To unsubscribe from this list: send the line "unsubsc
"Justin T. Gibbs" wrote:
>
> >You cannot expect that all people will instantly start using the
> >latest driver from your Web site, immediately. Especially considering
>
> I guess I expect people posting on LK to read it. There have been
> announcements for all the driver versions on that list
On Fri, 30 Mar 2001, Justin T. Gibbs wrote:
> >You cannot expect that all people will instantly start using the
> >latest driver from your Web site, immediately. Especially considering
>
> I guess I expect people posting on LK to read it. There have been
> announcements for all the driver ve
>You cannot expect that all people will instantly start using the
>latest driver from your Web site, immediately. Especially considering
I guess I expect people posting on LK to read it. There have been
announcements for all the driver versions on that list, I've responded
to all of the threads
On Fri, 30 Mar 2001, Justin T. Gibbs wrote:
> > 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 ima
> 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
>Just tried to build 2.4.3, got:
Grumble. Grumble. Grumble.
We've been through this before. The 6.1.8 version of the
driver has a fixed Makefile, doesn't even attempt to assemble
the firmware unless you config your kernel to turn it on, and has
been out for over a month now.
I guess it will ha
Hei
I have tried to compile 2.4.3 and got a error in aic7xxx:
--
make -C scsi
make[2]: Entering directory `/usr/src/linux-2.4.3/drivers/scsi'
make -C aic7xxx
make[3]: Entering directory `/usr/src/linux-2.4.3/drivers/scsi/aic7xxx
On Thu, 29 Mar 2001, 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 s
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:
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:
11 matches
Mail list logo
