public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin-apps@cygwin.com
Subject: Re: unison-2.48 build fails with latest ocaml and flexdll (ping: Yaakov, Damien)
Date: Wed, 27 Apr 2016 11:16:00 -0000	[thread overview]
Message-ID: <loom.20160427T131022-915@post.gmane.org> (raw)
In-Reply-To: <p601ibd449l7qe7euo3u2uvbqjops166ir@4ax.com>

Andrew Schulman <schulman.andrew@...> writes:
> I'm not sure if you meant that as diagnosis or solution. It doesn't seem
like a
> solution.  Changing the image base of my compiles seems like an extraordinary
> measure.  Unison has always built just fine OOTB before.

Well, then just manually rebase unixdll.so (whatever that is for) to some
address that doesn't produce that error (and is not currently used in your
process map).  THat would at least get you over the hump of the build not
working.


Regards,
Achim.

  reply	other threads:[~2016-04-27 11:16 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 [this message]
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
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=loom.20160427T131022-915@post.gmane.org \
    --to=stromeko@nexgo.de \
    --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).