From: Cao Qinxiang <caoqinxiang@gmail.com>
To: cygwin@cygwin.com, Achim Gratz <Stromeko@nexgo.de>,
Brian Inglis <Brian.Inglis@systematicsw.ab.ca>
Subject: Re: flexdll error: cannot relocate RELOC_REL32
Date: Fri, 06 Mar 2020 19:03:00 -0000 [thread overview]
Message-ID: <CAKAoUean1OPqX=ChmbB731b+h3NONRFrmwiXKrQ-Jaj6dbpSaQ@mail.gmail.com> (raw)
In-Reply-To: <87blpepsqp.fsf@Rainer.invalid>
Dear Achim and Brian,
Thank you very much for you suggestions. And as Achim guessed, I was trying
to build a ocaml based library: Menhir. Currently, my problem is still not
solved.
If I try:
-------
echo /usr/lib/ocaml/stublibs/ > /var/lib/rebase/dynpath.d/ocaml
-------
and then rebase, I get the following error:
-------
Fatal error: cannot load shared library dllunix
Reason: flexdll error: cannot relocate RELOC_REL32, target is too far:
0xfffffffc02088b5f 0x2088b5f
-------
I also tried to check whether BLODA is involved. I use
-------
export CYGWIN=detect_bloda
-------
But when I compile menhir, I get the same error message about fork() and
dllunix.so, but no bloda is detected. Also, if I try to search
"dllunix.so", I find the following instances:
-------
/lib/ocaml/stublibs/dllunix.so
/usr/lib/ocaml/stublibs/dllunix.so
/proc/sys/KernelObjects/HighCommitCondition/dllunix.so
/proc/sys/KernelObjects/HighMemoryCondition/dllunix.so
/proc/sys/KernelObjects/LowCommitCondition/dllunix.so
/proc/sys/KernelObjects/LowMemoryCondition/dllunix.so
/proc/sys/KernelObjects/MaximumCommitCondition/dllunix.so
/proc/sys/KernelObjects/MemoryErrors/dllunix.so
/proc/sys/KernelObjects/PhysicalMemoryChange/dllunix.so
--------
Is there a duplication there? I don't think I manually add any of these.
Best,
Qinxiang Cao
Shanghai Jiao Tong University, John Hopcroft Center
Room 1110-2, SJTUSE Building
800 Dongchuan Road, Shanghai, China, 200240
On Tue, Mar 3, 2020 at 1:33 AM Achim Gratz <Stromeko@nexgo.de> wrote:
> Brian Inglis writes:
> > Try what's documented in /usr/share/doc/Cygwin/_autorebase.README for
> DLLs under
> > non-standard system paths:
>
> …which by some extension means you shouldn't add system paths.
>
> > create a file /var/lib/rebase/dynpath.d/ocaml containing your .so
> directory path
> > /usr/lib/ocaml/stublibs/:
>
> Don't. The OCaml stublibs must not be rebased.
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> SD adaptation for Waldorf rackAttack V1.04R1:
> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
>
> --
> 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
>
>
--
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:[~2020-03-06 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 18:35 Cao Qinxiang
2020-03-02 7:58 ` Brian Inglis
2020-03-02 13:19 ` Cao Qinxiang
2020-03-02 7:58 ` Brian Inglis
[not found] ` <CAKAoUeasRTycj61MOn6KWWUhhc_3COrQ4-WcoyJKcJZV4HHqRA@mail.gmail.com>
2020-03-02 16:45 ` Brian Inglis
2020-03-02 17:32 ` Achim Gratz
2020-03-06 19:03 ` Cao Qinxiang [this message]
2020-03-02 17:16 ` Achim Gratz
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='CAKAoUean1OPqX=ChmbB731b+h3NONRFrmwiXKrQ-Jaj6dbpSaQ@mail.gmail.com' \
--to=caoqinxiang@gmail.com \
--cc=Brian.Inglis@systematicsw.ab.ca \
--cc=Stromeko@nexgo.de \
--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).