I have successfully built Pike on cygwin. There are currently a few issues you have to get around.
Pike doesn't support cygwin paths. If /cygdrive/x/foo gets handed to a file function it should instead use x:/foo (well, x:\foo). Could this be fixed in fdlib?
Stdio.Terminfo can not decode the cygwin terminfo file. sizeof(strbuf)==sstr-2.
mt_lock( &aap_timeout_mutex ); in HTTPLoop/accept_and_parse.c triggers some sort of thread bug during startup. Just build without HTTPLoop.
I only have 7.4 as native build so I can not make a meaningful comparison now.
/ Martin Nilsson (provokatör)
Previous text:
2004-03-20 12:29: Subject: Re: cygwin days
Martin Nilsson (provokatör) @ Pike (-) developers forum wrote:
I have successfully built Pike on cygwin. There are currently a few issues you have to get around.
Good:))
What is the speed compared to the native build ?
/ David
/ Brevbäraren
Pike doesn't support cygwin paths. If /cygdrive/x/foo gets handed to a file function it should instead use x:/foo (well, x:\foo). Could this be fixed in fdlib?
What does pike make of it? Does it try to access c:\cygdrive\x\foo (or whatever drive is the current one)?
/ Martin Stjernholm, Roxen IS
Previous text:
2004-03-20 08:13: Subject: cygwin days
I have successfully built Pike on cygwin. There are currently a few issues you have to get around.
Pike doesn't support cygwin paths. If /cygdrive/x/foo gets handed to a file function it should instead use x:/foo (well, x:\foo). Could this be fixed in fdlib?
Stdio.Terminfo can not decode the cygwin terminfo file. sizeof(strbuf)==sstr-2.
mt_lock( &aap_timeout_mutex ); in HTTPLoop/accept_and_parse.c triggers some sort of thread bug during startup. Just build without HTTPLoop.
/ Martin Nilsson (provokatör)
It appears I lack the strace ability to give a conclusive answer.
/ Martin Nilsson (provokatör)
Previous text:
2004-03-20 16:00: Subject: cygwin days
Pike doesn't support cygwin paths. If /cygdrive/x/foo gets handed to a file function it should instead use x:/foo (well, x:\foo). Could this be fixed in fdlib?
What does pike make of it? Does it try to access c:\cygdrive\x\foo (or whatever drive is the current one)?
/ Martin Stjernholm, Roxen IS
It doesn't work to make a file c:\cygdrive\foo\bar and then try to read it from hilfe with /cygdrive/foo/bar?
/ Martin Stjernholm, Roxen IS
Previous text:
2004-03-21 00:11: Subject: cygwin days
It appears I lack the strace ability to give a conclusive answer.
/ Martin Nilsson (provokatör)
The error you get from low_read_file is kind of funny.
Nilsson@Partikel /cygdrive/d/Pike/7.5/build/cygwin_nt-5.1-1.5.7_0.109_3_2_-i686 $ ./pike -mmaster.pike /cygdrive/d/Pike/7.5/src/object.c:491: Fatal error: low_read_file(master.pike) failed, short read: 116757 < 121065 No stack - no backtrace. Aborted (core dumped)
Nilsson@Partikel /cygdrive/d/Pike/7.5/build/cygwin_nt-5.1-1.5.7_0.109_3_2_-i686 $ ./pike -md:/pike/7.5/build/cygwin_nt-5.1-1.5.7_0.109_3_2_-i686/master.pike Pike v7.5 release 21 running Hilfe v3.5 (Incremental Pike Frontend)
/ Martin Nilsson (provokatör)
Previous text:
2004-03-21 00:18: Subject: cygwin days
No.
/ Martin Nilsson (provokatör)
In the last episode (Mar 21), Martin Nilsson (provokatr) @ Pike (-) developers forum said:
The error you get from low_read_file is kind of funny.
Nilsson@Partikel /cygdrive/d/Pike/7.5/build/cygwin_nt-5.1-1.5.7_0.109_3_2_-i686 $ ./pike -mmaster.pike /cygdrive/d/Pike/7.5/src/object.c:491: Fatal error: low_read_file(master.pike) failed, short read: 116757 < 121065 No stack - no backtrace. Aborted (core dumped)
This looks like the file is being accessed over a text mount. Are there 4308 lines in the file? What's the output of the "mount" command?
Right on target. 4308 lines.
$ mount C:\cygwin\bin on /usr/bin type system (textmode) C:\cygwin\lib on /usr/lib type system (textmode) C:\cygwin on / type system (textmode) c: on /cygdrive/c type user (textmode,noumount) d: on /cygdrive/d type user (textmode,noumount)
/ Martin Nilsson (provokatör)
Previous text:
2004-03-21 04:10: Subject: Re: cygwin days
In the last episode (Mar 21), Martin Nilsson (provokatr) @ Pike (-) developers forum said:
The error you get from low_read_file is kind of funny.
Nilsson@Partikel /cygdrive/d/Pike/7.5/build/cygwin_nt-5.1-1.5.7_0.109_3_2_-i686 $ ./pike -mmaster.pike /cygdrive/d/Pike/7.5/src/object.c:491: Fatal error: low_read_file(master.pike) failed, short read: 116757 < 121065 No stack - no backtrace. Aborted (core dumped)
This looks like the file is being accessed over a text mount. Are there 4308 lines in the file? What's the output of the "mount" command?
-- Dan Nelson dnelson@allantgroup.com
/ Brevbäraren
On Sun, Mar 21, 2004 at 12:15:02AM +0100, Martin Nilsson (provokatör) @ Pike (-) developers forum wrote:
It appears I lack the strace ability to give a conclusive answer.
AFAIK, at least in cygwin 1.5 this utility exists. Is something special needed to build Pike under cygwin? Or simle configure will do?
Regards, /Al
Yes strace exists, but it looks to me like Pike is reading the right file through some cygwin-internal path rewriter. But it obviously doesn't work, since Pike ends with a fatal. Doing the rewrite in Pike solves the problem.
/ Martin Nilsson (provokatör)
Previous text:
2004-03-21 01:43: Subject: Re: cygwin days
On Sun, Mar 21, 2004 at 12:15:02AM +0100, Martin Nilsson (provokatör) @ Pike (-) developers forum wrote:
It appears I lack the strace ability to give a conclusive answer.
AFAIK, at least in cygwin 1.5 this utility exists. Is something special needed to build Pike under cygwin? Or simle configure will do?
Regards, /Al
/ Brevbäraren
pike-devel@lists.lysator.liu.se
-
Alexander Demenshin -
Dan Nelson -
David Gourdelier -
Martin Nilsson (provokat�r) ＠ Pike (-) developers forum -
Martin Stjernholm, Roxen IS ＠ Pike developers forum