Re: [Paparazzi-devel] OSX 10.9 install

[chrisrobson]

Hi Stephen,

Thanks for the helpful reply.  I’ve made some progress!

First I checked to make sure I was running the correct version of python, I was fairly sure I’d completed this step but redid it all the same:

...$ sudo port select --set python python27

Selecting 'python27' for 'python' succeeded. 'python27' is now active.

So I tried:

ocamlfind query lablgtk2

Which did return:

 /opt/local/lib/ocaml/site-lib/lablgtk2

I then looked at the list of dependancies, and reinstalled them in order.  This solved the problem with lablgtk2.

Now could then go into my paparazzi directory, and hit make, which seemed to work, but when trying to run paparazzi (I’m in the paparazzi directory and type ./paparazzi) I get this:

...$ ./paparazzi

Fatal error: exception Gtk.Error("GtkMain.init: initialization failed

ml_gtk_init: initialization failed”)  

I had a search for it, but couldn’t find any results for something similar, then found something talking about X11.  It was at this point that I realised that while the X11 icon appears in my application folder, it is in fact a download link to download it, and not intact the software itself…  After feeling a bit silly and downloading XQuartz, Paparazzi Centre loaded and I can run simulations with no problems :).  

I also noticed the paparazzi tools installer for the mavericks binary installation has appeared on the wiki. I might enjoy everything working for a little while before going back and trying it that way instead!

Cheers

Chris

On 26 Jan 2014, at 05:25, Stephen Dwyer <address@hidden> wrote:

Hi Chris,

I have been very busy lately with other things so unfortunately I have not had time to properly update the OS X section on the wiki.

Mavericks and Mountain Lion should both be working fine now, including full operation of Paparazzi Center launching agents (Thanks Esden!).

I just recently finished building a binary installer for Mavericks, but it hasn't been tested. I also think that setting up the environment from the binary installers is still broken (haven't had time to debug it, takes a long time to test changes). This is easily created by adding the right path and environment variable changes to your .profile and creating a python symlink to the paparazzi installed python. Need to put this on the wiki. I can upload it if you are interested in testing, but it will take a while.

Again, needs updating, but PyUSB should be a dependency of paparazzi-tools now, so no need to do that. You do need to make sure you are using the right python though. Use macports port select command to change the default python (need to use a symlink if using the binary installer).

The failed fetch just means the server holding the files for that port failed to respond in time. Trying to install again like you did is usually how you solve that.

For the lablgtk2 library, you can see if ocaml can find it with:

ocamlfind query lablgtk2

It should return: /opt/local/lib/ocaml/site-lib/lablgtk2

It is possible that ocaml and ocamlfind and some of the other ocaml libs got a bit messed up (hinted by the broken files/ports). This occasionally pops up with macports and is a real pain. I am not sure how to properly solve the problem. In the past I have had to uninstall all the ocaml related items (it gives a list of dependencies in what you posted) and reinstalling them in that order. It is annoying, and doesn't always work either. I do not have any more insight right now, maybe someone else does.

The reason for the interface occurring in several directories warning is because we have a symlink for most of these libraries to keep compatibility with Paparazzi before v5.0. It is harmless, just makes it look messy. I haven't determined how to disable that warning. There are also a couple other v4.0 compatibility things that are installed that don't need to be there if you are using v5.0 and above only.

Hopefully that helps. If you have any further problems, please feel free to post them. Your extra information you posted this time was useful.

Thanks,

-Stephen Dwyer

On Sat, Jan 25, 2014 at 12:33 PM, chrisrobson <address@hidden> wrote:

Hi everyone,

So a couple of months ago I tried installing paparazzi on OSX snow leopard, and ran into problems installing paparazzi tools.  I’m now trying on a different laptop with OSX 10.9 (Mavericks).  The first thing I tried to do with it was install the two bits of software that I’d previously installed with Macports:  Paparazzi and OpenCV. OpenCV installed ok, then I tried Paparazzi.

Below I’ve wrote out a step by step of what I’m doing, in the hope that it can be solved with your help.

I’ve revisited the paparazzi osx installation page, noted the comments at the top and am using macports to install paparazzi tools as there is no binary installer file for mavericks. 

I’m using a Tiny 2 so I’m skipping the Luftboot and PyUSB steps.

Since I had problems with multiple ports in different places on my last attempt, I looked at the ‘troubleshooting' steps: 

echo $PATH

export PATH=/opt/paparazzi/bin:/opt/paparazzi/sbin:$PATH

This conflicts with the 'Installing from source' instructions immediately below it which asks for the first path entry to be set to /opt/local/bin, so I guessed that the troubleshooting steps are not applicable at this point.  

I followed the ‘Installing from source’ section and managed to install paparazzi tools OK, It did stop on one port with this error:

Error: org.macports.fetch for port gcc-arm-embedded returned: fetch failed

I got past this (I hope correctly) using:

sudo port install gcc-arm-embedded

This worked and I restarted the paparazzi-tools install, below is the tail end of the installation, which as far as I know means it was successful.  

Extracting paparazzi-tools

--->  Configuring paparazzi-tools

--->  Building paparazzi-tools

--->  Staging paparazzi-tools into destroot

--->  Installing paparazzi-tools @2013.03.26_1+pprz_v4

--->  Activating paparazzi-tools @2013.03.26_1+pprz_v4

--->  Cleaning paparazzi-tools

--->  Updating database of binaries: 100.0%

--->  Scanning binaries for linking errors: 100.0%

--->  Found 9 broken file(s), matching files to ports

--->  Found 2 broken port(s), determining rebuild order

--->  Rebuilding in order

     ocaml @4.01.0 

     tiff @4.0.3 

--->  Computing dependencies for ocaml

--->  Cleaning ocaml

--->  Computing dependencies for tiff

--->  Cleaning tiff

--->  Scanning binaries for linking errors: 100.0%

--->  Found 9 broken file(s), matching files to ports

--->  Found 2 broken port(s), determining rebuild order

--->  Rebuilding in order

     ocaml @4.01.0 

     tiff @4.0.3 

--->  Computing dependencies for ocaml

--->  Fetching distfiles for ocaml

--->  Attempting to fetch ocaml-4.01.0.tar.bz2 from http://lil.fr.distfiles.macports.org/ocaml

--->  Verifying checksums for ocaml

--->  Extracting ocaml

--->  Configuring ocaml

--->  Building ocaml

--->  Staging ocaml into destroot

--->  Unable to uninstall ocaml @4.01.0_0, the following ports depend on it:

--->  ocaml-findlib @1.4_1

--->  ocaml-pcre @7.0.4_0

--->  ocaml-ocamlnet @3.7.3_0

--->  ivy-ocaml @r3577-2013.03.27_2

--->  lablgtk2 @2.18.0_0+x11

--->  ocaml-gsl @0.6.0_3

--->  lablgl @20120306_3

--->  ocamlsdl @0.9.1_4

--->  xml-light @2.2_5

--->  paparazzi-tools @2013.03.26_1+pprz_v4

Warning: Uninstall forced.  Proceeding despite dependencies.

--->  Deactivating ocaml @4.01.0_0

--->  Unable to deactivate ocaml @4.01.0_0, the following ports depend on it:

--->  ocaml-findlib @1.4_1

--->  ocaml-pcre @7.0.4_0

--->  ocaml-ocamlnet @3.7.3_0

--->  ivy-ocaml @r3577-2013.03.27_2

--->  lablgtk2 @2.18.0_0+x11

--->  ocaml-gsl @0.6.0_3

--->  lablgl @20120306_3

--->  ocamlsdl @0.9.1_4

--->  xml-light @2.2_5

--->  paparazzi-tools @2013.03.26_1+pprz_v4

Warning: Deactivate forced.  Proceeding despite dependencies.

--->  Cleaning ocaml

--->  Uninstalling ocaml @4.01.0_0

--->  Cleaning ocaml

--->  Computing dependencies for ocaml

--->  Installing ocaml @4.01.0_0

--->  Activating ocaml @4.01.0_0

--->  Cleaning ocaml

--->  Computing dependencies for tiff

--->  Fetching distfiles for tiff

--->  Attempting to fetch tiff-4.0.3.tar.gz from http://lil.fr.distfiles.macports.org/tiff

--->  Verifying checksums for tiff

--->  Extracting tiff

--->  Applying patches to tiff

--->  Configuring tiff

--->  Building tiff

--->  Staging tiff into destroot

--->  Unable to uninstall tiff @4.0.3_2, the following ports depend on it:

--->  gdk-pixbuf2 @2.30.3_0+x11

--->  libsdl_image @1.2.12_4

--->  lcms @1.19_5

Warning: Uninstall forced.  Proceeding despite dependencies.

--->  Deactivating tiff @4.0.3_2

--->  Unable to deactivate tiff @4.0.3_2, the following ports depend on it:

--->  gdk-pixbuf2 @2.30.3_0+x11

--->  libsdl_image @1.2.12_4

--->  lcms @1.19_5

Warning: Deactivate forced.  Proceeding despite dependencies.

--->  Cleaning tiff

--->  Uninstalling tiff @4.0.3_2

--->  Cleaning tiff

--->  Computing dependencies for tiff

--->  Installing tiff @4.0.3_2

--->  Activating tiff @4.0.3_2

--->  Cleaning tiff

--->  Updating database of binaries: 100.0%

--->  Scanning binaries for linking errors: 100.0%

--->  No broken files found.

 

After this, I followed the generic instructions to get the source code using git, which was successful.  I then tried ‘make’ which is where it fails, giving multiple warnings that Interface gliblvy.cmi occurs in several directories.

findlib: [WARNING] Interface glibIvy.cmi occurs in several directories: /opt/local/lib/ocaml/site-lib/glibivy, /opt/local/lib/ocaml

File "_none_", line 1:

Error: Error on dynamically loaded library: dlllablgtk2.so: dlopen(dlllablgtk2.so, 138): image not found

make[1]: *** [paparazzicenter] Error 2

make: *** [sw/supervision] Error 2

Any ideas why it would be doing this?

Thanks

Chris 

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

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