Re: Cygwin, Lilypond 2.4.1, stepmake

[myndzi]

A proper Cygwin 'make' helps. Unknown to me, Cygwin was also using my
Windows paths, which contained some windows 'nix binaries including
make. Next up is this:

g++ -shared -o out/midi.dll out/midi.lo
out/midi.lo(.text+0x70): In function `add_constants':
/usr/src/lilypond-2.4.2/python/midi.c:110: undefined reference to
`_Py_BuildValue'
out/midi.lo(.text+0x88):/usr/src/lilypond-2.4.2/python/midi.c:110:
undefined reference to `_PyDict_SetItemString'
out/midi.lo(.text+0x175): In function `read_two_bytes':
/usr/src/lilypond-2.4.2/python/midi.c:159: undefined reference to
`_Py_BuildValue'
.....
out/midi.lo(.text+0x3db): In function `read_f0_byte':
/usr/src/lilypond-2.4.2/python/midi.c:179: undefined reference to
`_Py_BuildValue'
collect2: ld returned 1 exit status
make[1]: *** [out/midi.dll] Error 1
make[1]: Leaving directory `/usr/src/lilypond-2.4.2/python'
make: *** [all] Error 2

---

$ which python
/usr/bin/python

$ python -V
Python 2.3.4

$ which g++
/usr/bin/g++

$ g++ -v
...
gcc version 3.3.3 (cygwin special)


INSTALL.txt says 2.1 or higher. I verified that the file included in
midi.c (Python.h) referenced the modsupport.h file, which contains the
functions in question, though the underscores are throwing me off; the
midi.c file does not have the prefixed _'s on the function names, but
I figure that's just stuff that gets done automatically?

Hope I provided better info this time ;) I may just wait for the
mentioned Cygwin package, but after investing so much time in this
already, I'd like to see it succeed.

-myndzi


On Tue, 09 Nov 2004 16:50:04 +0100, Jan Nieuwenhuizen <address@hidden> wrote:
> myndzi writes:
> 
> > $ make
> > make/stepmake.make:103: 
> > /usr/src/lilypond-2.4.2/stepmake/stepmake/no-builtin-rul
> 
> > All the above files exist in their listed paths.
> 
> Have you tried to open that file?  What does cat
> 
>     cat /usr/src/lilypond-2.4.2/stepmake/stepmake/no-builtin-rules.make
> 
> say?
> 
> Check that you are using Cygwin make, issue something like
> 
>    cygcheck -v $(which make)
> 
> this should be linked to /bin/cygwin1.dll.
> 
> Check that you do not have conflict between DOS and UNIX text, ie, verify
> that the file that make wants to open is not called
> 
>   ../stepmake/no-builtin-rules.make^M
> 
> Do you have a sane mount table?
> 
> If this does not help, try asking the Cygwin list.  Files that do
> exist but cannot be opened is not a LilyPond problem.
> 
> Jan.
> 
> --
> Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
> http://www.xs4all.nl/~jantien       | http://www.lilypond.org
>