public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: root@chaos.analogic.com, Mikael Pettersson <mikpe@csd.uu.se>,
	jamagallon@able.es, linux-kernel@vger.kernel.org
Subject: Re: 2.4.27+stdarg+gcc-3.4.1
Date: Sun, 25 Jul 2004 11:31:46 +1000	[thread overview]
Message-ID: <5983.1090719106@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 25 Jul 2004 01:27:55 +0300." <200407250127.55782.vda@port.imtp.ilyichevsk.odessa.ua>

On Sun, 25 Jul 2004 01:27:55 +0300, 
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua> wrote:
>On Saturday 24 July 2004 17:59, Keith Owens wrote:
>> On Sat, 24 Jul 2004 09:19:04 -0400 (EDT),
>>
>> "Richard B. Johnson" <root@chaos.analogic.com> wrote:
>> >> >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>
>>
>> No.  -iwithprefix include picks up the private path.  It is probably a
>> misconfigured gcc, but I am waiting on detailed diagnostics to be sure.
>
>I have such 'misconfigured' gcc for a very long time.
>I compiled a lot of stuff with it.
>
>Nothing complains except the kernel.

Only the kernel adds '-nostdinc -withprefix include'.
 
>GCC_EXEC_PREFIX=/usr/app/gcc-3.3.3/lib/gcc-lib/
>
>fixes it for me.

Which makes it a local gcc build problem.  I run 3.3.3 and it handles
-nostdinc -iwithprefix include correctly.  Compile init/do_mounts.c
with gcc -v to get the list of include paths for your version of gcc,
stdarg.h will not be on those paths.  Rebuild your version of gcc with
the correct paths.


       reply	other threads:[~2004-07-25  1:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200407250127.55782.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-25  1:31 ` Keith Owens [this message]
2004-07-24  2:03 2.4.27+stdarg+gcc-3.4.1 Mikael Pettersson
2004-07-24 13:19 ` 2.4.27+stdarg+gcc-3.4.1 Richard B. Johnson
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
  -- 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=5983.1090719106@ocs3.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=root@chaos.analogic.com \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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