From: Jack <ostroffjh@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Notmuch mail indexer - talloc requirement?
Date: Tue, 14 Jun 2016 19:41:00 -0000 [thread overview]
Message-ID: <W3zljx2SBdX+ysyfsDYE8Z@9sDqWMiHGJUVCTETfrgws> (raw)
In-Reply-To: <loom.20160614T103928-331@post.gmane.org> (from vdplas@gmail.com on Tue Jun 14 04:44:13 2016)
On 2016.06.14 04:44, Corne Plas wrote:
> Jack Ostroff <ostroffjh <at> users.sourceforge.net> writes:
>> I realize this is a bit over a year old, but I'm in exactly the same
>> situation. 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.
> What exactly did you do 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'? I'll still trying to 'make' talloc,
> but still get the error 'cannot find -ltalloc'.
>
Starting from the main directory where the the tarball has been
expanded, "cd bin/defaults" then "ln -s cygtalloc_2.dll talloc.dll" and
"ln -s cygtalloc_2.dll cygtalloc.dll" and the equivalent two for the
other dll. I did this from a cygwin shell in mintty. (I don't have
that laptop booted up right now, so this is from memory. My desktop is
Linux, so I can't confirm from here.)
Jack
--
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
prev parent reply other threads:[~2016-06-14 16:14 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
2016-06-14 16:14 ` Corne Plas
2016-06-14 19:41 ` Jack [this message]
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=W3zljx2SBdX+ysyfsDYE8Z@9sDqWMiHGJUVCTETfrgws \
--to=ostroffjh@users.sourceforge.net \
--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).