From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@zip.com.au>
Cc: Ghozlane Toumi <ghoz@sympatico.ca>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] Fix BUG macro
Date: Fri, 17 May 2002 15:20:38 +1000 [thread overview]
Message-ID: <E178aAR-00020W-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Thu, 16 May 2002 21:50:16 MST." <3CE48C08.B0E59851@zip.com.au>
In message <3CE48C08.B0E59851@zip.com.au> you write:
> Some explanation of how this works, and of why I should not fill
> your ear with toothpaste would be appreciated here.
When an include file is found using "-I dir", __FILE__ in that include
file is "dir/filename":
gcc -D__KERNEL__ -I/usr/src/working-2.5.15-bug/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DKBUILD_BASENAME=delay -c -o delay.o delay.c
Hope that helps,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-05-17 5:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 8:08 [PATCH] Fix BUG macro Rusty Russell
2002-05-16 11:21 ` Hugh Dickins
2002-05-17 0:31 ` Rusty Russell
2002-05-17 7:56 ` Hugh Dickins
2002-05-17 9:43 ` Rusty Russell
2002-05-17 11:47 ` Hugh Dickins
2002-05-17 12:02 ` Andreas Schwab
2002-05-17 12:46 ` Rusty Russell
2002-05-17 13:19 ` Hugh Dickins
2002-05-16 16:27 ` Ghozlane Toumi
2002-05-17 2:25 ` Rusty Russell
2002-05-17 2:41 ` Andrew Morton
2002-05-17 4:25 ` Rusty Russell
2002-05-17 4:50 ` Andrew Morton
2002-05-17 5:20 ` Rusty Russell [this message]
2002-05-17 6:44 ` Andrew Morton
2002-05-17 9:39 ` Rusty Russell
2002-05-17 16:14 ` Kai Germaschewski
2002-05-17 18:41 ` Andrew Morton
2002-05-17 22:35 ` Stevie O
2002-05-17 23:09 ` Kai Germaschewski
2002-05-18 6:28 ` Linus Torvalds
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=E178aAR-00020W-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=ghoz@sympatico.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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