Util-Linux package development
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Karel Zak <kzak@redhat.com>
Cc: Ruediger Meier <sweet_f_a@gmx.de>, util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.29-rc2
Date: Mon, 12 Dec 2016 13:27:35 -0500	[thread overview]
Message-ID: <20161212182735.GQ10558@vapier.lan> (raw)
In-Reply-To: <20161212142834.jnspem6oeqqbly4g@ws.net.home>

[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]

On 12 Dec 2016 15:28, Karel Zak wrote:
> I have add one AC_IF and PKG_CHECK_MODULES to our UL_NCURSES_CHECK to
> prefer pkg-config and fallback to ncurses-config. It's trivial fix and
> it seems it works as expected.

thanks

i'd also note that the current logic isn't the preferred method for
finding tools like this.  the code looks like:
  if AC_RUN_LOG([suffix[]6-config --version >/dev/null]); then

which means it runs xxx6-config directly.  in autotools, you want to:
	AC_CHECK_TOOL([NCURSES_CONFIG], [ncurses-config])
this will make it search for $host-ncurses-config first, and when
cross-compiling, it'll warn if it falls back to ncurses-config.  it
also means builders can set $NCURSES_CONFIG to whatever weird path
they want to.

based on how the current code is written, it'll be a little more
difficult to integrate.  you'd have to use like m4_translit.
untested:
	m4_define([SUFFIX], m4_translit($1, [a-z], [A-Z]))
	...
	AC_CHECK_TOOL(SUFFIX[]6_CONFIG, suffix[]6-config)
	if AC_RUN_LOG($SUFFIX[]6_CONFIG --version ....
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-12-12 18:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 13:25 [ANNOUNCE] util-linux v2.29-rc2 Karel Zak
2016-10-20  6:03 ` Ruediger Meier
2016-10-20  9:17   ` Karel Zak
2016-10-20 10:25     ` Ruediger Meier
2016-10-20 11:00       ` Karel Zak
2016-10-20 11:34         ` Ruediger Meier
2016-10-20 15:19           ` Karel Zak
2016-10-20 16:28             ` Ruediger Meier
2016-10-20 16:40               ` Karel Zak
2016-10-20 17:08                 ` Ruediger Meier
2016-10-21 14:44                   ` Karel Zak
2016-10-21 15:03                     ` Ruediger Meier
2016-10-20 19:20             ` Ruediger Meier
2016-12-10 17:15             ` Mike Frysinger
2016-12-12 10:29               ` Karel Zak
2016-12-12 14:31                 ` Ruediger Meier
2016-12-12 14:01               ` Ruediger Meier
2016-12-12 14:28                 ` Karel Zak
2016-12-12 18:27                   ` Mike Frysinger [this message]
2016-12-13 11:44                     ` Karel Zak
2016-12-12 17:52                 ` Mike Frysinger
2016-10-20 17:11 ` Ruediger Meier

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=20161212182735.GQ10558@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=kzak@redhat.com \
    --cc=sweet_f_a@gmx.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