unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>, notmuch@notmuchmail.org
Subject: Re: notmuch release 0.20.2 now available
Date: Tue, 30 Jun 2015 19:02:52 +0200	[thread overview]
Message-ID: <87r3otjfib.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <20150630084018.GO24926@chitra.no-ip.org>

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

>
> Yes, I have looked at what the official packages[1] do, I do exactly the
> same[2].  Essentially the spec file does the following:
>
>   pushd bindings/ruby
>       ruby extconf.rb --vendor --with-cflags="%{optflags}"
>       make %{?_smp_mflags}
>   popd

I think the problem is contained in the original message. Since we want
to create a shared library "notmuch.so" for ruby to import, we need to
compile the C files in bindings/ruby with -fPIC.

I don't know if this is Debian specific, or ruby version specific, but
on my Debian Jessie machine with ruby 2.1, the generated Makefile
bindings/ruby/Makefile has

CFLAGS   = $(CCDLFLAGS) -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -fPIC $(ARCH_FLAG)

in it

even when invoked outside the notmuch build system; e.g.

% cd bindings/ruby && ruby extconf.rb

I guess the first step is to see if the -fPIC flag is also there on
Fedora, and if not, why not. If I look at the builds for 0.19 [1]
it seems it is. But notice there it is not required to pass it in to "--with-cflags"

d

[1] https://kojipkgs.fedoraproject.org/packages/notmuch/0.19/1.fc21/data/logs/x86_64/build.log
    - I couldn't find x86_64 build logs for 0.20  

  reply	other threads:[~2015-06-30 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  5:24 notmuch release 0.20.2 now available David Bremner
2015-06-30  6:39 ` Suvayu Ali
2015-06-30  7:34   ` David Bremner
2015-06-30  8:40     ` Suvayu Ali
2015-06-30 17:02       ` David Bremner [this message]
2015-07-06 14:04         ` Suvayu Ali

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=87r3otjfib.fsf@maritornes.cs.unb.ca \
    --to=david@tethera.net \
    --cc=fatkasuvayu+linux@gmail.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).