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 F<blib/lib> in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F<runtime/parrot/include/config.fpmc> and F<src/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
