2016-01-16 21:40 GMT+01:00 David Kastrup <d...@gnu.org>: > Thomas Morley <thomasmorle...@gmail.com> writes: > >> 2016-01-12 0:22 GMT+01:00 David Kastrup <d...@gnu.org>: >>> Thomas Morley <thomasmorle...@gmail.com> writes: >>> >>>> 2016-01-11 23:14 GMT+01:00 David Kastrup <d...@gnu.org>: >>>> >>>>>> Btw, it wasn't entirely clear to me that guilev2.x changes essential >>>>>> stuff that often. >>>>>> Exactly which guile-version are we aiming for? >>>>> >>>>> The non-existing 2.0.12. Currently, the stable-2.0 branch. The main >>>>> challenge currently seems to be compiling LilyPond with a Guile version >>>>> that is not installed on your system. >>>> >>>> To be sure, the exercise is: >>>> >>>> (1) checkout the marked branch >>>> >>>> ~/guile (master)$ git branch -a >>>> * master >>> [...] >>>> remotes/origin/stable-2.0 >>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^ >>> [...] >>> >>>> (2) Compile it >>>> (3) Build LilyPond with this guile somehow >>>> >>>> Correct? >>> >>> It's the basis for making more tangible progress. [...] >> >> I've now checked out branch origin/stable-2.0, derived a local branch >> and compiled it. >> >> ~/guile/meta (my-stable-2.0)$ ./guile >> GNU Guile 2.0.11.170-4d08e >> [...] >> >> Should be the version we aim at. >> >> Though, how to compile LilyPond with this guile-version? >> Which commands do you actually use for it? > > That question is easy to answer: I never built with anything but the > Ubuntu Guile versions. So this would appear to be of the "look at what > options "./configure --help" offers for this" kind. And if it's silent > about that, see what kind of environment variables might be interpreted. > > I mean, Gub has to do the same here: build its own library version and > use/link it. So there must be a way. > > -- > David Kastrup
"./configure --help" offers some options, eg. --with-python-include=DIR --with-python-lib=NAME but nothing directly for guile. There are several environment variables like CFLAGS but I don't know how to use them or the syntax they expect. Full output of "./configure --help" attached. I really hope someone can demonstrate how to point configure to a self-compiled guile. Cheers, Harm
`configure' configures this package to adapt to many kinds of systems. Usage: ../configure [OPTION]... [VAR=VALUE]... To assign environment variables (e.g., CC, CFLAGS...), specify them as VAR=VALUE. See below for descriptions of some of the useful variables. Defaults for the options are specified in brackets. Configuration: -h, --help display this help and exit --help=short display options specific to this package --help=recursive display the short help of all the included packages -V, --version display version information and exit -q, --quiet, --silent do not print `checking ...' messages --cache-file=FILE cache test results in FILE [disabled] -C, --config-cache alias for `--cache-file=config.cache' -n, --no-create do not create output files --srcdir=DIR find the sources in DIR [configure dir or `..'] Installation directories: --prefix=PREFIX install architecture-independent files in PREFIX [/usr/local] --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX [PREFIX] By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc. You can specify an installation prefix other than `/usr/local' using `--prefix', for instance `--prefix=$HOME'. For better control, use the options below. Fine tuning of the installation directories: --bindir=DIR user executables [EPREFIX/bin] --sbindir=DIR system admin executables [EPREFIX/sbin] --libexecdir=DIR program executables [EPREFIX/libexec] --sysconfdir=DIR read-only single-machine data [PREFIX/etc] --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] --localstatedir=DIR modifiable single-machine data [PREFIX/var] --libdir=DIR object code libraries [EPREFIX/lib] --includedir=DIR C header files [PREFIX/include] --oldincludedir=DIR C header files for non-gcc [/usr/include] --datarootdir=DIR read-only arch.-independent data root [PREFIX/share] --datadir=DIR read-only architecture-independent data [DATAROOTDIR] --infodir=DIR info documentation [DATAROOTDIR/info] --localedir=DIR locale-dependent data [DATAROOTDIR/locale] --mandir=DIR man documentation [DATAROOTDIR/man] --docdir=DIR documentation root [DATAROOTDIR/doc/PACKAGE] --htmldir=DIR html documentation [DOCDIR] --dvidir=DIR dvi documentation [DOCDIR] --pdfdir=DIR pdf documentation [DOCDIR] --psdir=DIR ps documentation [DOCDIR] System types: --build=BUILD configure for building on BUILD [guessed] --host=HOST cross-compile to build programs to run on HOST [BUILD] Optional Features: --disable-option-checking ignore unrecognized --enable/--with options --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) --enable-FEATURE[=ARG] include FEATURE [ARG=yes] --enable-config=CONF put settings in config-CONF.make and config-CONF.h; do `make conf=CONF' to get output in ./out-CONF --enable-documentation build Documentation. Default: on --enable-guile2 highly experimental GUILE 2 support. Default: off --enable-relocation compile with dynamic relocation. Default: off --enable-rpath hardcode runtime library path. Default: off --enable-static-gxx link libstdc++.a statically. Default: off --enable-debugging compile with debugging info. Default: on --enable-checking compile with expensive run-time checks. Default: off --enable-optimising compile with optimising. Default: on --enable-profiling compile with gprof support. Default: off --enable-pipe compile with -pipe. Default: on Optional Packages: --with-PACKAGE[=ARG] use PACKAGE [ARG=yes] --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) --with-texgyre-dir=DIR location of TeX Gyre fonts. --with-localedir=DIR location of locales. Default: PREFIX/share/locale --with-lang=LANG use LANG as language to emit messages --with-python-include=DIR location of the python include dir --with-python-lib=NAME name of the python lib Some influential environment variables: CC C compiler command CFLAGS C compiler flags LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a nonstandard directory <lib dir> LIBS libraries to pass to the linker, e.g. -l<library> CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if you have headers in a nonstandard directory <include dir> CXX C++ compiler command CXXFLAGS C++ compiler flags CXXCPP C++ preprocessor YACC The `Yet Another Compiler Compiler' implementation to use. Defaults to the first program found out of: `bison -y', `byacc', `yacc'. YFLAGS The list of arguments that will be passed by default to $YACC. This script will default YFLAGS to the empty string to avoid a default value of `-d' given by some make applications. Use these variables to override the choices made by `configure' or to help it to find libraries and programs with nonstandard names/locations. Report bugs to the package provider.
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel