URL:
  <http://savannah.gnu.org/bugs/?30317>

                 Summary: autoconf broken on Windows GNUstep MSYS & Core
0.25.0
                 Project: GNUstep
            Submitted by: leighsmith
            Submitted on: Thu 01 Jul 2010 06:34:24 PM GMT
                Category: Packaging
                Severity: 3 - Normal
              Item Group: Bug
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

autoconf is missing, but there is a version numbered binary at
/bin/autoconf-2.64. Unfortunately running that, autoconf-2.64 can't find
autom4t2-2.64, as it is looking in /mingw/bin whereas the binaries reside in
/bin. After setting a symlink of /bin/autom4te-2.64 to
/mingw/bin/autom4te-2.64, it runs, but this then runs /bin/m4 which barfs on
an unexpected --gnu parameter?

So perhaps the solution is to install autoconf into /mingw/bin or otherwise
change the path to search for autom4te-2.64 to include /bin. The error with
/bin/m4 not liking --gnu parameter seems to be a divergence in versions
between m4 and autoconf?






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?30317>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/


_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep

Reply via email to