> However, doing "git grep TMP" I also find
> scripts/lilypond-invoke-editor.scm:(or
> (getenv "TMP")
>
> which is from
>
>(or (getenv "TMP")
>(getenv "TEMP")
>
>>> The latter would need another similar fix. And the former uses
>>> Windows-only conventions: the POSIX convention is to look in the TMPDIR
>>> variable. So it might warrant putting a TMPDIR check in front.
>>>
>>> The TMPDIR patch should likely be separate (as it is a different issue
>>> and
> Your yes. But It is not my problem.
> On my 32 bit I have a segfault of the python interpreter, much
> later on
How about this?
$ export PYTHONDEBUG=1
$ make doc
or
$ export PYTHONVERBOSE=1
$ make doc
> have you looked at the output of "rebase -si" ?
Yes.
There is no collisions.
$ rebase -
On 4/18/2015 7:26 AM, Masamichi HOSODA wrote:
So, I use cygwin64 on 64 bit Windows.
Has current 32 bit cygwin been fixed the such problem?
There was some improvement, specially as automatic rebase after
install
is now in place. But they are always possible.
https://cygwin.com/faq.html#faq.usin
>> So, I use cygwin64 on 64 bit Windows.
>>
>> Has current 32 bit cygwin been fixed the such problem?
>
> There was some improvement, specially as automatic rebase after
> install
> is now in place. But they are always possible.
> https://cygwin.com/faq.html#faq.using.fixing-fork-failures
>
>
>
On 4/16/2015 4:04 PM, Masamichi HOSODA wrote:
64 bit "make doc" on 2.19.18 was completed.
on 32 bit I have still issue but much later for a different issue.
Any idea what could cause python to segfault here
or how to debug it ?
Do you use 64 bit Windows?
Both as I am one the package maintai
>> 64 bit "make doc" on 2.19.18 was completed.
>> on 32 bit I have still issue but much later for a different issue.
>
> Any idea what could cause python to segfault here
> or how to debug it ?
Do you use 64 bit Windows?
About two years ago, I installed cygwin (32 bit) to 64 bit Windows.
It was
On 4/14/2015 7:41 AM, Marco Atzeri wrote:
64 bit "make doc" on 2.19.18 was completed.
on 32 bit I have still issue but much later for a different issue.
Any idea what could cause python to segfault here
or how to debug it ?
make[1]: Leaving directory
'/cygdrive/e/cyg_pub/devel/lilypond/devel
cygwin-python.patch:
Set LDFLAGS to build python module
cygwin-remove-pathconv.patch:
Remove cygwin_conv_to_posix_path
This patch is similar to yours.
>>>
>>> Don't know enough about Cygwin to know whether those two are the right
>>> thing. I'd recomm
>>> cygwin-python.patch:
>>> Set LDFLAGS to build python module
>>>
>>> cygwin-remove-pathconv.patch:
>>> Remove cygwin_conv_to_posix_path
>>> This patch is similar to yours.
>>
>> Don't know enough about Cygwin to know whether those two are the right
>> thing. I'd recommend passi
>>> cygwin-env-TMP.patch:
>>> Don't use environment variable TMP when "make doc"
>>> If I understand correctly,
>>> cygwin system use environment variable TMP for a special purpose.
>>> In other words, on cygwin,
>>> it can not be used for other purpose like Makefile variable.
>> I've attach these patches to this mail.
>>
>> cygwin-python.patch:
>> Set LDFLAGS to build python module
>>
>> cygwin-remove-pathconv.patch:
>> Remove cygwin_conv_to_posix_path
>> This patch is similar to yours.
>
> Don't know enough about Cygwin to know whether those two are th
On 4/13/2015 4:29 PM, Masamichi HOSODA wrote:
I am using an equivalent way on the build system
make LDFLAGS="$(python-config --libs)"
Thank you.
When GUB builds cygwin and mingw lilypond,
it seems to be using a similar way.
However, when GUB builds linux lilypond etc., the option is not use
Masamichi HOSODA writes:
> I've attach these patches to this mail.
>
> cygwin-python.patch:
> Set LDFLAGS to build python module
>
> cygwin-remove-pathconv.patch:
> Remove cygwin_conv_to_posix_path
> This patch is similar to yours.
Don't know enough about Cygwin to know whether t
> I am using an equivalent way on the build system
> make LDFLAGS="$(python-config --libs)"
Thank you.
When GUB builds cygwin and mingw lilypond,
it seems to be using a similar way.
However, when GUB builds linux lilypond etc., the option is not used.
It is not cleary for me that why the option
On 4/13/2015 2:03 PM, Masamichi HOSODA wrote:
I've used three patches to build lilypond-2.18.2 on cygwin64 environment.
And, I've succeed following commands.
$ ./configure
$ make all
$ make doc
make doc is always stacking somewhere for me.
But it could be side effect on some dependencies.
> Attached the patches I am using, to remove the
> dos_to_posix CYGWIN specific usage.
> Not clear why it was needed in the past, it is not needed
> in a pure cygwin enviroment and cygwin_conv_to_posix_path
> is deprecated on 32bit and not available on 64bit.
I've used three patches to build lilyp
On 4/12/2015 3:06 PM, Masamichi HOSODA wrote:
On 4/11/2015 2:08 PM, Masamichi HOSODA wrote:
I've tried on my cygwin64 environment.
Maybe environment variable TMP is the cause.
Would you try the attached patch?
The version for 32 bit seems to have other problems.
I see segfaults but I need t
> On 4/11/2015 2:08 PM, Masamichi HOSODA wrote:
>>> Installed contains the results of running the program
>>> after installation only on that snippets.
>>> As it works, I am very puzzled.
>>>
>>> $ lilypond --png lily-487dce2c.ly
>>> GNU LilyPond 2.18.2
>>> Processing `lily-487dce2c.ly'
>>> Parsing
On 4/11/2015 2:08 PM, Masamichi HOSODA wrote:
Installed contains the results of running the program
after installation only on that snippets.
As it works, I am very puzzled.
$ lilypond --png lily-487dce2c.ly
GNU LilyPond 2.18.2
Processing `lily-487dce2c.ly'
Parsing...
Renaming input to: `out-w
> Installed contains the results of running the program
> after installation only on that snippets.
> As it works, I am very puzzled.
>
> $ lilypond --png lily-487dce2c.ly
> GNU LilyPond 2.18.2
> Processing `lily-487dce2c.ly'
> Parsing...
> Renaming input to: `out-www/quantize-start-midi.ly'
> Int
Marco Atzeri writes:
> On 4/11/2015 12:29 PM, David Kastrup wrote:
>
>>>
>>> I presume that lilypond is calling gs with a not recognized option
>>> only on this specific snippet.
>>
>> So which snippet is it? I don't know all the checksums by heart...
>> There likely should be some file
>>
>> /c
On 4/11/2015 12:29 PM, David Kastrup wrote:
I presume that lilypond is calling gs with a not recognized option
only on this specific snippet.
So which snippet is it? I don't know all the checksums by heart...
There likely should be some file
/cygdrive/e/cyg_pub/devel/lilypond/lilypond-2.18.
Marco Atzeri writes:
> On 4/11/2015 8:57 AM, Marco Atzeri wrote:
>>
>>
>> On 4/11/2015 8:09 AM, David Kastrup wrote:
>>> Marco Atzeri writes:
>>>
I am trying to build and package 2.18.2 for cygwin 64 bit.
I am currently stacked in building the documentation
>>>
>>> [...]
>>>
The l
On 4/11/2015 8:57 AM, Marco Atzeri wrote:
On 4/11/2015 8:09 AM, David Kastrup wrote:
Marco Atzeri writes:
I am trying to build and package 2.18.2 for cygwin 64 bit.
I am currently stacked in building the documentation
[...]
The log is not very informative
--
On 4/11/2015 8:09 AM, David Kastrup wrote:
Marco Atzeri writes:
I am trying to build and package 2.18.2 for cygwin 64 bit.
I am currently stacked in building the documentation
[...]
The log is not very informative
Conv
>
> Converting to
> `/cygdrive/e/cyg_pub/devel/lilypond/lilypond-2.18.2-1.x86_64/build/build/out/lybook-db/54/lily-487dce2c.pdf'...
> Converting to PNG...
> fatal error: GS exited with status: 256
> ---
Marco Atzeri writes:
> I am trying to build and package 2.18.2 for cygwin 64 bit.
> I am currently stacked in building the documentation
[...]
> The log is not very informative
>
>
> Converting to
> `/cygdrive/e/cyg_pub/devel/
I am trying to build and package 2.18.2 for cygwin 64 bit.
I am currently stacked in building the documentation
any help in debugging the root cause or go over will be appreciated.
---
make[4]: Entering directory
'/cygdrive/e/cyg_
29 matches
Mail list logo
