From: Nathan Thern <nthern@gmail.com>
To: cygwin@cygwin.com
Subject: Re: New (to me) undefined symbol issue when linking
Date: Mon, 10 Oct 2011 14:06:00 -0000 [thread overview]
Message-ID: <CALEg2uoDhXmXiN1QHMcxa+YPPZkmCKY6nb3M=qBHVuK+VPTR2g@mail.gmail.com> (raw)
In-Reply-To: <1317922069.7236.5.camel@YAAKOV04>
On Thu, Oct 6, 2011 at 12:27 PM, Yaakov (Cygwin/X)
<yselkowitz@users.sourceforge.net> wrote:
> It is a known issue that the testsuite does not build with the latest
> orc:
OK, I'll revert to your orc & try from there.
> That being said, libschroedinger1.0 and liborc0.4 are already available
> in Ports.
Yep. Thanks for those, since they were my starting point. I'm trying
to build ffmpeg-0.8.5 & it failed on libschroedinger1.0-1.0.5 with an
undeclared identifier. I figured maybe the latest libschroedinger
would clear that up.
NT
--
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:[~2011-10-10 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 15:18 Nathan Thern
2011-10-06 17:28 ` Yaakov (Cygwin/X)
2011-10-10 14:06 ` Nathan Thern [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='CALEg2uoDhXmXiN1QHMcxa+YPPZkmCKY6nb3M=qBHVuK+VPTR2g@mail.gmail.com' \
--to=nthern@gmail.com \
--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).