public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olivier MATZ <zer0@droids-corp.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] asm-i386 : config.h should not be included out of kernel
Date: Wed, 07 Dec 2005 21:09:50 +0100	[thread overview]
Message-ID: <4397418E.3070400@droids-corp.org> (raw)
In-Reply-To: <20051207191030.GA7585@mars.ravnborg.org>

Hi Sam,

> If you look at the commandline passed to gcc you will notice -include
> include/linux/autoconf.h which tell gcc to pull in autoconf.h.
> So it is no longer required to include config.h.

I'm not sure. On my 2.6.14.3, this is a compilation line :

gcc -m32 -Wp,-MD,kernel/.sys.o.d  -nostdinc -isystem
/usr/lib/gcc-lib/i486-linux-gnu/3.3.6/include -D__KERNEL__ -Iinclude
-Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing
-fno-common -ffreestanding -Os     -fno-omit-frame-pointer
-fno-optimize-sibling-calls -g -pipe -msoft-float
-mpreferred-stack-boundary=2  -march=i686 -mregparm=3
-Iinclude/asm-i386/mach-default      -DKBUILD_BASENAME=sys
-DKBUILD_MODNAME=sys -c -o kernel/.tmp_sys.o kernel/sys.c

Moreover, if I try to compile a C file which only define a variable and
assign it to a CONFIG_XXX, it doesn't work. Did I do something wrong ?

Olivier

  parent reply	other threads:[~2005-12-07 20:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 20:26 [PATCH] asm-i386 : config.h should not be included out of kernel Olivier MATZ
2005-12-06 21:11 ` Arnd Bergmann
2005-12-07 17:28   ` Olivier MATZ
2005-12-07 19:10     ` Sam Ravnborg
2005-12-07 20:02       ` Andrew Walrond
2005-12-07 20:09       ` Olivier MATZ [this message]
2005-12-07 21:32         ` Sam Ravnborg
2005-12-08 11:33           ` Olivier MATZ
2005-12-08 17:39             ` Sam Ravnborg

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=4397418E.3070400@droids-corp.org \
    --to=zer0@droids-corp.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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