From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Hollis Blanchard <hollis@austin.ibm.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: cross-compiler and stdarg.h
Date: Fri, 11 Oct 2002 12:46:23 +0200 [thread overview]
Message-ID: <3DA6ABFF.FF441B87@imc-berlin.de> (raw)
In-Reply-To: Pine.LNX.4.44.0210101627210.9384-100000@sandstone.austin.ibm.com
Hollis Blanchard wrote:
>
> On Thu, 10 Oct 2002, D'Abbraccio Joe-ljd015 wrote:
> >
> > When I build the kernel using the ELDK I get the following failure:
> > >>>>>
> > ppc_82xx-gcc -D__KERNEL__ -I/usr/opt/kernels/linuxppc_2_4_devel/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -I/usr/opt/kernels/linuxppc_2_4_devel/arch/ppc -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -nostdinc -iwithprefix include -DKBUILD_BASENAME=sched -fno-omit-frame-pointer -c -o sched.o sched.c
> > In file included from /usr/opt/kernels/linuxppc_2_4_devel/include/linux/wait.h:13,
> > from /usr/opt/kernels/linuxppc_2_4_devel/include/linux/fs.h:12,
> > from /usr/opt/kernels/linuxppc_2_4_devel/include/linux/capability.h:17,
> > from /usr/opt/kernels/linuxppc_2_4_devel/include/linux/binfmts.h:5,
> > from /usr/opt/kernels/linuxppc_2_4_devel/include/linux/sched.h:9,
> > from /usr/opt/kernels/linuxppc_2_4_devel/include/linux/mm.h:4,
> > from sched.c:23:
> > /usr/opt/kernels/linuxppc_2_4_devel/include/linux/kernel.h:10: stdarg.h: No such file or directory
> > <<<<<
> >
> > Where is stdarg.h expected to come from if not from stdinc (i.e.
> > -nostdinc). I don't believe there is one in kernel distribution.
>
> I just had this problem and I'm embarassed to say I'm not quite sure
> what caused it. I was building on a ppc64 box, but when I switched from
> the ppc32 "cross-compiler" to the native toolchain (which is ppc32) the
> problem went away.
>
> Your cross-compiler includes this file in
> <prefix>/lib/gcc-lib/powerpc-linux/<version>/include/ .
>
> -Hollis
I had this problem too. A while ago. On 2002/09/13 I posted to this list but
with no success.
I found the problem in the main Makefile:
---------------
@@ -261,7 +262,7 @@
# 'kbuild_2_4_nostdinc :=' or -I/usr/include for kernel code and you are not
UML
# then your code is broken! KAO.
-kbuild_2_4_nostdinc := -nostdinc -iwithprefix include
+kbuild_2_4_nostdinc := -nostdinc $(shell $(CC) -print-search-dirs | sed -ne
's/install: \(.*\)/-I \1include/gp')
export kbuild_2_4_nostdinc
export CPPFLAGS CFLAGS CFLAGS_KERNEL AFLAGS AFLAGS_KERNEL
---------------
I have no idea why... :o(
Cheers,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-11 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 21:22 Problems building the kernel using the ELDK D'Abbraccio Joe-ljd015
2002-10-10 21:33 ` cross-compiler and stdarg.h Hollis Blanchard
2002-10-11 10:46 ` Steven Scholz [this message]
2002-10-11 11:20 ` Query Anish
2002-10-11 11:43 ` Query Wolfgang Denk
2002-10-11 14:35 ` cross-compiler and stdarg.h Marius Groeger
-- strict thread matches above, loose matches on Subject: below --
2002-10-11 15:55 D'Abbraccio Joe-ljd015
2002-10-17 12:16 ` Marius Groeger
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=3DA6ABFF.FF441B87@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=hollis@austin.ibm.com \
--cc=linuxppc-embedded@lists.linuxppc.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.