All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weber <weber@nyc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.15-pre4 fails to build in setup.c
Date: Wed, 14 Nov 2001 11:37:24 -0500	[thread overview]
Message-ID: <3BF29DC4.B1BD0F1B@nyc.rr.com> (raw)
In-Reply-To: <fa.kvqcg8v.1d3c0qv@ifi.uio.no>

this is in the archives.  you'll find a patch here:

http://marc.theaimsgroup.com/?l=linux-kernel&m=100559812101821&w=2



Chris Meadors wrote:
> 
> I don't think I've seen this yet.
> 
> Build failed with this error:
> 
> 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 -malign-functions=4     -c
> -o setup.o setup.c
> setup.c: In function `c_start':
> setup.c:2791: subscripted value is neither array nor pointer
> setup.c:2792: warning: control reaches end of non-void function
> make[1]: *** [setup.o] Error 1
> make[1]: Leaving directory `/usr/src/linux/arch/i386/kernel'
> make: *** [_dir_arch/i386/kernel] Error 2
> 
> My "grep ^CONFIG .config" is attatched.
> 
> -Chris
> --
> Two penguins were walking on an iceberg.  The first penguin said to the
> second, "you look like you are wearing a tuxedo."  The second penguin
> said, "I might be..."                         --David Lynch, Twin Peaks
> 
>   ------------------------------------------------------------------------
>              Name: config
>    config    Type: Plain Text (TEXT/PLAIN)
>          Encoding: BASE64

       reply	other threads:[~2001-11-14 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.kvqcg8v.1d3c0qv@ifi.uio.no>
2001-11-14 16:37 ` John Weber [this message]
2001-11-14 16:40 2.4.15-pre4 fails to build in setup.c Chris Meadors
2001-11-14 17:52 ` Chris Meadors

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=3BF29DC4.B1BD0F1B@nyc.rr.com \
    --to=weber@nyc.rr.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.