Re: [Mingw-users] configure: error: unsafe absolute working directory name

[LRN <lr...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 13.04.2012 13:20, Pra...@Ea... wrote:
> Hello,
> 
> I have Windows XP, SP3 machine with following details,
> 
> 1. MinGW, msys is installed on C:/MinGW/msys 2. Cygwin installed on
> C:/ 3. Buildslave created for directory C:/MinGW/BuildBot
> 
> PATH = 
> C:\bin\;C:\usr\bin;C:\MinGW\BuildBot;C:\Subversion\bin;C:\Python26\Scrip
>
> 
ts;C:\TortoiseSVN\bin;C:\MinGW\libexec\gcc\i686-pc-mingw32\4.6.2;%System
> Root%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\SourceCode\Lib
>
> 
raries\wxWidgets2.8;C:\wxWidgets-2.6.2;
> 
> SHELL = C:/bin/sh.exe
> 
> I am able to configure successfully my NUT(network ups tools)
> source code from msys shell, cygwin terminal and from cmd (windows
> command prompt) with 'sh -c ./configure' command. But it gives
> error "unsafe absolute working directory name" for checking whether
> build environment is sane when called from BuildBot master. Below
> is the log 
> http://buildbot.ghz.cc/public/nut/builders/WinXP-x86/builds/108/steps/co
>
> 
nfigure/logs/stdio
> 
> Can anybody tell me how to solve this issue?
This is the shell code in configure that breaks:
# Reject unsafe characters in $srcdir or the absolute working directory
# name.  Accept space and tab only in the latter.
am_lf='
'
case `pwd` in
  *[\\\"\#\$\&\'\`$am_lf]*)
    as_fn_error $? "unsafe absolute working directory name" "$LINENO" 5 ;;
esac

to debug it, edit configure script by hand and add the following line:
echo pwd=`pwd`
just before the "case..." line, then try to build it with the buildbot
(presumably, you'll have to do it in a buildstep, since builbots pull
source from a repository most of the time).
That will show you what exactly is the value of pwd that freaks
configure script off.
The characters it frowns upon are:
\ " # $ & ' `
and 0x0A (also known as \n).

As for what you did wrong - well, first thing that comes into mind is
that you're running `sh' without --login, which means that
/etc/profile is not getting sourced, which means that:
1) MSYSTEM is not defined
2) C:/mingw/msys/bin and c:/mingw/bin are not added to PATH (and you
have not added them yourself either)
3) HOME is not defined
4) MAKE_MODE is not defined (not sure what it does, but sounds important)

Note that invoking with --login will force you to use command like 'cd
<absolutedirectoryname>; ./configure' instead of just './configure',
since /etc/profile will change current directory.

Or you can do yourself the things /etc/profile does, before invoking
`sh'. In that case you can omit --login and keep using just 'sh -c
./configure'.


ALSO, having both MSys and Cygwin in PATH simultaneously might not be
a good idea (though i have to admit that i haven't tried that myself
for some time, maybe it's safe now).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPiA2lAAoJEOs4Jb6SI2CwYlAH/jr0cIDXisYRd6UBpvk08U+8
f1OYwHPuIGhegOTCjAwJTPN1DGSJa3UdCdPjV0B8fjs9Eiy7I5PB8X8Sy+alNDF+
RQm+0DOg6IxQqy+V+nJVPOv7RLv0aC4vw5DfcHZJoVFlQsvgDCuBB7w0+wF+TDu5
DegVSjyA2FEDaGKUGFDY9kcwVztDHZLucDzOq400epsGgzZyq1145caKeWYtoGVa
BAa85+hK1JtwLFJQQdcuA50Yv7LBJscjoAmEor1cWjYcJfw13aW0clpEVUgvWGy8
g6CQCrWzDVPKUKd0Gozf/cQYKsDNMPiZxnwlQPTowlTT2ktJfgULSk1hl0L7oaY=
=+Uff
-----END PGP SIGNATURE-----