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: Mon, 18 Mar 2013 10:50:43 +0100 [thread overview]
Message-ID: <5146E373.8090702@users.sourceforge.net> (raw)
In-Reply-To: <CANrVCd2jbGE2X+C6K9s=VanN_CquDp98f2Ne6fYOBAJt+nU8Yg@mail.gmail.com>
> Unlikely, unless there is a clear need to do so.
I wonder why you do not see the need for corrections in your current build
specification and corresponding configuration scripts so far.
https://github.com/coccinelle/coccinelle/blob/abad11c5570b7b9bbae5ff92b3050cf68fe3fd14/configure.ac
I recommend adjustments for places like the following.
1. A "working directory" should not be referenced by the macro call
'AC_SUBST([COCCI_SRCDIR], ["$(pwd)"])'.
2. I find it strange that OCaml source files are passed in the macro call
'AC_CONFIG_FILES([...])'.
http://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Configuration-Files.html
3. How do you think about to rename the extension for the "top level Makefile"
to ".mk"?
4. How would you like to fix the following error message?
elfring at Sonne:~/Projekte/Coccinelle/Bau> LANG=C make -j6 -f Makefile.config
make: *** No targets. Stop.
5. I find that your "Makefile.am" files became inappropriate.
- outdated comments
- Which subdirectories should be used?
http://www.gnu.org/software/automake/manual/html_node/Conditional-Subdirectories.html
- Which source files should be assigned to the variable "spatch_SOURCES"?
http://www.gnu.org/software/automake/manual/html_node/Program-Sources.html
- When will the OCaml compiler and linker be called there?
Regards,
Markus
next prev parent reply other threads:[~2013-03-18 9:50 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
2013-03-16 20:07 ` SF Markus Elfring
2013-03-17 12:18 ` Arie Middelkoop
2013-03-18 9:50 ` SF Markus Elfring [this message]
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=5146E373.8090702@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