Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: alexandre.montplaisir@gmail.com (Alexandre Montplaisir)
Subject: [lttng-dev] [lttng-tools RFC PATCH] Add target arch and paths to the configure output
Date: Wed, 30 Nov 2011 17:19:02 -0500	[thread overview]
Message-ID: <1322691542-24888-1-git-send-email-alexandre.montplaisir@gmail.com> (raw)

The two eval's are needed to correctly expand the variables in the
default path. Anyone know of a cleaner way to achieve this?

"RFC" to also discuss the following:
- Should we also print the information about the $bindir and $libdir
  this current build with install into?

- Right now to cross-build a 32-bit consumer on a 64-bit system and
  vice versa, you have to specify CFLAGS=-m32  or -m64. Would it be
  worth it to create a --with-enable-32bit/--with-enable-64bit option
  too? It would be a bit redundant, but the options would be more
  uniform. Mesa, for example, has such a thing.

Signed-off-by: Alexandre Montplaisir <alexandre.montplaisir at gmail.com>
---
 configure.ac |   48 +++++++++++++++++++++++++++++++++++++++++++++---
 1 files changed, 45 insertions(+), 3 deletions(-)

diff --git a/configure.ac b/configure.ac
index ba5f7bd..2708e21 100644
--- a/configure.ac
+++ b/configure.ac
@@ -147,18 +147,60 @@ AC_CONFIG_FILES([
 
 AC_OUTPUT
 
+#
 # Mini-report on what will be built
-AS_ECHO("")
-
+#
+AS_ECHO()
+
+# Target architecture we're building for
+target_arch=$host_cpu
+[
+for f in $CFLAGS; do
+        if test $f = "-m32"; then
+        	target_arch="32-bit"
+        elif test $f = "-m64"; then
+        	target_arch="64-bit"
+        fi
+done
+]
+AS_ECHO_N("Target architecture: ")
+AS_ECHO($target_arch)
+
+# LTTng-UST enabled/disabled
 AS_ECHO_N("Lttng-UST support: ")
 AS_IF([test "x$lttng_ust_support" = "xyes"], [AS_ECHO("Enabled")],
 	[AS_ECHO("Disabled")]
 )
 
+# Do we build only the consumerd, or everything
 AS_IF([test "x$consumerd_only" = "xyes"],
 	[AS_ECHO("Only the consumerd daemon will be built.")],
 	[AS_ECHO("All binaries will be built.")]
 )
 
-AS_ECHO("")
+
+
+# If we build the sessiond, print the paths it will use
+AS_IF([test "x$consumerd_only" = "xno"],[
+AS_ECHO()
+AS_ECHO("The sessiond daemon will look in the following directories: ")
+AS_ECHO_N("32-bit consumerd executable in: ")
+AS_IF([test "$CONSUMERD32_PATH" = ""], [AS_ECHO("`eval eval echo $bindir`")],
+	[AS_ECHO("$CONSUMERD32_PATH")]
+)
+AS_ECHO_N("32-bit consumer libraries in: ")
+AS_IF([test "$CONSUMERD32_LIBDIR" = ""], [AS_ECHO("`eval eval echo $libdir`")],
+	[AS_ECHO("$CONSUMERD32_LIBDIR")]
+)
+AS_ECHO_N("64-bit consumerd executable in: ")
+AS_IF([test "$CONSUMERD64_PATH" = ""], [AS_ECHO("`eval eval echo $bindir`")],
+	[AS_ECHO("$CONSUMERD64_PATH")]
+)
+AS_ECHO_N("64-bit consumer libraries in: ")
+AS_IF([test "$CONSUMERD64_LIBDIR" = ""], [AS_ECHO("`eval eval echo $libdir`")],
+	[AS_ECHO("$CONSUMERD64_LIBDIR")]
+)],
+[])  #endif
+
+AS_ECHO()
 
-- 
1.7.7.3




                 reply	other threads:[~2011-11-30 22:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1322691542-24888-1-git-send-email-alexandre.montplaisir@gmail.com \
    --to=alexandre.montplaisir@gmail.com \
    /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