Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configure: error: unsafe absolute working directory name #23

Closed
vincentcr opened this issue Feb 9, 2012 · 4 comments
Closed

configure: error: unsafe absolute working directory name #23

vincentcr opened this issue Feb 9, 2012 · 4 comments
Labels

Comments

@vincentcr
Copy link

trying to install on osx lion, with node 0.6.6, results in this error:

cd deps/libiconv && ./configure --disable-shared --enable-static --enable-relocatable --enable-extra-encodings
checking for a BSD-compatible install... /usr/local/bin/ginstall -c
checking whether build environment is sane... configure: error: unsafe absolute working directory name
make: *** [deps/libiconv/Makefile] Error 1
Waf: Leaving directory `/Users/vincent/devel/node_modules/iconv/build'
'install' finished successfully (1.459s)
iconv@1.1.3 ./node_modules/iconv 

note that, for some reason, the failure is not communicated up the chain and npm believes the install suceeded.

@bnoordhuis
Copy link
Owner

Thanks for the report. Can you clone the repo and run wscript configure build? That error you get is an autoconf macro that checks if the path doesn't contain funny characters like & or #.

note that, for some reason, the failure is not communicated up the chain and npm believes the install suceeded.

Fixed in b4988e1.

@vincentcr
Copy link
Author

Will try later when I get back at my laptop, but that would make sense as
the path contains both a space and a single quote.

@vincentcr
Copy link
Author

confirmed, it's the single quote in the directory name that triggers the "unsafe absolute working directory name" error.

@bnoordhuis
Copy link
Owner

confirmed, it's the single quote in the directory name that triggers the "unsafe absolute working directory name" error.

The best advice I can give you is "don't do that." :-)

autoconf checks for such characters because they wreak all kinds of havoc in Makefiles and shell scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants