Re: Current State of Building Parrot on Cygwin
Eric Hanchrow wrote: Ron == Ron Blaschke [EMAIL PROTECTED] writes: Ron If you see this error ... Ron the file has Windows line endings Dare I suggest that parrot not be so fussy about line endings? I second that. ;) Actually, both things are supposed only as workarounds until fixed, to get Parrot fly on Cygwin again, if only with a broken wing. Ron
Re: Current State of Building Parrot on Cygwin
Steve Peters wrote: On Sun, Apr 01, 2007 at 04:15:24PM +0200, Ron Blaschke wrote: As recently discussed it is currently necessary to include the absolute path to Fblib/lib in the environment variable PATH. This should be done before trying to built parrot, otherwise one gets a broken Fruntime/parrot/include/config.fpmc and Fsrc/parrot_config.c. One needs a make clean or remove *both* files before trying again. Make sure to export the PATH changes, not just only set them, and use the absolute path, not the relative (otherwise building some libs will fail later on.) I was beginning to think that was the problem with Cygwin. With Perl 5, the build process keeps all the Perl library in the same directory with executable. This seems to make things much easier for Windows, since DLL's need to be on the PATH on Windows (including Cygwin). Once I reboot into Windows, I'll see what I can do to help make this more automatic. See my Link'n'Load on Windows post for more thoughts. If you're interested, here's how Windows loads DLLs. Dynamic-Link Library Search Order http://msdn2.microsoft.com/en-us/library/ms682586.aspx Ron
Re: Current State of Building Parrot on Cygwin
chromatic wrote: On Sunday 01 April 2007 07:15, Ron Blaschke wrote: As recently discussed it is currently necessary to include the absolute path to Fblib/lib in the environment variable PATH. This should be done before trying to built parrot, otherwise one gets a broken Fruntime/parrot/include/config.fpmc and Fsrc/parrot_config.c. One needs a make clean or remove *both* files before trying again. Make sure to export the PATH changes, not just only set them, and use the absolute path, not the relative (otherwise building some libs will fail later on.) Is it possible to pass flags to the linker that hint at a path to libparrot.so? That's how the Linux version works anyway. And that's quite convenient. Haven't seen anything similar on Windows, though. Ron
Current State of Building Parrot on Cygwin
Hi, As recently discussed it is currently necessary to include the absolute path to Fblib/lib in the environment variable PATH. This should be done before trying to built parrot, otherwise one gets a broken Fruntime/parrot/include/config.fpmc and Fsrc/parrot_config.c. One needs a make clean or remove *both* files before trying again. Make sure to export the PATH changes, not just only set them, and use the absolute path, not the relative (otherwise building some libs will fail later on.) If you see this error make runtime/parrot/library/Crow.pbc ./parrot.exe -o runtime/parrot/library/Crow.pbc runtime/parrot/library/Crow.pir error:imcc:syntax error, unexpected $end in file 'runtime/parrot/library/Crow.pir' line 146 make: *** [runtime/parrot/library/Crow.pbc] Error 1 the file has Windows line endings, usually because checked out with Windows' Subversion. Get the Cygwin version and a clean checkout. Ron
Re: Current State of Building Parrot on Cygwin
Ron == Ron Blaschke [EMAIL PROTECTED] writes: Ron If you see this error ... Ron the file has Windows line endings Dare I suggest that parrot not be so fussy about line endings? -- If you're trying to choose between two theories and one gives you an excuse for being lazy, the other one is probably right. -- Paul Graham
Re: Current State of Building Parrot on Cygwin
On Sun, Apr 01, 2007 at 04:15:24PM +0200, Ron Blaschke wrote: Hi, As recently discussed it is currently necessary to include the absolute path to Fblib/lib in the environment variable PATH. This should be done before trying to built parrot, otherwise one gets a broken Fruntime/parrot/include/config.fpmc and Fsrc/parrot_config.c. One needs a make clean or remove *both* files before trying again. Make sure to export the PATH changes, not just only set them, and use the absolute path, not the relative (otherwise building some libs will fail later on.) If you see this error make runtime/parrot/library/Crow.pbc ./parrot.exe -o runtime/parrot/library/Crow.pbc runtime/parrot/library/Crow.pir error:imcc:syntax error, unexpected $end in file 'runtime/parrot/library/Crow.pir' line 146 make: *** [runtime/parrot/library/Crow.pbc] Error 1 the file has Windows line endings, usually because checked out with Windows' Subversion. Get the Cygwin version and a clean checkout. I was beginning to think that was the problem with Cygwin. With Perl 5, the build process keeps all the Perl library in the same directory with executable. This seems to make things much easier for Windows, since DLL's need to be on the PATH on Windows (including Cygwin). Once I reboot into Windows, I'll see what I can do to help make this more automatic. Steve Peters [EMAIL PROTECTED]
Re: Current State of Building Parrot on Cygwin
On Sunday 01 April 2007 07:15, Ron Blaschke wrote: As recently discussed it is currently necessary to include the absolute path to Fblib/lib in the environment variable PATH. This should be done before trying to built parrot, otherwise one gets a broken Fruntime/parrot/include/config.fpmc and Fsrc/parrot_config.c. One needs a make clean or remove *both* files before trying again. Make sure to export the PATH changes, not just only set them, and use the absolute path, not the relative (otherwise building some libs will fail later on.) Is it possible to pass flags to the linker that hint at a path to libparrot.so? That's how the Linux version works anyway. -- c
