From: Jack Ostroff <ostroffjh@frontier.com>
To: cygwin@cygwin.com
Subject: Re: Notmuch mail indexer - talloc requirement?
Date: Sun, 12 Jun 2016 07:53:00 -0000 [thread overview]
Message-ID: <21f01060-238b-a2fe-37af-f9709cc20f14@frontier.com> (raw)
In-Reply-To: <7e7ae7e7-7729-c053-6866-e17c669c9bf5@tiscali.co.uk>
On 6/11/2016 7:01 PM, David Stacey wrote:
> On 11/06/16 19:55, Jack Ostroff wrote:
>> I was able to complete the talloc compile and install by going
>> into the bin/defaults directory and linking cygtalloc_2.dll to both
>> talloc.dll and cygtalloc.dll, and the same for cygpytalloc-util-2.dll.
>>
>> However, even then, when doing ./configure on notmuch I still get errors:
>>
>> /usr/include/xapian/version.h:28:2: error: #error The C++ ABI version of
>> compiler you are using does not match
>>
>> /usr/include/xapian/version.h:31:2: error: #error The Xapian library was
>> built with g++ 4.8.3
>> My current g++ is 5.3.0.
>
>
> Does this help?
>
> ./configure CXXFLAGS="-g -O2 -D_GLIBCXX_USE_CXX11_ABI=0"
>
> It should force the compiler to use to older ABI.
Oddly, no. With that line, I get "Unrecognized option: CXXFLAGS=-g -O2
-D_GLIBCXX_USE_CXX11_ABI=0". Passing it as an environment variable
seems to have no effect. (I thought I had recompiled xapian, which I
thought would have used the new ABI, but even that didn't seem to make
any difference.)
Other ideas?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-06-12 2:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 2:23 Joe Rochette
2015-03-19 8:51 ` Corinna Vinschen
2015-03-19 15:00 ` joefromct
2015-03-19 20:21 ` Corinna Vinschen
2015-03-19 22:22 ` Yaakov Selkowitz
2016-06-11 23:01 ` Jack Ostroff
2016-06-12 2:28 ` David Stacey
2016-06-12 6:00 ` Jack Ostroff
2016-06-12 7:53 ` Jack Ostroff [this message]
2016-06-14 16:14 ` Corne Plas
2016-06-14 19:41 ` Jack
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=21f01060-238b-a2fe-37af-f9709cc20f14@frontier.com \
--to=ostroffjh@frontier.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).