From: Mike Frysinger <vapier@gentoo.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH 1/2] conifigure: add a crosscompile path for scanf_cv_alloc_modifier
Date: Fri, 30 Mar 2012 15:49:37 -0400 [thread overview]
Message-ID: <201203301549.39151.vapier@gentoo.org> (raw)
In-Reply-To: <20120229213128.GA11628@linutronix.de>
[-- Attachment #1: Type: Text/Plain, Size: 781 bytes --]
On Wednesday 29 February 2012 16:31:28 Sebastian Andrzej Siewior wrote:
> My earlier assumption was that scanf_cv_alloc_modifier is unused. This
> is not true as pointed out by Karel since it used befoe checking for
> libmount. Argh. So instead saying no I add a test to check for glibc
> >= 2.7 which provides %m. As of uClibc v0.9.32-rc3 the situation looks
> the following:
the uClibc code you grepped for is printf("%m"), not scanf("%ms")
uClibc itself has a place holder for %as, but has never implemented it since
it conflicts with C99. and it hasn't gotten around to implementing the new %ms
which is specified by the latest POSIX spec.
be nice if this patch was in 2.21.1, but i guess that ship has sailed, and
there prob won't be a 2.21.2 ...
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-30 19:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 17:16 [PATCH 1/2] conifigure: add a crosscompile path for scanf_cv_alloc_modifier Sebastian Andrzej Siewior
2012-02-24 17:16 ` [PATCH 2/2] Add uuid to the linker flags if using built LIBBLKID Sebastian Andrzej Siewior
2012-02-28 14:35 ` Karel Zak
2012-02-29 21:38 ` Sebastian Andrzej Siewior
2012-02-28 14:12 ` [PATCH 1/2] conifigure: add a crosscompile path for scanf_cv_alloc_modifier Karel Zak
2012-02-29 21:31 ` Sebastian Andrzej Siewior
2012-03-20 8:18 ` Karel Zak
2012-03-30 19:49 ` Mike Frysinger [this message]
2012-03-30 20:52 ` Mike Frysinger
2012-04-02 7:14 ` Sebastian Andrzej Siewior
2012-04-02 19:00 ` Mike Frysinger
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=201203301549.39151.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=bigeasy@linutronix.de \
--cc=kzak@redhat.com \
--cc=util-linux@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