public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8.1-mm2 make ?config fails
Date: Fri, 20 Aug 2004 06:07:18 +0100	[thread overview]
Message-ID: <41258706.1050103@blueyonder.co.uk> (raw)
In-Reply-To: <41251DCC.9070601@blueyonder.co.uk>

FIXED! I had some header file in /usr/include that was mangled.
Regards
Sid.

Sid Boyce wrote:

> make xconfig/config/menuconfig/oldconfig - SuSE 9.1 Athlon 3000+. All 
> is fine on x86_64 Athlon 3000+ laptop with SuSE 9.1 x86_64.
> barrabas:/usr/src/linux-2.6.8.1-mm2 # make mrproper
>  CLEAN   scripts/basic
>  CLEAN   scripts/kconfig
>  CLEAN   .config .config.old
> barrabas:/usr/src/linux-2.6.8.1-mm2 # make xconfig
>  HOSTCC  scripts/basic/fixdep
> scripts/basic/fixdep.c: In function `do_config_file':
> scripts/basic/fixdep.c:275: warning: implicit declaration of function 
> `close'
>  HOSTCC  scripts/basic/split-include
> scripts/basic/split-include.c: In function `main':
> scripts/basic/split-include.c:97: warning: implicit declaration of 
> function `chdir'
>  HOSTCC  scripts/basic/docproc
> scripts/basic/docproc.c: In function `exec_kernel_doc':
> scripts/basic/docproc.c:84: warning: implicit declaration of function 
> `fork'
> scripts/basic/docproc.c:89: warning: implicit declaration of function 
> `execvp'
>  SHIPPED scripts/kconfig/zconf.tab.h
>  HOSTCC  scripts/kconfig/conf.o
> scripts/kconfig/conf.c: In function `main':
> scripts/kconfig/conf.c:498: warning: implicit declaration of function 
> `isatty'
> sed < scripts/kconfig/lkc_proto.h > scripts/kconfig/lkc_defs.h 
> 's/P(\([^,]*\),.*/#define \1 (\*\1_p)/'
>  HOSTCC  scripts/kconfig/kconfig_load.o
>  HOSTCC  scripts/kconfig/mconf.o
> scripts/kconfig/mconf.c: In function `init_wsize':
> scripts/kconfig/mconf.c:116: error: `STDIN_FILENO' undeclared (first 
> use in this function)
> scripts/kconfig/mconf.c:116: error: (Each undeclared identifier is 
> reported only once
> scripts/kconfig/mconf.c:116: error: for each function it appears in.)
> scripts/kconfig/mconf.c: In function `exec_conf':
> scripts/kconfig/mconf.c:223: warning: implicit declaration of function 
> `pipe'
> scripts/kconfig/mconf.c:224: warning: implicit declaration of function 
> `fork'
> scripts/kconfig/mconf.c:227: warning: implicit declaration of function 
> `dup2'
> scripts/kconfig/mconf.c:228: warning: implicit declaration of function 
> `close'
> scripts/kconfig/mconf.c:230: warning: implicit declaration of function 
> `execv'
> scripts/kconfig/mconf.c:231: warning: implicit declaration of function 
> `_exit'
> scripts/kconfig/mconf.c:238: warning: implicit declaration of function 
> `read'
> scripts/kconfig/mconf.c: In function `conf':
> scripts/kconfig/mconf.c:441: warning: implicit declaration of function 
> `unlink'
> scripts/kconfig/mconf.c: In function `show_textbox':
> scripts/kconfig/mconf.c:551: warning: implicit declaration of function 
> `write'
> make[1]: *** [scripts/kconfig/mconf.o] Error 1
> make: *** [xconfig] Error 2
>
> Regards
> Sid.
>


-- 
Sid Boyce .... Hamradio G3VBV and keen Flyer
=====LINUX ONLY USED HERE=====


      reply	other threads:[~2004-08-20  5:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 21:38 2.6.8.1-mm2 make ?config fails Sid Boyce
2004-08-20  5:07 ` Sid Boyce [this message]

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=41258706.1050103@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --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