Openstreetmap-website: fail to vagrant up after I download the "openstreetmap-website" file according to the step

[dog1993]

I use vagrant and VirtualBox Built a virtual environment on my Mac，and download the "openstreetmap-website" file according to the step. when i vagrant up，default: make: * No rule to make target '/root', needed by 'quadtile.o'. Stop. How do i fix it? Thanks.

[tomhughes]

No idea I'm afraid.

Sounds like maybe it was a problem installing the quad_tile gem but would need more context to be sure.

[tomhughes]

I'd add that I know nothing much about vagrant or macs so I may not be the best person to help anyway ;-)

[gravitystorm]

I get the same problem running vagrant up on master. It's related to the changes in https://github.com/openstreetmap/openstreetmap-website/pull/1899.

The provisioning command that fails is:

pushd db/functions
sudo -u vagrant make

The Makefile tries to find the quad_tile headers with

QTDIR=$(shell bundle show quad_tile)/ext/quad_tile

but running sudo -u vagrant bundle show quad_tile as root within the virtual machine highlights the bug:

root@ubuntu-xenial:/srv/openstreetmap-website/db/functions# sudo -u vagrant bundle show quad_tile
`/root` is not writable.
Bundler will use `/tmp/bundler/home/vagrant' as your home directory temporarily.
/var/lib/gems/2.3.0/gems/quad_tile-1.0.1

The makefile is taking the output from that, including the warnings, and so the error message becomes:

==> default: make: *** No rule to make target '`/root`', needed by 'quadtile.o'.  Stop.

[gravitystorm]

I can think of many different ways to solve this, but I'm not sure what would be best.

• Avoid installing the gems as root in the first place
• Complain to bundler about stdout vs stderr outputs!
• Change the Makefile to handle the garbled output better
• Probably many more options too

[dog1993]

@gravitystorm I build up the “openstreetmap-website” on the Ubuntu system to avoid the error result of vagrant up. I hope I can succeed. Thank you very much

[dog1993]

@tomhughes Thank you all the same.Maybe it's because I'm unfamiliar with vagrant.

[gravitystorm]

@dog1993 Just to be more clear - you have found a bug in our code, and this issue is now where we are trying to fix this bug. You did nothing wrong.

[gravitystorm]

Complain to bundler about stdout vs stderr outputs!

https://github.com/bundler/bundler/issues/6067 - apparently will be fixed in bundler 2.0, but that doesn't help us here.