From: Justus Winter <4winter@informatik.uni-hamburg.de>
To: David Bremner <david@tethera.net>,
Jameson Graef Rollins <jrollins@finestructure.net>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: Ali Polatel <alip@exherbo.org>, notmuch@notmuchmail.org
Subject: Re: Can't compile notmuch-delivery
Date: Sat, 02 Jun 2012 00:49:09 +0200 [thread overview]
Message-ID: <20120601224909.24629.70500@thinkbox.jade-hamburg.de> (raw)
In-Reply-To: <87sjeezx7g.fsf@zancas.localnet>
Quoting David Bremner (2012-06-01 20:46:59)
> Jameson Graef Rollins <jrollins@finestructure.net> writes:
>
> > I think the zeroth-order thing we have to do then is to have the build
> > include the bindings as well. Then everyone will be able to see
> > immediately if the bindings are broken. I wouldn't even make it an
> > option, or make it an option to exclude building the bindings rather
> > than to include.
>
> OK, I can agree with this. Can we get some help from the bindings
> maintainers (or other interested people) in getting this working?
> Probably configure should detect/decide what bindings to build.
I like the idea. The thing with the python bindings is that building
them wont detect any errors, one has to import the module. Quick and
dirty python oneliner that doesn't even require installing the
bindings:
teythoon@thinkbox ~/repos/notmuch (git)-[master] % ( export LD_LIBRARY_PATH="$(pwd)/lib" ; cd bindings/python && python -c "import notmuch" )
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "notmuch/__init__.py", line 54, in <module>
from .database import Database
File "notmuch/database.py", line 46, in <module>
class Database(object):
File "notmuch/database.py", line 76, in Database
_get_directory = nmlib.notmuch_database_get_directory_b0rked
File "/usr/lib/python2.7/ctypes/__init__.py", line 378, in __getattr__
func = self.__getitem__(name)
File "/usr/lib/python2.7/ctypes/__init__.py", line 383, in __getitem__
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /home/teythoon/repos/notmuch/lib/libnotmuch.so.3: undefined symbol: notmuch_database_get_directory_b0rked
Justus
next prev parent reply other threads:[~2012-06-01 22:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 21:42 Can't compile notmuch-delivery Jostein Gogstad
2012-06-01 6:44 ` Tomi Ollila
2012-06-01 8:54 ` Felipe Contreras
2012-06-01 13:43 ` David Bremner
2012-06-01 17:01 ` Jameson Graef Rollins
2012-06-01 18:17 ` David Bremner
2012-06-01 18:28 ` Jameson Graef Rollins
2012-06-01 18:46 ` David Bremner
2012-06-01 22:49 ` Justus Winter [this message]
2012-06-02 2:14 ` David Bremner
2012-06-01 18:44 ` Felipe Contreras
2012-06-03 5:35 ` Adam Wolfe Gordon
2012-06-04 7:02 ` Jostein Gogstad
2012-06-04 7:07 ` Jostein Gogstad
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=20120601224909.24629.70500@thinkbox.jade-hamburg.de \
--to=4winter@informatik.uni-hamburg.de \
--cc=alip@exherbo.org \
--cc=david@tethera.net \
--cc=felipe.contreras@gmail.com \
--cc=jrollins@finestructure.net \
--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).