2016-06-06 19:07 GMT+02:00 Achim Gratz <strom...@nexgo.de>: > That file is created by configure, so patching it in anyway is still > useless. No. The file created by configure is version.h.
VERSION file later is employed by the version.sh script: ----------------- if test "x$LIBSASS_VERSION" = "x"; then LIBSASS_VERSION=`git describe --abbrev=4 --dirty --always --tags 2>/dev/null` fi if test "x$LIBSASS_VERSION" = "x"; then LIBSASS_VERSION=`cat VERSION 2>/dev/null` fi if test "x$LIBSASS_VERSION" = "x"; then LIBSASS_VERSION="[na]" fi echo $LIBSASS_VERSION ----------------- Former will fail because it's not a git repository, so it falls back to reading from VERSION file, or else it will use "[na]". This script is called using m4_esyscmd_s from configure.ac line 6: ----------------- AC_INIT([libsass], m4_esyscmd_s([./version.sh]), [supp...@moovweb.com]) ----------------- to set the library version at compile time. Then configure uses it to generate the version.h file. The patch is supposed to create that file at ./libsass-3.3.6-1.i686/src/VERSION, but for some reason cygport creates it at ./libsass-3.3.6-1.i686/src/libsass-3.3.6/src/libsass-3.3.6/VERSION, so version.sh can't read it and reports "[na]" anyway. Any insight on why the patch created by cygport itself isn't working? -- Marcos Vives Del Sol https://github.com/socram8888 miniLock: NscWdW8fh2E5SBoRtrnXWrDwmQmwaR5awMKE78tQW1Ffx
