From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Roland McGrath <roland@redhat.com>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: Re: [WARNING -mm] 2.6.18-rc2-mm1 build kills /dev/null!?
Date: Thu, 27 Jul 2006 13:22:15 +0200 [thread overview]
Message-ID: <20060727112215.GA25569@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <20060727101709.GB31920@rhlx01.fht-esslingen.de>
On Thu, Jul 27, 2006 at 12:17:09PM +0200, Andreas Mohr wrote:
> Hi,
>
> On Thu, Jul 27, 2006 at 12:11:28PM +0200, Andreas Mohr wrote:
> > Hello all,
> >
> > for some reason a 2.6.18-rc2-mm1 build seems to kill my /dev/null device!
>
> Replying to myself, this could easily be due to:
Yup, seems it is, see newly posted:
"Re: [PATCH] vDSO hash-style fix"
http://lkml.org/lkml/2006/7/27/83
| > +# ld-option
| > +# Usage: ldflags += $(call ld-option, -Wl$(comma)--hash-style=both)
| > +ld-option = $(shell if $(CC) $(1) \
| > + -nostdlib -o /dev/null -xc /dev/null \
| > + > /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi)
|
| This is not good. When I introduced something similar for lxdialog I
| received lots of reports about /dev/null becoming a regular file.
| ld does something strange with the output file when it fails.
|
| When re-done ld-option shall be accompanied by documentation in
| Documentation/makefiles.txt like cc-option.
Could we have a -mm hot-fix here?
Andreas Mohr
next prev parent reply other threads:[~2006-07-27 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 10:11 Andreas Mohr
2006-07-27 10:17 ` Andreas Mohr
2006-07-27 11:22 ` Andreas Mohr [this message]
2006-07-27 14:19 ` Michael Tokarev
2006-07-27 14:24 ` gmu 2k6
2006-07-27 14:24 ` gmu 2k6
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=20060727112215.GA25569@rhlx01.fht-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--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
all inboxes | Powered by JetHome®