From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 12/14] 'tty' is from coreutils. So, handle it like all other coreutil tools
Date: Wed, 13 Jun 2012 17:23:41 +0200 [thread overview]
Message-ID: <1339601023-28824-13-git-send-email-jbe@pengutronix.de> (raw)
In-Reply-To: <1339601023-28824-1-git-send-email-jbe@pengutronix.de>
Signed-off-by: Juergen Beisert <jbe@pengutronix.de>
---
Makefile.in | 1 +
configure.ac | 7 +------
2 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/Makefile.in b/Makefile.in
index a5c5ad4..ebddea5 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -53,6 +53,7 @@ environment:
@ln -sf @GNU_install@ "$(abs_srcdir)/bin/install"
@ln -sf @GNU_stat@ "$(abs_srcdir)/bin/stat"
@ln -sf @GNU_mknod@ "$(abs_srcdir)/bin/mknod"
+ @ln -sf @GNU_tty@ "$(abs_srcdir)/bin/tty"
@ln -sf @GNU_tar@ "$(abs_srcdir)/bin/tar"
@ln -sf @GNU_find@ "$(abs_srcdir)/bin/find"
@ln -sf @PTXDIST_FILE@ "$(abs_srcdir)/bin/file"
diff --git a/configure.ac b/configure.ac
index 3d027b0..0715df0 100644
--- a/configure.ac
+++ b/configure.ac
@@ -149,6 +149,7 @@ GNU_TOOL(mknod, coreutils)
GNU_TOOL(dirname, coreutils)
GNU_TOOL(sort, coreutils)
GNU_TOOL(cat, coreutils)
+GNU_TOOL(tty, coreutils)
GNU_TOOL(readlink, coreutils)
GNU_TOOL(tar, tar)
GNU_TOOL(find, findutils)
@@ -288,12 +289,6 @@ if test -z "$MSGFMT"; then
AC_MSG_ERROR([gettext could not be found, please install])
fi
-dnl Check for tty
-AC_PATH_PROGS(TTY, tty,, $PATH)
-if test -z "$TTY"; then
- AC_MSG_ERROR([tty could not be found, please install])
-fi
-
dnl Check for gcc
AC_PATH_PROGS(GCC, gcc,, $PATH)
--
1.7.10
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-06-13 15:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 15:23 [ptxdist] Make PTXdist more OS independent Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 01/14] Core CPU count detection: do not rely on a fixed path to the 'sysctl' tool Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 02/14] Sed: prefer the GNU sed tool to do the configure job Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 03/14] Don't check for 'find' twice Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 04/14] Fix: use the 'find' utility which was already detected as the correct one Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 05/14] Don't check for 'install' twice Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 06/14] Don't check for 'readlink' twice Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 07/14] 'sort' is from coreutils. So, handle it like all other coreutil tools Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 08/14] 'dirname' " Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 09/14] 'cat' " Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 10/14] 'xargs' is from findutils. So, handle it like all other findutils tools Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 11/14] Find: ensure the 'file' command is always found Juergen Beisert
2012-06-13 15:23 ` Juergen Beisert [this message]
2012-06-13 15:23 ` [ptxdist] [PATCH 13/14] Bash: ensure the bash " Juergen Beisert
2012-06-13 15:23 ` [ptxdist] [PATCH 14/14] Make: ensure the GNU make " Juergen Beisert
2012-06-13 16:41 ` [ptxdist] Make PTXdist more OS independent Bernhard Walle
2012-06-13 17:22 ` Juergen Beisert
2012-06-13 17:26 ` Michael Olbrich
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=1339601023-28824-13-git-send-email-jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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