From: Scott Robinson <scott@quadhome.com>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Build and link against notmuch shared library
Date: Sun, 24 Jan 2010 19:00:04 -0600 [thread overview]
Message-ID: <1264381119-sup-9840@elise> (raw)
In-Reply-To: <1264272821-sup-5331@ben-laptop>
Excerpts from bgamari.foss's message of Sat Jan 23 12:58:42 -0600 2010:
> True, but I don't think that this means that we need to link the
> executable with a C++ compiler. I've tried linking with CC and it seems
> to succeed, so I don't think there should be a problem changing it.
>
Are you using "cc" or "gcc"?
Even when cc is an alias to gcc, there are different semantics. And "cc" vs.
"cpp" can be even more different on non-GCC compilers.
I wouldn't mess with it. :-)
next prev parent reply other threads:[~2010-01-25 1:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 20:07 libtool-less shared library building Ben Gamari
2010-01-20 20:07 ` [PATCH] Build and link against notmuch shared library Ben Gamari
2010-01-20 20:20 ` Mike Hommey
2010-01-20 20:18 ` libtool-less shared library building David Bremner
2010-01-20 20:35 ` [PATCH] Build and link against notmuch shared library Ben Gamari
2010-01-23 0:58 ` Felipe Contreras
2010-01-23 2:06 ` Ingmar Vanhassel
2010-01-23 18:58 ` bgamari.foss
2010-01-24 21:23 ` [PATCH] Notmuch " Ben Gamari
2010-01-24 21:23 ` [PATCH 1/2] Fix typo in message Ben Gamari
2010-01-24 21:23 ` [PATCH 2/2] Build and link against notmuch shared library Ben Gamari
2010-03-04 8:25 ` Sebastian Spaeth
2010-03-11 22:41 ` Ben Gamari
2010-03-12 15:04 ` Sebastian Spaeth
2010-01-25 1:00 ` Scott Robinson [this message]
2010-01-23 18:35 ` [PATCH] " Ben Gamari
-- strict thread matches above, loose matches on Subject: below --
2010-01-26 5:38 [PATCH] Add SWIG interface file Ben Gamari
2010-01-26 6:15 ` [PATCH] Build and link against notmuch shared library Ben Gamari
2010-03-11 22:37 Notmuch " Ben Gamari
2010-03-11 22:37 ` [PATCH] Build and link against notmuch " Ben Gamari
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1264381119-sup-9840@elise \
--to=scott@quadhome.com \
--cc=notmuch@notmuchmail.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).