paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Build Failure on OS X Yosemite


From: Gautier Hattenberger
Subject: Re: [Paparazzi-devel] Build Failure on OS X Yosemite
Date: Wed, 12 Nov 2014 17:25:43 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.8.1

Hi,

So, it appears that the error comes from a change in the API of lablgtk (and probably Gtk itself). A parameter that was previously an int32 (in version 2.16.0 and below) has now the type Gdk.native_window (in version 2.18.x). Unbuntu only package 2.16.0, but opam install by default the latest version 2.18.3. You can still get an older version with opam (opam install -v lablgtk.2.16.0, maybe remove the 2.18.3 version first). It is really annoying to deal with this kind of stuff in ocaml, but I still need to make something for this because we'll face this problem in Unbuntu one day or another.

Gautier

Le 07/11/2014 10:48, liangchao a écrit :
Hi, Wangyeee:

On Ubuntu 14.04, I could build successfully. But after I've installed opam
manually, the same error as yours have raised.

OC gcs.ml
findlib: [WARNING] Interface glibIvy.cmi occurs in several directories:
/Users/wang/.opam/system/lib/glibivy, /opt/local/lib/ocaml
findlib: [WARNING] Interface ivy.cmi occurs in several directories:
/Users/wang/.opam/system/lib/glibivy, /opt/local/lib/ocaml
File "gcs.ml", line 632, characters 23-29:
Error: This expression has type int32 but an expression was expected of type
          Gdk.native_window
make: *** [gcs.cmo] Error 2

After roll back the environment variables and remove the opam, it could be
build again.




--
View this message in context: 
http://lists.paparazziuav.org/Build-Failure-on-OS-X-Yosemite-tp16302p16362.html
Sent from the paparazzi-devel mailing list archive at Nabble.com.

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel




reply via email to

[Prev in Thread] Current Thread [Next in Thread]