From: system_lists@nullzone.org
To: linux-kernel@vger.kernel.org
Subject: Same with Linux 2.4.20-ac2 <-> Re: Problems compiling 2.4.20 - fail just in 'make' - please help
Date: Wed, 11 Dec 2002 22:33:05 +0100 [thread overview]
Message-ID: <5.1.1.6.2.20021211223006.00cded00@192.168.2.131> (raw)
In-Reply-To: <5.1.1.6.2.20021211210820.00cde0c0@192.168.2.131>
Same problem with Linux 2.4.20-ac2
I think its not a kernel code problem. Have any some idea about the real one?
Any compatibility problem with gcc3.2.2 in variable use?
BTW: special warning with:
-> /usr/src/linux-2.4.20/include/linux/kernel.h:10:20: stdarg.h: No such
file or directory
At 21:11 11/12/2002 +0100, system_lists@nullzone.org wrote:
>My gcc compiler:
>
>server01:/usr/src/linux-2.4.20# gcc -v
>Reading specs from /usr/lib/gcc-lib/i386-linux/3.2.2/specs
>Configured with: ../src/configure -v
>--enable-languages=c,c++,java,f77,proto,pascal,objc,ada --prefix=/usr
>--mandir=/usr/share/man --infodir=/usr/share/info
>--with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared
>--with-system-zlib --enable-nls --without-included-gettext
>--enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm
>--enable-objc-gc i386-linux
>Thread model: posix
>gcc version 3.2.2 20021202 (Debian prerelease)
>
>
>------- the fail --------
>
>server01:/usr/src/linux-2.4.20# make
>gcc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall -Wstrict-prototypes
>-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
>-pipe -mpreferred-stack-boundary=2 -march=i686 -DKBUILD_BASENAME=main -c
>-o init/main.o init/main.c
>. scripts/mkversion > .tmpversion
>gcc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall -Wstrict-prototypes
>-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
>-pipe -mpreferred-stack-boundary=2 -march=i686 -DUTS_MACHINE='"i386"'
>-DKBUILD_BASENAME=version -c -o init/version.o init/version.c
>gcc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall -Wstrict-prototypes
>-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
>-pipe -mpreferred-stack-boundary=2
>-march=i686 -DKBUILD_BASENAME=do_mounts -c -o init/do_mounts.o
>init/do_mounts.c
>make CFLAGS="-D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall
>-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
>-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 "
>-C kernel
>make[1]: Entering directory `/usr/src/linux-2.4.20/kernel'
>make all_targets
>make[2]: Entering directory `/usr/src/linux-2.4.20/kernel'
>gcc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall -Wstrict-prototypes
>-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
>-pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix
>include -DKBUILD_BASENAME=sched -fno-omit-frame-pointer -c -o sched.o sched.c
>In file included from /usr/src/linux-2.4.20/include/linux/wait.h:13,
> from /usr/src/linux-2.4.20/include/linux/fs.h:12,
> from /usr/src/linux-2.4.20/include/linux/capability.h:17,
> from /usr/src/linux-2.4.20/include/linux/binfmts.h:5,
> from /usr/src/linux-2.4.20/include/linux/sched.h:9,
> from /usr/src/linux-2.4.20/include/linux/mm.h:4,
> from sched.c:23:
>/usr/src/linux-2.4.20/include/linux/kernel.h:10:20: stdarg.h: No such file
>or directory
>In file included from /usr/src/linux-2.4.20/include/linux/wait.h:13,
> from /usr/src/linux-2.4.20/include/linux/fs.h:12,
> from /usr/src/linux-2.4.20/include/linux/capability.h:17,
> from /usr/src/linux-2.4.20/include/linux/binfmts.h:5,
> from /usr/src/linux-2.4.20/include/linux/sched.h:9,
> from /usr/src/linux-2.4.20/include/linux/mm.h:4,
> from sched.c:23:
>/usr/src/linux-2.4.20/include/linux/kernel.h:74: parse error before "va_list"
>/usr/src/linux-2.4.20/include/linux/kernel.h:74: warning: function
>declaration isn't a prototype
>/usr/src/linux-2.4.20/include/linux/kernel.h:77: parse error before "va_list"
>/usr/src/linux-2.4.20/include/linux/kernel.h:77: warning: function
>declaration isn't a prototype
>/usr/src/linux-2.4.20/include/linux/kernel.h:81: parse error before "va_list"
>/usr/src/linux-2.4.20/include/linux/kernel.h:81: warning: function
>declaration isn't a prototype
>make[2]: *** [sched.o] Error 1
>make[2]: Leaving directory `/usr/src/linux-2.4.20/kernel'
>make[1]: *** [first_rule] Error 2
>make[1]: Leaving directory `/usr/src/linux-2.4.20/kernel'
>make: *** [_dir_kernel] Error 2
>server01:/usr/src/linux-2.4.20#
>
>
>
>???????
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-12-11 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 19:21 [PATCH] intermezzo fixes for 2.5.50 Peter Braam
2002-12-11 19:43 ` Randy.Dunlap
[not found] ` <Pine.LNX.4.33L2.0212111138530.15702-100000@dragon.pdx.osdl .net>
2002-12-11 20:11 ` Problems compiling 2.4.20 - fail just in 'make' - please help system_lists
2002-12-11 21:33 ` system_lists [this message]
2002-12-11 22:34 ` Same with Linux 2.4.20-ac2 <-> " Alan Cox
2002-12-14 1:29 ` [PATCH] intermezzo update Linus Torvalds
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=5.1.1.6.2.20021211223006.00cded00@192.168.2.131 \
--to=system_lists@nullzone.org \
--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®