Re: 2.4.27+stdarg+gcc-3.4.1

[Richard B. Johnson]

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.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/