New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Building Rakudo/Parrot on Mac OS X 10.5.6 (mixed perls) #733
Comments
From ck@ix.de-----BEGIN PGP SIGNED MESSAGE----- Hi, I'm trying to build rakudo/parrot (checked out from GIT about 10 minutes - -- Mindestinformationen im geschäftlichen E-Mail-Verkehr nach §37a HGB: Persönlich haftende Gesellschafterin: iD8DBQFJq5knYamCtkVm7roRAoCjAJ9TT786pzoGK1pWo/VzlNwfOgrYsQCfa43d |
From ck@ix.deduden:perl6 ck$ cd rakudo You can now use 'make' to build Rakudo Perl. /Users/ck/ix/0409/titel/perl6/rakudo/parrot/parrot /Users/ck/ix/0409/titel/perl6/rakudo/parrot/runtime/parrot/library/PGE/Perl6Grammar.pbc \ |
From @moritzOn Mon Mar 02 00:32:06 2009, ck@ix.de wrote:
In an off-list conversation Christian told me that he has two different I don't know where that came from. Usually parrot sticks to the perl Cheers, |
The RT System itself - Status changed from 'new' to 'open' |
From ck@ix.de-----BEGIN PGP SIGNED MESSAGE----- The bug seems to be due to two different Perl versions installed on the After changing the PATH so that the version in /usr/bin was used - -- Mindestinformationen im geschäftlichen E-Mail-Verkehr nach §37a HGB: Persönlich haftende Gesellschafterin: iD8DBQFJq7C2YamCtkVm7roRAjzlAJ0ZzqNsCC7M2ojm2DBgkeb1zL7yBACfYy4K |
From @cokeLooks like the original issue was diagnosed; I regularly build on darwin with no issues. If this is still an issue on recent rakudos, please let us know. Regards. -- |
1 similar comment
From @cokeLooks like the original issue was diagnosed; I regularly build on darwin with no issues. If this is still an issue on recent rakudos, please let us know. Regards. -- |
@coke - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#63584 (status was 'resolved')
Searchable as RT63584$
The text was updated successfully, but these errors were encountered: