Currently Parrot is not building on Win32 using MSVC 2008
Will Coleda
will at coleda.com
Mon Jan 7 13:35:51 UTC 2013
ISTR that Reini changed the makefiles on windows to have backslashes
recently and probably missed this location when updating.
On Fri, Jan 4, 2013 at 10:38 PM, James E Keenan <jkeen at verizon.net> wrote:
> On 1/4/13 10:17 PM, Solinski, Mark wrote:
>
>> I don't know if this is the correct area to report this but Parrot
>> currently is not building on Win32 using MSVC 2008. I haven't built it in
>> a while but it used to build quite easily.
>>
>> I tracked the problem down to method _generate_guard_macro_name in
>> compilers/opsc/src/Ops/**Emitter.pm. The line:
>>
>> my @path := split('/', $filename);
>>
>> ...does not work as expected since the $filename passed in has
>> backslashes as directory separators and not forward slashes. I know that
>> this is a "Win32" thing but it is usually handled in other places. I
>> hacked _generate_guard_macro_name so that the backslash is treated like the
>> forward slash and are replaced with underscores in the guard name. Without
>> this hack the build chokes on the backslashes in the guard name of the
>> header files produced by ops2c for the dynoplibs like obscure_ops.h. With
>> the hack, the build completes and running "nmake test" produces no errors.
>>
>> BTW, googling "Parrot report defect" does not bring up anything useful
>> :(; what is the correct process for reporting defects? If more
>> information is required, I'd be happy to report it.
>>
>>
> You can start the ball rolling by filing a Git Issues ticket here:
>
> https://github.com/parrot/**parrot/issues/new<https://github.com/parrot/parrot/issues/new>
>
> (You might also want to subscribe to the parrot-tickets mailing list. Get
> there from lists.parrot.org.)
>
> Since you say that Parrot is not currently *building*, I'll assume that
> you never got as far as 'make test'.
>
> What you should do is post in that Issues ticket as much as possible of
> the full output of 'perl Configure.pl && make'.
>
> You can also go on IRC #parrot on irc.perl.org and see if anyone who
> builds on Win32 is around.
>
> HTH
>
> Jim Keenan
> ______________________________**_________________
> http://lists.parrot.org/**mailman/listinfo/parrot-dev<http://lists.parrot.org/mailman/listinfo/parrot-dev>
>
--
Will "Coke" Coleda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.parrot.org/pipermail/parrot-dev/attachments/20130107/23726dff/attachment.html>
More information about the parrot-dev
mailing list