Opened 6 years ago

Closed 21 months ago

#21896 closed defect (wontfix)

Error installing autotools spkg on Cygwin-64

Reported by: embray Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: porting: Cygwin Keywords:
Cc: mkoeppe, dimpase Merged in:
Authors: Reviewers: Dima Pasechnik
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

When installing the autotools spkg on Cygwin it runs for a while, then fails at:

[autotools-20141105] [ "$SAGE_KEEP_BUILT_SPKGS" = yes ] || rm -rf autoconf-2.69/*
[autotools-20141105] export MAKE='make -j1' ; \
[autotools-20141105] export AUTOCONF_VERSION=2.59 ; \
[autotools-20141105] cd automake-1.9 && \
[autotools-20141105]     ./configure --prefix="/home/embray/src/sagemath/sage/local/automake-1.9" && \
[autotools-20141105]     $MAKE && $MAKE install
[autotools-20141105] checking build system type... lib/config.guess: unable to guess system type
[autotools-20141105]
[autotools-20141105] This script, last modified 2004-06-24, has failed to recognize
[autotools-20141105] the operating system you are using. It is advised that you
[autotools-20141105] download the most up to date version of the config scripts from
[autotools-20141105]
[autotools-20141105]     ftp://ftp.gnu.org/pub/gnu/config/
[autotools-20141105]
[autotools-20141105] If the version you run (lib/config.guess) is already up to date, please
[autotools-20141105] send the following data and any information you think might be
[autotools-20141105] pertinent to <config-patches@gnu.org> in order to provide the needed
[autotools-20141105] information to handle your system.
[autotools-20141105]
[autotools-20141105] config.guess timestamp = 2004-06-24
[autotools-20141105]
[autotools-20141105] uname -m = x86_64
[autotools-20141105] uname -r = 2.5.1(0.297/5/3)
[autotools-20141105] uname -s = CYGWIN_NT-10.0
[autotools-20141105] uname -v = 2016-04-21 22:14
[autotools-20141105]
[autotools-20141105] /usr/bin/uname -p = unknown
[autotools-20141105] /bin/uname -X     =
[autotools-20141105]
[autotools-20141105] hostinfo               =
[autotools-20141105] /bin/universe          =
[autotools-20141105] /usr/bin/arch -k       =
[autotools-20141105] /bin/arch              = x86_64
[autotools-20141105] /usr/bin/oslevel       =
[autotools-20141105] /usr/convex/getsysinfo =
[autotools-20141105]
[autotools-20141105] UNAME_MACHINE = x86_64
[autotools-20141105] UNAME_RELEASE = 2.5.1(0.297/5/3)
[autotools-20141105] UNAME_SYSTEM  = CYGWIN_NT-10.0
[autotools-20141105] UNAME_VERSION = 2016-04-21 22:14
[autotools-20141105] configure: error: cannot guess build type; you must specify one
[autotools-20141105] make[2]: *** [Makefile:235: /home/embray/src/sagemath/sage/local/automake-1.9] Error 1
[autotools-20141105] make[2]: Leaving directory '/home/embray/src/sagemath/sage/local/var/tmp/sage/build/autotools-20141105/build'

upon trying to install automake 1.9.

This also left the autoreconf script installed by sage broken:

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I m4 --output=aclocal.m4t
/home/embray/src/sagemath/sage/local/bin/aclocal: line 25: /home/embray/src/sagemath/sage/local/automake-1.15/bin/aclocal: No such file or directory
autoreconf: aclocal failed with exit status: 127

It would be nice if sage packages didn't actually install anything into $SAGE_LOCAL until it has successfully built.

Change History (11)

comment:1 Changed 6 years ago by embray

Manually going into the automake-1.9 source directory and copying the config.guess from my system's /usr/share/automake-1.15 allowed it to build.

Version 0, edited 6 years ago by embray (next)

comment:2 Changed 6 years ago by embray

  • Summary changed from Error installing autotools spkg on Cygwin to Error installing autotools spkg on Cygwin-64

After a closer look at the different config.guess scripts, the old ones would have worked on 32-bit Cygwin, but not on 64-bit Cygwin (they lack wildcard patterns that would match "x86_64" as the machine name).

comment:3 follow-up: Changed 6 years ago by jpflori

Sage provides more or less up to date config.* scripts. You can try to modify the spkg-install script to copy them at build time to let the build proceed... But maybe installing autotools on a cygwin setup is not the best idea :/

comment:4 in reply to: ↑ 3 ; follow-up: Changed 6 years ago by embray

Replying to jpflori:

Sage provides more or less up to date config.* scripts.

Provides how?

But maybe installing autotools on a cygwin setup is not the best idea :/

What would make you say that?

comment:5 in reply to: ↑ 4 Changed 6 years ago by jpflori

Replying to embray:

Replying to jpflori:

Sage provides more or less up to date config.* scripts.

Provides how?

In $SAGE_ROOT/config/

But maybe installing autotools on a cygwin setup is not the best idea :/

What would make you say that?

You could autoreconf on a Linux machine, ok that implies maintaining two systems and communicating btw them...

comment:6 Changed 6 years ago by embray

For now I hand-edited the Makefile.build to copy my working config.guess to the proper place when building all the automakes, so I've kicked off that build.

In the meantime I've edited spkg-write-makefile (will post a patch soon) to add such a step to the makefile (the details are subject to debate; I haven't thought it through fully). Once I've bootstrapped my $SAGE_LOCAL with a working autotools build I can re-run spkg-write-makefile to provide an updated Makefile.build as well.

comment:7 Changed 6 years ago by mkoeppe

  • Cc mkoeppe added

comment:8 Changed 5 years ago by embray

  • Milestone changed from sage-7.5 to sage-wishlist

comment:9 Changed 22 months ago by mkoeppe

  • Cc dimpase added
  • Milestone changed from sage-wishlist to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

Outdated - we removed the spkg

comment:10 Changed 22 months ago by dimpase

  • Reviewers set to Dima Pasechnik
  • Status changed from needs_review to positive_review

comment:11 Changed 21 months ago by embray

  • Resolution set to wontfix
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.