mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.9 SCSI driver compile error w/gcc-3.4.2.
Date: Wed, 24 Nov 2004 12:05:27 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0411241205240.19627@p500> (raw)
In-Reply-To: <20041124170327.GB19873@stusta.de>

Ahh, ok thanks!

On Wed, 24 Nov 2004, Adrian Bunk wrote:

> On Wed, Nov 24, 2004 at 08:13:06AM -0500, Justin Piszcz wrote:
>> Under slackware-current, gcc-3.4.2.
>>
>> root@p500b:/usr/src/linux# make modules
>>   CHK     include/linux/version.h
>> make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
>>   CC [M]  drivers/scsi/cpqfcTScontrol.o
>> drivers/scsi/cpqfcTScontrol.c:609:2: #error This is too much stack
>> drivers/scsi/cpqfcTScontrol.c:721:2: #error This is too much stack
>> make[2]: *** [drivers/scsi/cpqfcTScontrol.o] Error 1
>> ...
>
> This compile error (as well as the other two compile errors you
> reported) comes from the fact, that you disabled the option
>
>  Code maturity level options
>    Prompt for development and/or incomplete code/drivers
>      Select only drivers expected to compile cleanly
>
>
> It's known that some drivers do not compile and marked in the Kconfig
> files. But if you choose to try to compile them anyway, they don't
> compile.
>
>
> cu
> Adrian
>
> -- 
>
>       "Is there not promise of rain?" Ling Tan asked suddenly out
>        of the darkness. There had been need of rain for many days.
>       "Only a promise," Lao Er said.
>                                       Pearl S. Buck - Dragon Seed
>

  reply	other threads:[~2004-11-24 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 13:13 Justin Piszcz
2004-11-24 17:03 ` Adrian Bunk
2004-11-24 17:05   ` Justin Piszcz [this message]
2004-11-24 18:35 Daniel_Weigert
2004-11-24 18:44 ` Adrian Bunk

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=Pine.LNX.4.61.0411241205240.19627@p500 \
    --to=jpiszcz@lucidpixels.com \
    --cc=bunk@stusta.de \
    --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®