From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Cc: "Dr. Volker Zell" <dr.volker.zell@oracle.com>
Subject: Re: xpdf relocation error
Date: Sat, 14 May 2016 16:15:00 -0000 [thread overview]
Message-ID: <0aad0ae6-8e7d-8257-807c-cfda58f3ab7d@cornell.edu> (raw)
In-Reply-To: <1463223408.895157.20323.56786@mail.rambler.ru>
On 5/14/2016 6:56 AM, Jaakov Jaakov wrote:
> This rebasement does not seem to survive updates or reinstalls. I know
> that rebasement is difficult, but still, could you, perhaps, solve it in
> a more long-term way?
As was pointed out in the first post on this subject
(https://www.cygwin.com/ml/cygwin/2016-04/msg00365.html), simply
rebuilding from source with the current gcc seems to fix the problem.
I've also verified this.
I assume the xpdf maintainer, Volker Zell, will rebuild it when he has a
chance. In the meantime, are you able to build it yourself? If not, I
can provide a binary for you.
Ken
--
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
next prev parent reply other threads:[~2016-05-14 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 10:57 Jaakov Jaakov
2016-05-14 16:15 ` Ken Brown [this message]
2016-05-18 19:07 ` Dr. Volker Zell
-- strict thread matches above, loose matches on Subject: below --
2016-05-28 21:57 Jaakov Jaakov
2016-05-28 22:01 ` Ken Brown
2016-05-28 21:09 Jaakov Jaakov
2016-05-28 21:22 ` Ken Brown
[not found] <1462710225.11142.ezmlm@cygwin.com>
2016-05-13 20:23 ` Jaakov Jaakov
2016-05-06 14:50 Jaakov Jaakov
2016-05-07 4:22 ` Mark Geisert
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=0aad0ae6-8e7d-8257-807c-cfda58f3ab7d@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=dr.volker.zell@oracle.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).