From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] 1.0.0-rc16: Further fine-tuning for the build system?
Date: Thu, 07 Mar 2013 18:07:43 +0100 [thread overview]
Message-ID: <5138C95F.8010608@users.sourceforge.net> (raw)
In-Reply-To: <CANrVCd3HS+i84W01R-pZv5B1jz_r9HJVjJfVh1OxN1mGMmxAuA@mail.gmail.com>
> Does it work as it is supposed to be?
It seems that the desired build configuration works also as expected on my
system with an out-of-source build after a small adjustment for a variable.
www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Build-Directories.html
diff --git a/configure.ac b/configure.ac
index 2f0f682..4905af0 100644
--- a/configure.ac
+++ b/configure.ac
@@ -8,7 +8,7 @@ AC_CONFIG_MACRO_DIR([setup])
AC_CONFIG_AUX_DIR([setup])
AC_SUBST([CONFIGURE_FLAGS], ["$*"])
AC_SUBST([COCCI_VERSION], ["$PACKAGE_VERSION"])
-AC_SUBST([COCCI_SRCDIR], ["$(pwd)"])
+AC_SUBST([COCCI_SRCDIR], ["$srcdir"])
AC_MSG_NOTICE([configuring coccinelle $COCCI_VERSION in $COCCI_SRCDIR])
AM_INIT_AUTOMAKE
I have got the impression that there are more update candidates to consider
since the macro call "AM_INIT_AUTOMAKE" was added.
https://github.com/coccinelle/coccinelle/blob/abad11c5570b7b9bbae5ff92b3050cf68fe3fd14/configure.ac#L13
- Would you like to drop the variable "COCCI_SRCDIR" eventually (because there
is a standard one available)?
- How do you think about to change comments in files like "Makefile.am"?
Regards,
Markus
next prev parent reply other threads:[~2013-03-07 17:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 21:02 [Cocci] 1.0.0-rc16: Further fine-tuning for the build system? SF Markus Elfring
2013-03-02 21:18 ` Julia Lawall
2013-03-04 11:35 ` SF Markus Elfring
2013-03-04 12:36 ` Julia Lawall
2013-03-04 12:37 ` Julia Lawall
2013-03-04 12:43 ` SF Markus Elfring
2013-03-04 12:48 ` Julia Lawall
2013-03-04 13:14 ` SF Markus Elfring
2013-03-04 13:54 ` SF Markus Elfring
2013-03-04 15:40 ` SF Markus Elfring
2013-03-04 15:47 ` Julia Lawall
2013-03-04 16:05 ` SF Markus Elfring
2013-03-05 8:36 ` Arie Middelkoop
2013-03-07 15:54 ` SF Markus Elfring
2013-03-07 16:27 ` Arie Middelkoop
2013-03-07 17:07 ` SF Markus Elfring [this message]
2013-03-16 20:07 ` SF Markus Elfring
2013-03-17 12:18 ` Arie Middelkoop
2013-03-18 9:50 ` SF Markus Elfring
2013-04-07 10:51 ` [Cocci] 1.0.0-rc17: " SF Markus Elfring
2013-04-07 11:05 ` Julia Lawall
2013-04-07 11:14 ` SF Markus Elfring
2013-04-07 11:20 ` Julia Lawall
2013-04-07 11:30 ` SF Markus Elfring
2013-04-07 11:43 ` Julia Lawall
2013-04-07 12:07 ` SF Markus Elfring
2013-04-07 12:11 ` Julia Lawall
2013-04-07 12:13 ` SF Markus Elfring
2013-04-26 8:14 ` [Cocci] 1.0.0-rc16: " Richard W.M. Jones
2013-04-26 9:10 ` SF Markus Elfring
2013-04-26 9:16 ` Richard W.M. Jones
2013-04-26 9:36 ` SF Markus Elfring
2013-04-26 9:52 ` Richard W.M. Jones
2013-04-26 10:15 ` SF Markus Elfring
2013-04-26 10:25 ` Julia Lawall
2013-04-26 11:03 ` Peter Senna Tschudin
2013-04-26 11:28 ` SF Markus Elfring
2013-04-29 9:52 ` [Cocci] 1.0.0-rc17: " SF Markus Elfring
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=5138C95F.8010608@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/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