Fix issue with builddir when calling configure with absolute path

Calling configure with an absolute path fails on my machine:

    $ /home/j/repos/libffi/configure
    checking build system type... x86_64-pc-linux-gnu
    checking host system type... arm-unknown-linux-gnueabihf
    checking target system type... arm-unknown-linux-gnueabihf
    continue configure in default builddir "./arm-unknown-linux-gnueabihf"
    ....exec /bin/bash ..//home/j/repos/sfx1_build/Binaries/tegra3-arm/master/build/libffi/libffi/configure "--srcdir=.." "--enable-builddir=arm-unknown-linux-gnueabihf" "linux
    gnueabihf"
    /bin/bash: ..//home/j/repos/sfx1_build/Binaries/tegra3-arm/master/build/libffi/libffi/configure: No such file or directory
    make: *** [/home/j/repos/sfx1_build/Binaries/tegra3-arm/master/build/libffi/libffi-git-patched.configured] Error 127

This is due to missing escaping of square brackets in m4/ax_enable_builddir.m4, which defeats the absolute path detection. The proposed patch adds escaping of square brackets, as well as detection of absolute Windows paths (not sure if that is useful here but it shouldn't hurt).