public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: unison-2.48 build fails with latest ocaml and flexdll (ping: Yaakov, Damien)
Date: Fri, 24 Feb 2017 18:15:00 -0000	[thread overview]
Message-ID: <5mt0bcpirrh22jobp0qtm5q0hsfqqncjt8@4ax.com> (raw)
In-Reply-To: <2169ibt34ifh3cr6s63bovbnb3ed485lj1@4ax.com>

> > A bald xpdf run failed with...
> > Cygwin runtime failure: /usr/bin/xpdf.exe: Invalid relocation.  Offset 
> > 0x2fb02bad9 at address 0x100494523 doesn't fit into 32 bits
> > I rebased /usr/bin/cygXt-6.dll from 0x0003fb480000 down to 0x0000fb480000, i.e. 
> > just turn the first 3 in the address to 0, and that allowed xpdf to run.
> 
> So I tried this, moving dllunix.so from 0x3e6440000 down to 0xe6440000:
> 
> $ rebase -i /usr/lib/ocaml/stublibs/dllunix.so
> /usr/lib/ocaml/stublibs/dllunix.so        base 0x0003e6440000 size 0x0004b000
> 
> $ rebase -b 0xe6440000 /usr/lib/ocaml/stublibs/dllunix.so
> 
> $ rebase -i /usr/lib/ocaml/stublibs/dllunix.so
> /usr/lib/ocaml/stublibs/dllunix.so        base 0x0000e6440000 size 0x0004b000
> 
> The build still failed, so I moved it down further, to 0x06440000. After that
> the build still failed but on a different DLL,
> /usr/lib/ocaml/stublibs/dllcamlstr.so.  So I rebased that one too, down to
> 0x06510000.  And finally the build succeeded!  (Well, it still failed, but in a
> source code problem, not a DLL problem.)

So to follow up on this old thread: The commands to make ocaml work again
in x86_64 are

rebase -b 0x06440000 /usr/lib/ocaml/stublibs/dllunix.so
rebase -b 0x06510000 /usr/lib/ocaml/stublibs/dllcamlstr.so

> Damien: OCaml is broken OOTB in x86_64. dllunix.so and dllcamlstr.so need to be
> rebased before it will work.

This is still true today. The above commands will probably have to be rerun
each time you use ocaml, since updating packages usually runs rebaseall
which undoes the above.

Andrew

  reply	other threads:[~2017-02-24 18:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 19:17 unison-2.48 build fails with latest ocaml and flexdll Andrew Schulman
2016-04-26 19:47 ` unison-2.48 build fails with latest ocaml and flexdll (ping: Yaakov, Damien) Andrew Schulman
2016-04-26 20:16   ` Achim Gratz
2016-04-27  9:16     ` Andrew Schulman
2016-04-27 11:16       ` Achim Gratz
2016-04-28  8:03   ` Marco Atzeri
2016-04-29 16:03     ` Andrew Schulman
2016-04-29 19:32       ` Mark Geisert
2016-04-29 19:43         ` Mark Geisert
2016-04-30 11:54         ` Andrew Schulman
2017-02-24 18:15           ` Andrew Schulman [this message]
2017-03-27 21:50             ` Yaakov Selkowitz
2017-03-31 17:00               ` Andrew Schulman
2017-04-03  2:23                 ` unison-2.48 build fails with latest ocaml and flexdll (attn: Achim) Yaakov Selkowitz
2017-04-03  6:23                   ` Achim Gratz
2017-04-08 17:42                     ` Achim Gratz
2017-04-03 17:12                   ` Andrew Schulman
2017-04-03 17:23                     ` Yaakov Selkowitz

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=5mt0bcpirrh22jobp0qtm5q0hsfqqncjt8@4ax.com \
    --to=schulman.andrew@epa.gov \
    --cc=cygwin-apps@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).