From: Rob Landley <rob@landley.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix headers_install for x86-64 (now with less whitespace damage!)
Date: Tue, 26 Jun 2007 10:48:41 -0400 [thread overview]
Message-ID: <200706261048.41738.rob@landley.net> (raw)
In-Reply-To: <1182866629.8896.37.camel@pmac.infradead.org>
On Tuesday 26 June 2007 10:03:49 David Woodhouse wrote:
> On Tue, 2007-06-26 at 09:12 -0400, Rob Landley wrote:
> > Signed-off-by: Rob Landley <rob@landley.net>
> >
> > A bug in headers_install for ARCH=x86_64 yields an asm/ directory full
> > of files all of which are using the same #ifdef guard, "__ASM_STUB_" with
> > no postfix. So the second and later asm files #included in the same C
> > file (often through standard headers like ioctl.h) yields no symbols.
>
> Interesting. It works here with bash 3.2 -- I thought it was the _first_
> shell which expanded $FNAME and $STUBDEF inside the parentheses. Which
> shell are you using?
Stock Ubuntu 7.04 comes with /bin/sh pointing to the Dumb-Ass SHell. (Motto:
If it's not explicitly mentioned in posix, and we accidentally support it,
let us know so we can remove it!)
> Is it sufficient just to add the missing semicolon after FNAME=...?
Huh. Apparently, yes it is. (I thought I'd tried that and it hadn't worked,
but I just tried it again and it worked, so ok. It's before noon, don't
expect accuracy from me yet today...)
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
prev parent reply other threads:[~2007-06-26 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 13:12 Rob Landley
2007-06-26 14:03 ` David Woodhouse
2007-06-26 14:48 ` Rob Landley [this message]
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=200706261048.41738.rob@landley.net \
--to=rob@landley.net \
--cc=dwmw2@infradead.org \
--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
all inboxes | Powered by JetHome®