public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.27+stdarg+gcc-3.4.1
Date: Mon, 26 Jul 2004 00:58:21 +0200	[thread overview]
Message-ID: <20040725225821.GA4745@werewolf.able.es> (raw)
In-Reply-To: <18199.1090681162@ocs3.ocs.com.au> (from kaos@ocs.com.au on Sat, Jul 24, 2004 at 16:59:22 +0200)

[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]


On 2004.07.24, 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.
> 

Sorry, I won't have time to do more dignostics until wednesday.
I'll be back then...

Just one note. 2.6 builds fine with this gcc...

werewolf:~# gcc -v
Reading specs from /usr/lib/gcc/i586-mandrake-linux-gnu/3.4.1/specs
Configured with: ../configure --prefix=/usr --libdir=/usr/lib --with-slibdir=/li
b --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-thr
eads=posix --disable-checking --enable-long-long --enable-__cxa_atexit --enable-
clocale=gnu --disable-libunwind-exceptions --enable-languages=c,c++,ada,f77,objc
,java --host=i586-mandrake-linux-gnu --with-system-zlib
Thread model: posix
gcc version 3.4.1 (Mandrakelinux (Alpha 3.4.1-2mdk)


--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.1 (Alpha 1) for i586
Linux 2.6.8-rc1-jam2 (gcc 3.4.1 (Mandrakelinux (Alpha 3.4.1-2mdk)) #1

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-07-25 22:58 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 ` 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     ` J.A. Magallon [this message]
     [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=20040725225821.GA4745@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=kaos@ocs.com.au \
    --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