From: Karel Zak <kzak@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 1/2] conifigure: add a crosscompile path for scanf_cv_alloc_modifier
Date: Tue, 28 Feb 2012 15:12:26 +0100 [thread overview]
Message-ID: <20120228141226.GC22034@x2.net.home> (raw)
In-Reply-To: <1330103768-32139-1-git-send-email-bigeasy@linutronix.de>
On Fri, Feb 24, 2012 at 06:16:07PM +0100, Sebastian Andrzej Siewior wrote:
> This allows to building the package cross again. Since the return value
> is not used I guess there is little loss.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> configure.ac | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index d3b298c..c27e890 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -387,6 +387,8 @@ AC_CACHE_VAL([scanf_cv_alloc_modifier],
> [scanf_cv_alloc_modifier=as],
> [scanf_cv_alloc_modifier=no]
> )
> + ,
> + [scanf_cv_alloc_modifier=no]
> )
> )
Applied, thanks.
...but it means that you will compile the package without libmount.
Is it expected? In the next release fsck will depend on the library,
we have new mount and umount, ....
Is it really true that your glibc is without %as / %ms ?
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-02-28 14:12 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 ` Karel Zak [this message]
2012-02-29 21:31 ` [PATCH 1/2] conifigure: add a crosscompile path for scanf_cv_alloc_modifier Sebastian Andrzej Siewior
2012-03-20 8:18 ` Karel Zak
2012-03-30 19:49 ` Mike Frysinger
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=20120228141226.GC22034@x2.net.home \
--to=kzak@redhat.com \
--cc=bigeasy@linutronix.de \
--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