From: Bart Bunting <bart.bunting@ursys.com.au>
To: notmuch@notmuchmail.org
Subject: muchsync and osx compile failure
Date: Mon, 09 Nov 2015 12:42:37 +1100 [thread overview]
Message-ID: <m2ziyoq776.fsf@ursys.com.au> (raw)
Hi,
Not sure if it is appropriate to post to this list with muchsync
questions but if not could someone let me know...
I'm trying to compile muchsync from git on OSX, I noted that the
announcement said it should compile cleanly.
I get the following when trying to compile:
make
g++ -DPACKAGE_NAME=\"muchsync\" -DPACKAGE_TARNAME=\"muchsync\" -DPACKAGE_VERSION=\"2\" -DPACKAGE_STRING=\"muchsync\ 2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"muchsync\" -DVERSION=\"2\" -DHAVE_OPENAT=1 -DHAVE_FDOPENDIR=1 -DST_MTIM=st_mtimespec -I. -I/usr/local/Cellar/xapian/1.2.19/include -g -O2 -std=c++11 -Wall -pthread -MT infinibuf.o -MD -MP -MF .deps/infinibuf.Tpo -c -o infinibuf.o infinibuf.cc
mv -f .deps/infinibuf.Tpo .deps/infinibuf.Po
g++ -DPACKAGE_NAME=\"muchsync\" -DPACKAGE_TARNAME=\"muchsync\" -DPACKAGE_VERSION=\"2\" -DPACKAGE_STRING=\"muchsync\ 2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"muchsync\" -DVERSION=\"2\" -DHAVE_OPENAT=1 -DHAVE_FDOPENDIR=1 -DST_MTIM=st_mtimespec -I. -I/usr/local/Cellar/xapian/1.2.19/include -g -O2 -std=c++11 -Wall -pthread -MT misc.o -MD -MP -MF .deps/misc.Tpo -c -o misc.o misc.cc
In file included from misc.cc:11:
./misc.h:10:10: fatal error: 'openssl/sha.h' file not found
#include <openssl/sha.h>
> ^
1 error generated.
make: *** [misc.o] Error 1
And if it is of use here is the configure:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking whether g++ supports C++11 features by default... no
checking whether g++ supports C++11 features with -std=c++11... yes
checking whether C++ compiler accepts ... yes
checking whether C++ compiler accepts -pthread... yes
checking for openat... yes
checking for fdopendir... yes
checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for sqlite3... yes
checking for libcrypto... yes
checking for xapian-config... /usr/local/bin/xapian-config
checking For st_mtim in struct stat... no
checking For st_mtimespec in struct stat... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
Thanks for any help.
Kind regards
Bart
--
Bart Bunting - URSYS
PH: 02 87452811
Mbl: 0409560005
next reply other threads:[~2015-11-09 1:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 1:42 Bart Bunting [this message]
2015-11-09 16:35 ` muchsync and osx compile failure J. Lewis Muir
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=m2ziyoq776.fsf@ursys.com.au \
--to=bart.bunting@ursys.com.au \
--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).