All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <falfaro@borak.es>
To: linux-kernel@vger.kernel.org
Subject: 2.5.23 won't compile
Date: Thu, 20 Jun 2002 14:41:07 +0200	[thread overview]
Message-ID: <3D11CD63.70505@borak.es> (raw)

  _Summary_

    Can't get linux kernel 2.5.23 to compile with success using config
    options in the attached file "config-2.5.23"

_Full description_

    When trying to compile the kernel using config options in
    "config-2.5.13", I get the following erros during a "make bzImage":

    make[1]: Entering directory `/usr/src/linux-2.5.23/kernel'
      gcc -Wp,-MD,./.sched.o.d -D__KERNEL__
    -I/usr/src/linux-2.5.23/include -Wall -Wstrict-prototypes
    -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
    -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc
    -iwithprefix include    -fno-omit-frame-pointer
    -DKBUILD_BASENAME=sched   -c -o sched.o sched.c
    sched.c: In function `sys_sched_setaffinity':
    sched.c:1332: `cpu_online_map' undeclared (first use in this function)
    sched.c:1332: (Each undeclared identifier is reported only once
    sched.c:1332: for each function it appears in.)
    sched.c: In function `sys_sched_getaffinity':
    sched.c:1391: `cpu_online_map' undeclared (first use in this function)
    make[1]: *** [sched.o] Error 1
    make[1]: Leaving directory `/usr/src/linux-2.5.23/kernel'
    make: *** [kernel] Error 2

_Keywords
_

    Compile, Kernel



             reply	other threads:[~2002-06-20 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 12:41 Felipe Alfaro Solana [this message]
2002-06-20 12:57 ` 2.5.23 won't compile Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 12:43 Felipe Alfaro Solana
2002-06-20 13:07 ` Erlend Aasland

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=3D11CD63.70505@borak.es \
    --to=falfaro@borak.es \
    --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.