From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: jamagallon@able.es, linux-kernel@vger.kernel.org
Subject: Re: 2.4.27+stdarg+gcc-3.4.1
Date: Sat, 24 Jul 2004 09:19:04 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0407240915260.2402@chaos> (raw)
In-Reply-To: <200407240203.i6O23p2L004061@harpo.it.uu.se>
On Sat, 24 Jul 2004, Mikael Pettersson wrote:
> On Sat, 24 Jul 2004 02:14:21 +0200, J.A. Magallon wrote:
> >With gcc-3.4.1 I get the following error when building 2.4.27-rc3.
> >Any suggestion ?
> >
> >gcc -D__KERNEL__ -nostdinc -iwithprefix include -I/usr/src/linux-2.4.27-rc3=
> >-jam1/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-alia=
> >sing -fno-common -fomit-frame-pointer -mpreferred-stack-boundary=3D2 -msoft=
> >-float -march=3Dpentium3 -fno-unit-at-a-time -DKBUILD_BASENAME=3Ddo_mount=
> >s -c -o init/do_mounts.o init/do_mounts.c
> >init/do_mounts.c: In function `change_floppy':
> >init/do_mounts.c:424: error: `va_list' undeclared (first use in this functi=
> >on)
> >init/do_mounts.c:424: error: (Each undeclared identifier is reported only o=
> >nce
> >init/do_mounts.c:424: error: for each function it appears in.)
> >init/do_mounts.c:424: error: syntax error before "args"
> >init/do_mounts.c:425: warning: implicit declaration of function `va_start'
> >init/do_mounts.c:425: error: `args' undeclared (first use in this function)
> >init/do_mounts.c:426: warning: implicit declaration of function `vsprintf'
> >init/do_mounts.c:427: warning: implicit declaration of function `va_end'
> >make: *** [init/do_mounts.o] Error 1
>
> gcc picks stdarg.h from its own private install directory,
> which you specified with --prefix=$prefix at configure-time.
> $prefix/lib/gcc/i686-pc-linux-gnu/3.4.1/include/stdarg.h in my case.
>
> I suspect you either mis-configured your gcc-3.4.1, or somehow
> broke the installation.
>
> /Mikael
> >gcc -D__KERNEL__ -nostdinc -iwithprefix include
^^^^^^^_______
This will prevent it from using its private copy of stdarg.h.
There needs to be one in the -I<include-path>
Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-07-24 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 2:03 2.4.27+stdarg+gcc-3.4.1 Mikael Pettersson
2004-07-24 13:19 ` Richard B. Johnson [this message]
2004-07-24 14:59 ` 2.4.27+stdarg+gcc-3.4.1 Keith Owens
2004-07-25 0:03 ` 2.4.27+stdarg+gcc-3.4.1 Richard B. Johnson
2004-07-26 18:49 ` 2.4.27+stdarg+gcc-3.4.1 Alexandre Oliva
2004-07-25 22:58 ` 2.4.27+stdarg+gcc-3.4.1 J.A. Magallon
[not found] <200407250127.55782.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-25 1:31 ` 2.4.27+stdarg+gcc-3.4.1 Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2004-07-24 0:14 2.4.27+stdarg+gcc-3.4.1 J.A. Magallon
2004-07-24 1:56 ` 2.4.27+stdarg+gcc-3.4.1 Keith Owens
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=Pine.LNX.4.53.0407240915260.2402@chaos \
--to=root@chaos.analogic.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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®