David Bremner writes:
> David Bremner writes:
>
>> Because ruby generates a Makefile, we have to use recursive make.
>> Because mkmf.rb hardcodes the name Makefile, put our Makefile{.local}
>> in the parent directory.
>
> Pushed the first patch in the series. Let's see if anything breaks.
>
It
David Bremner da...@tethera.net writes:
David Bremner da...@tethera.net writes:
Because ruby generates a Makefile, we have to use recursive make.
Because mkmf.rb hardcodes the name Makefile, put our Makefile{.local}
in the parent directory.
Pushed the first patch in the series. Let's see
Jinwoo Lee writes:
> ld: unknown option: --no-undefined
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
I wonder if this the actual relevant error. Can you try with the next
two patches in the series?
id:1433142542-2307-3-git-send-email-david at
Jinwoo Lee writes:
>> I with configure has an option to skip the ruby-bindings build.
>
> `configure' seems to try to detect whether the ruby development tools
> are installed. It thinks I have them but I don't actually, and that's
> why my build fails. When I manually set 'HAVE_RUBY_DEV = 0'
On Sat, Jun 13, 2015 at 02:24 PM, Jinwoo Lee wrote:
> That error is from 'cd bindings/ruby && ruby extconf.rb --vendor' BTW.
The contents of mkmf.log are below. It shows a warning about
-L/usr/local/lib and I don't have the directory /usr/local/lib on my
machine. I'm not sure if that's the
That error is from 'cd bindings/ruby && ruby extconf.rb --vendor' BTW.
On Sat, Jun 13, 2015 at 02:11 PM, David Bremner wrote:
> Jinwoo Lee writes:
>
>>> I with configure has an option to skip the ruby-bindings build.
>>
>> `configure' seems to try to detect whether the ruby development tools
>> are installed. It thinks I have them but I don't actually, and that's
On Sat, Jun 13, 2015 at 01:46 PM, Jinwoo Lee wrote:
> On Sat, Jun 13, 2015 at 12:59 PM, Jinwoo Lee wrote:
>> This breaks Mac OS X. ruby-bindings depends on lib/libnotmuch.so but it
>> should be lib/libnotmuch.dylib on OS X.
>>
>> That makes `make' and `make install' fail.
>
> Even after I
On Sat, Jun 13, 2015 at 12:59 PM, Jinwoo Lee wrote:
> This breaks Mac OS X. ruby-bindings depends on lib/libnotmuch.so but it
> should be lib/libnotmuch.dylib on OS X.
>
> That makes `make' and `make install' fail.
Even after I update the dependency to lib/libnotmuch.dylib, building
This breaks Mac OS X. ruby-bindings depends on lib/libnotmuch.so but it
should be lib/libnotmuch.dylib on OS X.
That makes `make' and `make install' fail.
On Fri, Jun 12, 2015 at 11:37 PM, David Bremner wrote:
> David Bremner writes:
>
>> Because ruby generates a Makefile, we have to use
David Bremner writes:
> Because ruby generates a Makefile, we have to use recursive make.
> Because mkmf.rb hardcodes the name Makefile, put our Makefile{.local}
> in the parent directory.
Pushed the first patch in the series. Let's see if anything breaks.
d
Jinwoo Lee jinwo...@gmail.com writes:
ld: unknown option: --no-undefined
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
I wonder if this the actual relevant error. Can you try with the next
two patches in the series?
David Bremner da...@tethera.net writes:
Because ruby generates a Makefile, we have to use recursive make.
Because mkmf.rb hardcodes the name Makefile, put our Makefile{.local}
in the parent directory.
Pushed the first patch in the series. Let's see if anything breaks.
d
This breaks Mac OS X. ruby-bindings depends on lib/libnotmuch.so but it
should be lib/libnotmuch.dylib on OS X.
That makes `make' and `make install' fail.
On Fri, Jun 12, 2015 at 11:37 PM, David Bremner da...@tethera.net wrote:
David Bremner da...@tethera.net writes:
Because ruby generates a
On Sat, Jun 13, 2015 at 12:59 PM, Jinwoo Lee jinwo...@gmail.com wrote:
This breaks Mac OS X. ruby-bindings depends on lib/libnotmuch.so but it
should be lib/libnotmuch.dylib on OS X.
That makes `make' and `make install' fail.
Even after I update the dependency to lib/libnotmuch.dylib,
On Sat, Jun 13, 2015 at 01:46 PM, Jinwoo Lee jinwo...@gmail.com wrote:
On Sat, Jun 13, 2015 at 12:59 PM, Jinwoo Lee jinwo...@gmail.com wrote:
This breaks Mac OS X. ruby-bindings depends on lib/libnotmuch.so but it
should be lib/libnotmuch.dylib on OS X.
That makes `make' and `make install'
Jinwoo Lee jinwo...@gmail.com writes:
I with configure has an option to skip the ruby-bindings build.
`configure' seems to try to detect whether the ruby development tools
are installed. It thinks I have them but I don't actually, and that's
why my build fails. When I manually set
On Sat, Jun 13, 2015 at 02:11 PM, David Bremner da...@tethera.net wrote:
Jinwoo Lee jinwo...@gmail.com writes:
I with configure has an option to skip the ruby-bindings build.
`configure' seems to try to detect whether the ruby development tools
are installed. It thinks I have them but I
That error is from 'cd bindings/ruby ruby extconf.rb --vendor' BTW.
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
On Sat, Jun 13, 2015 at 02:24 PM, Jinwoo Lee jinwo...@gmail.com wrote:
That error is from 'cd bindings/ruby ruby extconf.rb --vendor' BTW.
The contents of mkmf.log are below. It shows a warning about
-L/usr/local/lib and I don't have the directory /usr/local/lib on my
machine. I'm not sure if
Because ruby generates a Makefile, we have to use recursive make.
Because mkmf.rb hardcodes the name Makefile, put our Makefile{.local}
in the parent directory.
---
Makefile.local | 2 +-
bindings/Makefile | 7 +++
bindings/Makefile.local | 19 +++
Because ruby generates a Makefile, we have to use recursive make.
Because mkmf.rb hardcodes the name Makefile, put our Makefile{.local}
in the parent directory.
---
Makefile.local | 2 +-
bindings/Makefile | 7 +++
bindings/Makefile.local | 19 +++
22 matches
Mail list logo
