On Wednesday, 26 July 2000, Mark Hindley writes:
> Yes guile-1.3.4.
Ok.
> I have built and installed kpathsea under cygwin from the texk sources. Is
> it not supposed to work? I have had no problems and it works fine
Good! Like I said, I'm using cross-building, so I don't have miktex
installed. I tried to strip the kpathsea lib from texk, but it wouldn't
configure without a tex installation (which I don't have in my
cross-build environment).
Two questions:
* How did you configure+ compile kpathsea? After stripping kpathsea
from texk, a number of configure files were missing: klibtool,
config.guess etc. after adding all missing stuff, kpathsea wouldn't
configure without fooling it to find a TeX distribution. After that,
it wouldn't compile:
++ tar xzf /usr/src/cygwin-1.1.1/usr/src/releases/kpathsea-7.2.tar.gz
++ mkdir -p kpathsea-build
++ cd kpathsea-build
++ CPPFLAGS=-I/Cygnus/usr/include
++ LDFLAGS=-L/Cygnus/usr/lib /Cygnus/usr/bin/cygwin1.dll
++ CONFIG_SITE=/usr/src/cygwin-1.1.1/usr/share/native-config.site
++ ../kpathsea/configure --host=ppc-gnu-linux --target=i686-pc-cygwin
--prefix=/Cygnus/usr --program-prefix= -v
loading site script /usr/src/cygwin-1.1.1/usr/share/native-config.site
creating cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc -g -L/Cygnus/usr/lib
/Cygnus/usr/bin/cygwin1.dll) works... yes
checking whether the C compiler (gcc -g -L/Cygnus/usr/lib
/Cygnus/usr/bin/cygwin1.dll) is a cross-compiler... yes
checking whether we are using GNU C... yes
...
configure: warning: The main texmf tree was not found.
Specify the location of its parent directory with the --datadir option.
If you do not have the files, you can retrieve a minimal set from
ftp://ftp.tug.org/tex/texmflib.tar.gz, which is mirrored on CTAN hosts
in systems/web2c. Winging it by using the default location.
updating cache ./config.cache
creating ./config.status
creating Makefile
creating c-auto.h
++ make
make: *** No rule to make target `kpsewhich.c', needed for `kpsewhich.o'. Stop.
+ result=2
then, I gave up.
* Like I said, I'm currently distributing binaries for Windows. Now that
you're able to build with kpathsea support, and I'm not, would you be
willing to build and or distribute them? I'd like to be able to build
them myself (too), but I can't do any testing anyway.
> I'm using MikTex 1.20e.
>
> What other cygwin issues are there?
1. The symlinks in the .zip or .tar.gz distribution don't work when
unpacked (this may be a non-issue if we/you get kpathsea to works for
all).
2. The regex module of guile doesn't work*. It's probably a problem with
the underlying regex library. I've tried to use cygwin's regex routines,
but didn't succeed to find the proper header file: it either wouldn't
compile, or any call to the regex interface would result in a core dump.
ALso, I've tried rx-1.5, rx-1.8a and regex-0.12.
* regex is currently disabled on windows, see scm/lily.scm and
scm/chord-names.scm:
;; The regex module may not be available, or may be broken.
;; If you have trouble with regex, define #f
;;(define use-regex #t)
;;(define use-regex #f)
(define use-regex
(let ((os (string-downcase (vector-ref (uname) 0))))
(not (equal? "cygwin" (substring os 0 (min 6 (string-length os)))))))
3. No manual pages, because we don't have help2man, no other prepackaged
documentation, because I can't run the cross-built lilypond.
4. For users: probably no dvi viewer that shows PostScript symbols such
as slurs and beams? On unix, xdvi shows PostScript symbols by forking
ghostscript, with the latest xdvi we also have point-n-click editing:
clicking on a symbol in your xdvi window lets your favourit editor
jump to the definition in the .ly source file.
5. What packaging/installing convention to use? I've tried rpms for easy
upgrading, and installed/packaged as:
/Cygnus/usr/bin/lilypond
/Cygnus/usr/bin/guile
/Cygnus/usr/share/lilypond/...
but users requested something like:
Cygnus/lilypond-x.y.z/bin/lilypond
Cygnus/lilypond-x.y.z/share/lilypond/...
so that they would have every package in its own directory. However,
this needs ./configure --prefix=/Cygnus/lilypond-x.y.z/ of course.
That's all I can think of now...
O, and pl75 fixes a number of small bugs, you'll want to try that.
Thanks for your efforts + Greetings,
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
