From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] release: 1.0.1: Checking installation dependencies
Date: Wed, 01 Jul 2015 17:10:15 +0200 [thread overview]
Message-ID: <559402D7.7020203@users.sourceforge.net> (raw)
In-Reply-To: <5593A5BE.7090308@gmail.com>
> The pattern lib64 is not used at all in my version of coccinelle's source code
How do you think about to recheck make files and related build scripts?
> and when I installed coccinelle on openSUSE it did end up in lib rather than lib64.
Which run time environment did you try out for this software installation test?
> Do any of you have an idea why coccinelle was installed in lib64?
Yes, in principle. ;-)
How do you distinguish 64 bit systems nowadays?
Regards,
Markus
next prev parent reply other threads:[~2015-07-01 15:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 13:57 [Cocci] new release: 1.0.1 Julia Lawall
2015-06-19 18:20 ` [Cocci] release: 1.0.1: Checking installation dependencies SF Markus Elfring
2015-06-19 19:13 ` Quentin Lambert
2015-06-20 8:25 ` SF Markus Elfring
2015-06-20 9:15 ` SF Markus Elfring
2015-06-22 13:41 ` Quentin Lambert
2015-06-22 14:17 ` SF Markus Elfring
2015-06-23 9:34 ` Quentin Lambert
2015-06-23 9:57 ` SF Markus Elfring
2015-06-23 17:28 ` Luis R. Rodriguez
2015-07-01 8:33 ` Quentin Lambert
2015-07-01 15:10 ` SF Markus Elfring [this message]
2015-07-02 6:08 ` Julia Lawall
2015-07-02 7:23 ` SF Markus Elfring
2015-07-02 7:35 ` Julia Lawall
2015-07-02 8:05 ` SF Markus Elfring
2015-07-02 8:11 ` Julia Lawall
2015-07-02 8:38 ` SF Markus Elfring
2015-07-02 9:06 ` Quentin Lambert
2015-07-01 19:10 ` SF Markus Elfring
2015-06-24 13:41 ` [Cocci] new release: 1.0.1 Nicholas Mc Guire
2015-06-24 14:06 ` Julia Lawall
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=559402D7.7020203@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.