I just updated config.guess and config.sub to the latest version. See: https://www.gnu.org/software/gettext/manual/html_node/config_002eguess.html
Regards, Matthias Am 15.11.2017 um 17:23 schrieb Matthias Seidel: > > Hi Damjan, > > Next "problem", ./bootstrap can't guess the system: > > --- > entering dmake-4.12 > checking build system type... ./config.guess: unable to guess system type > > This script, last modified 2005-07-08, has failed to recognize > the operating system you are using. It is advised that you > download the most up to date version of the config scripts from > > > http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess > and > > http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub > > If the version you run (./config.guess) is already up to date, please > send the following data and any information you think might be > pertinent to <[email protected]> in order to provide the needed > information to handle your system. > > config.guess timestamp = 2005-07-08 > > uname -m = x86_64 > uname -r = 2.9.0(0.318/5/3) > uname -s = CYGWIN_NT-10.0 > uname -v = 2017-09-12 10:18 > > /usr/bin/uname -p = unknown > /bin/uname -X = > > hostinfo = > /bin/universe = > /usr/bin/arch -k = > /bin/arch = x86_64 > /usr/bin/oslevel = > /usr/convex/getsysinfo = > > UNAME_MACHINE = x86_64 > UNAME_RELEASE = 2.9.0(0.318/5/3) > UNAME_SYSTEM = CYGWIN_NT-10.0 > UNAME_VERSION = 2017-09-12 10:18 > configure: error: cannot guess build type; you must specify one > --- > > I am wondering about the timestamp, our config.guess is from 2009-12-30. > > Regards, Matthias > > > > Am 14.11.2017 um 03:06 schrieb Damjan Jovanovic: >> Please test whether the attached patch helps? >> >> Regards >> Damjan >> >> On Sat, Nov 11, 2017 at 8:02 PM, Matthias Seidel >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hi Damjan, >> >> Am 10.11.2017 um 06:27 schrieb Damjan Jovanovic: >> > Hi >> > >> > I've committed a few small small fixes to oowintool, mostly for >> JDK 8 >> > detection and better logging, but I've confirmed that it >> already works >> > well, and --with-frame-home --with-psdk-home --with-midl-path >> > --with-jdk-home --with-csc-path and --with-cl-home options to >> ./configure >> > are all unnecessary. >> > >> > As for 64 bit Cygwin I believe the problem with oowintool is >> that it needs >> > to look under the Wow6432node subkey in the registry too, >> something that >> > should be easy to add. Is anyone available to test 64 bit Cygwin? >> >> I just installed Cygwin64 on Windows 10 and ./configure stops with: >> >> Can't find MS Visual Studio / VC++ at ./oowintool line 236. >> configure: error: oowintool failed to copy CRT >> >> Regards, Matthias >> >> > >> > Damjan >> > >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >
smime.p7s
Description: S/MIME Cryptographic Signature
