Re: strange error during make of lily on cygwin

2001-09-16 Thread Jan Nieuwenhuizen

"Gerrit P. Haase" <[EMAIL PROTECTED]> writes:

> $ export HELLO=bug
> 
> $ make
> hello
> Nope, seems to be o.k.

Ok, thanks.  I was a bit confused after this, but it turns out we have
a LilyPond makefile bug after all.  I didn't notice it was the scripts
directory where this happened, where NAME is not set.  This will be
fixed some time soon.

Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel



Re: strange error during make of lily on cygwin

2001-09-16 Thread Paul Jarc

Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote:
> $ unset HELLO
> $ make -f env.make
> $ export HELLO=bug
> $ make -f env.make
>
> Both make runs should say `hello'.

Both do, for me.

> Paul, what platform are you running?

$ uname -a
Linux multivac.cwru.edu 2.4.4 #1 SMP Fri May 11 16:28:16 EDT 2001 i686 unknown
$ /bin/sh --version
GNU bash, version 2.05.0(1)-release (i686-pc-linux-gnu)
Copyright 2000 Free Software Foundation, Inc.
$ make --version
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Built for i386-redhat-linux-gnu
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 2000
Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

Report bugs to <[EMAIL PROTECTED]>.


paul

___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel



Re: strange error during make of lily on cygwin

2001-09-16 Thread Gerrit P. Haase

Jan Nieuwenhuizen schrieb am 2001-09-16, 19:24:

>Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
>
>> "Gerrit P. Haase" <[EMAIL PROTECTED]> writes:
>> 
>> > g++ -s -o out/Gerrit   -s  -L/usr/local/lib -lguile -s -lm
>> > /usr/lib/libm.a(libcmain.o): In function `main':
>> > /cygnus/netrel/src/cygwin-1.3.3-2/winsup/cygwin/lib/libcmain.c:31: undefined 
>reference to `WinMain@16'
>> 
>> You have an environment variable set as NAME, see
>> 
>> http://mail.gnu.org/pipermail/lilypond-devel/2001-August/35.html
>
>I've looked into this, and it seems that your make is broken.
>
>From the info pages:
>
> (If the `-e' flag is specified, then values
>from the environment override assignments in the makefile.  *Note
>Summary of Options: Options Summary.  But this is not recommended
>practice.)
>
>so, an environment variable (eg NAME) should NOT override the variable
>used in the makefile.
>
>Could you try what happens if you make this makefile:
>
>#env.make:
>HELLO=hello
>default:
> @echo $(HELLO)
>
>
>and then do:
>
>
>$ unset HELLO
>$ make -f env.make
>$ export HELLO=bug
>$ make -f env.make
>
>Both make runs should say `hello'.   If they do not, file a bug report
>against your make maintainer (Cygwin for Gerrit; Paul, what platform
>are you running?).

$ unset HELLO

$ make
hello

$ export HELLO=bug

$ make
hello

$ cat Makefile
HELLO=hello
default:
@echo $(HELLO)

$ set | grep HELLO=
HELLO=bug

Nope, seems to be o.k.

Gerrit


-- 
=^..^=

___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel



Re: strange error during make of lily on cygwin

2001-09-16 Thread Gerrit P. Haase

Jan Nieuwenhuizen schrieb am 2001-09-16, 19:24:

>Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
>
>> "Gerrit P. Haase" <[EMAIL PROTECTED]> writes:
>> 
>> > g++ -s -o out/Gerrit   -s  -L/usr/local/lib -lguile -s -lm
>> > /usr/lib/libm.a(libcmain.o): In function `main':
>> > /cygnus/netrel/src/cygwin-1.3.3-2/winsup/cygwin/lib/libcmain.c:31: undefined 
>reference to `WinMain@16'
>> 
>> You have an environment variable set as NAME, see
>> 
>> http://mail.gnu.org/pipermail/lilypond-devel/2001-August/35.html
>
>I've looked into this, and it seems that your make is broken.
>
>From the info pages:
>
> (If the `-e' flag is specified, then values
>from the environment override assignments in the makefile.  *Note
>Summary of Options: Options Summary.  But this is not recommended
>practice.)
>
>so, an environment variable (eg NAME) should NOT override the variable
>used in the makefile.

Maybe a little hint for 'tin' users would not be that bad. For 'tin' you
may set NAME as environment variable.
Dunno what programs else use it.

$ man tin

tin(1) A Usenet newsreader tin(1)

NAME
   tin, rtin, tind - A Usenet newsreader
[...]
ENVIRONMENT VARIABLES
[...]
Overrides the fullname given in the gecos-files in /etc/passwd, see also mail_address. 
[...]

Gerrit


-- 
=^..^=

___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel



Re: lilypond build on cygwin stucks

2001-09-16 Thread Gerrit P. Haase

Jan Nieuwenhuizen schrieb am 2001-09-16, 11:52:

>"Gerrit P. Haase" <[EMAIL PROTECTED]> writes:
>
>> I got compiletime errors:
>> =
>> rm -f ./out/kpath.dep; DEPENDENCIES_OUTPUT="./out/kpath.dep ./out/kpath.o" g++ -c  
>-DHAVE_
>> CONFIG_H  -DSTRING_UTILS_INLINED -Iinclude -I./out -I.././lib/include 
>-I../lib/./out -I../
>> ./flower/include -I../flower/./out -I../flower/include -O2 -finline-functions -g
> -O2 -
>> finline-functions -g   -DSTRING_UTILS_INLINED -I/usr/local/include -Wall  -W 
>-Wmissing-pro
>> totypes -Wconversion  kpath.cc -o out/kpath.o
>> In file included from /usr/include/kpathsea/kpathsea.h:27,
>>  from kpath.cc:19:
>> /usr/include/kpathsea/getopt.h:99: redefinition of `struct option'
>> /usr/include/getopt.h:46: previous definition here
>> /usr/include/kpathsea/getopt.h:128: declaration of C function `int getopt_long(int, 
>char *
>> const *, const char *, const option *, int *)' conflicts with
>> /usr/include/getopt.h:56: previous declaration `int getopt_long(int, char **, char 
>*, opti
>> on *, int *)' here
>
>That's strange.  /usr/include/getopt.h should not get included at
>all.  You should check who's doing that, eg add a #warning to the top
>getopt.h and recompile, see what happens.
>
>> lily-guile.cc: In function `class String ly_scm2string(scm_unused_struct *)':
>> lily-guile.cc:187: passing `int *' as argument 2 of 
>`gh_scm2newstr(scm_unused_struct *, size_t *)' changes signedness
>> make[1]: *** [out/lily-guile.o] Error 1
>> make[1]: Leaving directory `/perl/stuff/sound/lilybuild/lilypond-1.4.7/lily'
>> make: *** [all] Error 2
>
>Are you using a newer guile?  LilyPond 1.5.2 has seen fixes for latest
>(at that time) cvs guile, that won't be backported to lily-1.4.

I used guile-1.4 to at buildtime.
I'm trying to build guile-1.5.2 with dll's, but it doesn't work yet.

>You should use guile 1.3.4 or guile 1.4 with lilypond-1.4.  Patches to
>compile guile for cygwin are in the cygwin-cross package.

Ah, the patches doesn't fit here. There are only some related to
cross-compiling stuff.
But the problem with net_db.c and and_let*.scm are not adressed.
I will try to send my patch so everyone on cygwin should succeed
to compile guile-1.4 without errors.
Another problem is that i would like to include libregex automagically
so the user simply can do 'configure; make; make install' after patching.
Another solution would be to distribute a patched source like usual for cygwin.

Gerrit


-- 
=^..^=

___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel



Re: strange error during make of lily on cygwin

2001-09-16 Thread Jan Nieuwenhuizen

Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:

> "Gerrit P. Haase" <[EMAIL PROTECTED]> writes:
> 
> > g++ -s -o out/Gerrit   -s  -L/usr/local/lib -lguile -s -lm
> > /usr/lib/libm.a(libcmain.o): In function `main':
> > /cygnus/netrel/src/cygwin-1.3.3-2/winsup/cygwin/lib/libcmain.c:31: undefined 
>reference to `WinMain@16'
> 
> You have an environment variable set as NAME, see
> 
> http://mail.gnu.org/pipermail/lilypond-devel/2001-August/35.html

I've looked into this, and it seems that your make is broken.

>From the info pages:

 (If the `-e' flag is specified, then values
from the environment override assignments in the makefile.  *Note
Summary of Options: Options Summary.  But this is not recommended
practice.)

so, an environment variable (eg NAME) should NOT override the variable
used in the makefile.

Could you try what happens if you make this makefile:

#env.make:
HELLO=hello
default:
@echo $(HELLO)


and then do:


$ unset HELLO
$ make -f env.make
$ export HELLO=bug
$ make -f env.make

Both make runs should say `hello'.   If they do not, file a bug report
against your make maintainer (Cygwin for Gerrit; Paul, what platform
are you running?).

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel



[PATCH] Emacs-mode

2001-09-16 Thread Han-Wen Nienhuys

[EMAIL PROTECTED] writes:
> 
> Here is a patch which makes the typesetting with Emacs nicer for an eye.
> Identifiers are separated from keywords and some dynamics are included in
> the font-locking. I make a forecast that this patch makes typing with
> Emacs even a bit more fun!

thanks. I put in all your patches, they will be in 1.5.10.

-- 

Han-Wen Nienhuys   |   [EMAIL PROTECTED]| http://www.cs.uu.nl/~hanwen/


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel



Re: lilypond build on cygwin stucks

2001-09-16 Thread Jan Nieuwenhuizen

"Gerrit P. Haase" <[EMAIL PROTECTED]> writes:

> I got compiletime errors:
> =
> rm -f ./out/kpath.dep; DEPENDENCIES_OUTPUT="./out/kpath.dep ./out/kpath.o" g++ -c  
>-DHAVE_
> CONFIG_H  -DSTRING_UTILS_INLINED -Iinclude -I./out -I.././lib/include -I../lib/./out 
>-I../
> ./flower/include -I../flower/./out -I../flower/include -O2 -finline-functions -g 
>-O2 -
> finline-functions -g   -DSTRING_UTILS_INLINED -I/usr/local/include -Wall  -W 
>-Wmissing-pro
> totypes -Wconversion  kpath.cc -o out/kpath.o
> In file included from /usr/include/kpathsea/kpathsea.h:27,
>  from kpath.cc:19:
> /usr/include/kpathsea/getopt.h:99: redefinition of `struct option'
> /usr/include/getopt.h:46: previous definition here
> /usr/include/kpathsea/getopt.h:128: declaration of C function `int getopt_long(int, 
>char *
> const *, const char *, const option *, int *)' conflicts with
> /usr/include/getopt.h:56: previous declaration `int getopt_long(int, char **, char 
>*, opti
> on *, int *)' here

That's strange.  /usr/include/getopt.h should not get included at
all.  You should check who's doing that, eg add a #warning to the top
getopt.h and recompile, see what happens.

> lily-guile.cc: In function `class String ly_scm2string(scm_unused_struct *)':
> lily-guile.cc:187: passing `int *' as argument 2 of `gh_scm2newstr(scm_unused_struct 
>*, size_t *)' changes signedness
> make[1]: *** [out/lily-guile.o] Error 1
> make[1]: Leaving directory `/perl/stuff/sound/lilybuild/lilypond-1.4.7/lily'
> make: *** [all] Error 2

Are you using a newer guile?  LilyPond 1.5.2 has seen fixes for latest
(at that time) cvs guile, that won't be backported to lily-1.4.

You should use guile 1.3.4 or guile 1.4 with lilypond-1.4.  Patches to
compile guile for cygwin are in the cygwin-cross package.

Jan.


-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel



Re: guile-1.5.2 for lilypond ok?

2001-09-16 Thread Jan Nieuwenhuizen

"Gerrit P. Haase" <[EMAIL PROTECTED]> writes:

> I'm just building a new version of guile with regex support.
> Does LilyPond works with guile 1.5.2, too?

Latest Lily 1.5.x should.  If it doesn't, file a bug report.

Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel