Re: [Paparazzi-devel] Paparazzi Install on OSX Lion

[bernard]

Hi Chris,

So I'm guessing from that lack of write permissions to /tmp that something
isn't quite right with the permissions on your Mac...
I'd run disk utility and check the and fix the permissions as this
"should" fix the permissions on /tmp to make the directory 0777
(Actually you'll find that /tmp is a sum link to /private/tmp and this
directory is the one with the permissions problem.
ls -la /private/
...
drwxrwxrwt   17 root  wheel   578 22 Feb 12:29 tmp
...

If Disk Utility doesn't fix it then a good old "sudo chmod 0777
/private/tmp" should do the trick.
I'm not sure what the t is on the end of the permissions so maybe "sudo
chmod a+wrx /private/tmp" might be better???

You shouldn't have any problems building or running paparazzi as a non
root user.

Cheers,
Bernie.

> Thanks Bernard,
>
> That did indeed solve that issue, but it uncovered a new one. Now I've
> got permission errors when trying to make paparazzi:
>
> ld: warning: -read_only_relocs cannot be used with x86_64
> cd sw/supervision; make PAPARAZZI_SRC=/Users/cwozny/paparazzi
> PAPARAZZI_HOME=/Users/cwozny/paparazzi
> ocamldep -I ../lib/ocaml *.ml* > .depend
> grep -v invisible_char paparazzicenter.glade > /tmp/paparazzicenter.glade
> /bin/sh: /tmp/paparazzicenter.glade: Permission denied
> make[1]: *** [gtk_pc.ml] Error 1
> make: *** [center] Error 2
>
> Have you seen this before? I then sudo made paparazzi and sudo ran
> paparazzi and everything seems to work, but I'd rather not give
> paparazzi su access everytime I have to use it ;)
>
> - Chris
>
> On Tue, Feb 21, 2012 at 6:02 PM,  <address@hidden> wrote:
>> Hi Chris,
>>
>> I haven't ever seen this.
>>
>> When encountering errors of any kind when building my plan of attack is
>> always
>> 1) make clean
>> 2) git pull origin <branch>
>> 3) make
>> 4) whatever I was trying to do before...
>>
>> This usually fixes the problems.
>>
>> When I was building MacPorts I used to also make the approach
>> 1) make clean
>> 2) sudo port selfupdate
>> 3) sudo port upgrade outdated
>> 4) git pull origin <branch>
>> 5) make
>> 6) whatever I was trying to do before...
>>
>> Sometimes however step three would spew heaps of errors and so step 3
>> would become
>> 3a) sudo port -f uninstall installed
>> 3b) sudo port clean --all uninstalled
>> 3c) sudo port install paparazzi-tools
>>
>> Now however I just take the binary build as its a much quicker process
>> and
>> more stable as I don't have to worry about the moving target that
>> MacPorts
>> is.
>>
>> Cheers,
>> Bernie.
>>
>>> Have any of the OSX users run into this situation when trying to build
>>> from source on OSX?
>>>
>>> $ make
>>> cd data/maps; make PAPARAZZI_SRC=/Users/cwozny/paparazzi
>>> PAPARAZZI_HOME=/Users/cwozny/paparazzi
>>> DOWNLOAD: google maps version code
>>> if test ! -e conf/maps.xml; then cp conf/maps.xml.example
>>> conf/maps.xml;
>>> fi
>>> cd sw/lib/ocaml; make PAPARAZZI_SRC=/Users/cwozny/paparazzi
>>> PAPARAZZI_HOME=/Users/cwozny/paparazzi
>>> OC fig.ml
>>> File "fig.ml", line 1, characters 0-1:
>>> Error: Could not find the .cmi file for interface fig.mli.
>>> make[1]: *** [fig.cmo] Error 2
>>> make: *** [lib] Error 2
>>>
>>> It's looking for a .cmi file related to fig.mli. I've installed
>>> paparazzi-tools and have pulled the dev branch from git. The only
>>> related topic on the mailing list was someone installing on Ubuntu,
>>> but that was two years ago and was said to be rectified in later
>>> posts.
>>>
>>> - 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
>