From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: unison-2.48 build fails with latest ocaml and flexdll (attn: Achim)
Date: Mon, 03 Apr 2017 17:12:00 -0000 [thread overview]
Message-ID: <otv4echi6209us46mheullq71ceu21hp2s@4ax.com> (raw)
In-Reply-To: <841a950b-57dd-337f-4eb9-f76f053f0c06@cygwin.com>
> > Then I got a different build error, but
> > I'll ask on the unison list about that.
>
> Is 2.49 a stable version? It seems neither Fedora nor Debian have
> packaged it.
Hm, you're right. I thought it was the latest beta release, but that's
2.48. Anyway, no need to worry about it here.
> > The build of orpie also failed, but for a different reason. It needed
> > ocaml-camlp4, but when I installed that and tried again I got
> >
> > ocamlopt.opt -c -pp camlp4o -I ./curses -I ./gsl -I ./units -thread
> > curses_assist.ml
> > >> Fatal error: OCaml and preprocessor have incompatible versions
>
> Oops, it seems there were some old curr:/prev: tags on ocaml-camlp4. I
> removed those, so please try again with 4.04+1-1.
Build gets farther now, but fails later on complaining about caml__frame:
cd gsl && ocamlc.opt -ccopt "-I/usr/include -I/usr/include/ncurses -ggdb
-O2 -pipe -Wimplicit-function-d
eclaration
-fdebug-prefix-map=/home/ASchulma/dev/cygwin/orpie/orpie-1.5.2-2.x86_64/build=/usr/src/debug/
orpie-1.5.2-2
-fdebug-prefix-map=/home/ASchulma/dev/cygwin/orpie/orpie-1.5.2-2.x86_64/src/orpie-1.5.2=/usr/src/debug/orpie-1.5.2-2
-DHAVE_INLINE -DHAVE_FENV -g -O2" -c mlgsl_matrix_double.c
ml_curses.c:1:0: warning: -fPIC ignored for target (all code is position
independent)
#include <caml/mlvalues.h>
^
In file included from mlgsl_error.c:9:0:
mlgsl_error.c: In function Âml_gsl_raise_exnÂ:
/usr/lib/ocaml/caml/memory.h:236:12: error: Âcaml__frame undeclared (first
use in this function)
(void) caml__frame, \
^
/usr/lib/ocaml/caml/memory.h:309:3: note: in expansion of macro
ÂCAMLxparam2Â
CAMLxparam2 (x, y)
^
This isn't actually a problem now, I was only using orpie as a test. Orpie
hasn't been updated in several years, and the source site has gone dark. So
I may never actually need to build it again. If I do, then I'll have to
solve this.
Thanks for maintaining all the ocaml packages. I see BTW that you added
ocaml-lablgtk2. Some time I'll get back to trying to package Unison with
the GTK2 GUI.
Andrew
next prev parent reply other threads:[~2017-04-03 17:12 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
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 [this message]
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=otv4echi6209us46mheullq71ceu21hp2s@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).