Deploy.sh errors on VM'ed Ubuntu 12.04

[osrf-migration]

Original report (archived issue) by Nick Sweet (Bitbucket: nckswt).

The original report had attachments: gzweb-build-report-nckswt.txt

---

(Not sure if I should be adding this here or on http://answers.gazebosim.org/)

When I run the deploy.sh script, I get a number of errors. Here's a selection of them (full output attached):

#!bash

home/cohrint/gzweb/tools/gzcoarse.cc: In function ‘void ExportTextureSource(const gazebo::common::SubMesh*, const gazebo::common::SubMesh*, TiXmlElement*, const char*)’:
/home/cohrint/gzweb/tools/gzcoarse.cc:144:25: error: invalid conversion from ‘long unsigned int*’ to ‘unsigned int*’ [-fpermissive]
/home/cohrint/gzweb/tools/nanoflann.hpp:947:21: error:   initializing argument 3 of ‘void nanoflann::KDTreeSingleIndexAdaptor<Distance, DatasetAdaptor, DIM, IndexType>::knnSearch(const ElementType*, size_t, IndexType*, nanoflann::KDTreeSingleIndexAdaptor<Distance, DatasetAdaptor, DIM, IndexType>::DistanceType*, int) const [with Distance = nanoflann::L2_Simple_Adaptor<double, PointCloud<double> >, DatasetAdaptor = PointCloud<double>, int DIM = 3, IndexType = unsigned int, nanoflann::KDTreeSingleIndexAdaptor<Distance, DatasetAdaptor, DIM, IndexType>::ElementType = double, size_t = unsigned int, nanoflann::KDTreeSingleIndexAdaptor<Distance, DatasetAdaptor, DIM, IndexType>::DistanceType = double]’ [-fpermissive]
make[2]: *** [tools/CMakeFiles/gzcoarse.dir/gzcoarse.cc.o] Error 1
make[1]: *** [tools/CMakeFiles/gzcoarse.dir/all] Error 2
make: *** [all] Error 2

#!bash

make: Entering directory `/home/cohrint/gzweb/gzbridge/build'
  CXX(target) Debug/obj.target/gzbridge/GZNode.o
g++: fatal error: no input files
compilation terminated.
/bin/sh: 1: /usr/include: Permission denied
make: *** [Debug/obj.target/gzbridge/GZNode.o] Error 126
make: Leaving directory `/home/cohrint/gzweb/gzbridge/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/cohrint/gzweb/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:70:17)
gyp ERR! stack     at maybeExit (child_process.js:360:16)
gyp ERR! stack     at Process.onexit (child_process.js:396:5)
gyp ERR! System Linux 3.2.0-60-generic-pae
gyp ERR! command "node" "/home/cohrint/gzweb/node_modules/.bin/node-gyp" "build" "-d"
gyp ERR! cwd /home/cohrint/gzweb/gzbridge
gyp ERR! node -v v0.6.12
gyp ERR! node-gyp -v v0.9.6
gyp ERR! not ok 

#!bash

error [Errno 2] No such file or directory
Traceback (most recent call last):
  File "./webify_models_v2.py", line 44, in <module>
    subprocess.check_call(cmd)
  File "/usr/lib/python2.7/subprocess.py", line 506, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 493, in call
    return Popen(*popenargs, **kwargs).wait()
  File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1249, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

I'm running this on a VM of Ubuntu 12.04 from OS X on a late 2013 rMBP. Any idea what the issues might be caused by? This was built from the default branch, but I've also tried the 1.1.0 branch to the same outcome.

[osrf-migration]

Original comment by Nick Sweet (Bitbucket: nckswt).

---

• changed state from "new" to "resolved"

Actually, it seems like this is a local group permission issue. Please delete this.

[osrf-migration]

Original comment by Nick Sweet (Bitbucket: nckswt).

---

• Edited issue description

[osrf-migration]

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

---

Hello Nick,

Actually I started having the exact same problem yesterday when I upgraded to ubuntu 14.04.

Can you share your solution here?

Thanks

[osrf-migration]

Original comment by Nick Sweet (Bitbucket: nckswt).

---

Kind of - I had changed my username, and the files were still listed under the group of the previous username. So, seeing that, I jumped the gun and deleted my post (because I figured it was just a problem on my end).

...then I realized that the problem still persisted, and I was sheepish about my pre-emptive post deletion, so I didn't re-instate the post because of my embarrassment and tried installing Gazebo on Mac instead.

I'll put everything back, and hopefully we can find the bug!

[osrf-migration]

Original comment by Nick Sweet (Bitbucket: nckswt).

---

• changed state from "resolved" to "open"

Issue wasn't ever solved.

[osrf-migration]

Original comment by Nick Sweet (Bitbucket: nckswt).

---

• Edited issue description

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

for the gzbridge build errors, there was a change in the latest gazebo version that broke the build. The gazebo pkg-config cflags and ldflags are incorrect. I've ticketed a gazebo issue #1259.

Until that's fixed, we'll have to find a workaround to make gzweb build. One manual way for now is to find the gazebo.pc file (e.g. /usr/lib/pkgconfig)

• under CFlags: remove ;/usr/include

• under Libs: remove -l in front of the libsdformat.so

I'll see if there's a better way around this

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

@chapulina do you get the gzcoarse.cc errors?

[osrf-migration]

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

---

No, only the gzbridge ones

[osrf-migration]

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

---

Btw, Ian's workaround worked for me :D

[osrf-migration]

Original comment by Nick Sweet (Bitbucket: nckswt).

---

Hmm, my gazebo.pc was found under /usr/lib/i386-linux-gnu/pkgconfig/gazebo.pc instead. I wonder if that causes issues as well?

I still wasn't able to get gzweb installed with Ian's fix. Output can be found here: https://dl.dropboxusercontent.com/u/372239/gzweb-build-report-nckswt2.rtf

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

It looks like you're getting the node-gyp errors now which is a good sign

can you try update to the gzcoarse_kdtree_type branch to see if it fixes the compile error with gzcoarse?

then just do ./deploy.sh without the -m as the models should have already been downloaded in the previous run.

[osrf-migration]

Original comment by Nick Sweet (Bitbucket: nckswt).

---

Ah, that almost worked! It fixed the compile errors with gzcoarse, but it looks like there's still a problem when I try to download the models with the -m flag. If I run deploy.sh without the -m, everything builds just fine and I can run gzweb, but I don't have any models at all (I have the names of models, but they just all load as white boxes).

If I run it with the -m flag, I get this output at the end:

error [Errno 2] No such file or directory Traceback (most recent call last): File "./webify_models_v2.py", line 44, in <module> subprocess.check_call(cmd) File "/usr/lib/python2.7/subprocess.py", line 506, in check_call retcode = call(*popenargs, **kwargs) File "/usr/lib/python2.7/subprocess.py", line 493, in call return Popen(*popenargs, **kwargs).wait() File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1249, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory

So, one bug down, one to go!

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

just checking, you have ImageMagick installed? typing convert in the terminal works?

[osrf-migration]

Original comment by Nick Sweet (Bitbucket: nckswt).

---

I didn't - so I sudo apt-get installed it, and then the deploy.sh script completed without error! The only issue that remains is that some models don't seem to be imported correctly - as you can see in the attached images, even though I import a husky twice, neither one shows up and it looks like a lot of graphical links are broken (though the Create seems to come in just fine).

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

ahh yes, we have problem with the husky model as it's using stl meshes. Currently gzweb only supports collada .dae meshes. There is a plan in gazebo to update the husky model in the model database. Do you need to use it?

As for the broken image links, @chapulina did we add an option in deploy.sh to generate thumbnails?

[osrf-migration]

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

---

Pull request #60 generates the thumbnails when the database is created (./deploy.sh -m). I can make it optional if you want. And maybe add a README file inside tools explaining how to use the thumbnail generator outside of deploy...

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

ok mmm because that line seems to be missing from deploy.sh in the default branch

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

• changed state from "open" to "resolved"

pull request #59, pull request #61, and gazebo pull request #1171

need to wait for the next gazebo release for the npm errors to go away completely