Skip to content
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

non-installed Rakudo can't be run from outside the build tree #1233

Closed
p6rt opened this issue Aug 18, 2009 · 7 comments
Closed

non-installed Rakudo can't be run from outside the build tree #1233

p6rt opened this issue Aug 18, 2009 · 7 comments

Comments

@p6rt
Copy link

p6rt commented Aug 18, 2009

Migrated from rt.perl.org#68636 (status was 'resolved')

Searchable as RT68636$

@p6rt
Copy link
Author

p6rt commented Aug 18, 2009

From @moritz

Since the ins2 branch merge, you can't run the non-installed 'perl6'
fakexecutable from anywhere else than the build tree.

$ ./rakudo/perl6 -e 'say "hi"'
Null PMC access in isa()
current instr.​: 'parrot;P6metaclass;register' pc 633
(runtime/parrot/library/P6object.pir​:430)
called from Sub 'perl6;Perl6Role;onload' pc 5091
(src/classes/Signature.pir​:412)
called from Sub '_block138' pc -1 ((unknown file)​:-1)

(this has been reported on IRC independently a few times on linux and MacOS)

Usually I'd just recommend installing Rakudo (which works from any
directory then), but there's a case where that doesn't work​:
Rakudo installs into the same --prefix directory as parrot, so if you
have a system wide parrot installation and no root privileges, you can't
get Rakudo running outside the build dir now.

So either the non-installed rakudo should be made to work, or rakudo's
Configure.pl should get its own (optional) --prefix to enable local
installs.

Cheers,
Moritz

@p6rt
Copy link
Author

p6rt commented Sep 26, 2009

From @pmichaud

The problem is that Rakudo needs to have its dynamic PMCs and opcodes
available in a place where the installed Parrot can find them. By
default the only places that Parrot looks is in its own installed
library directories and in the "dynext/" subdirectory of the current
working directory.

I don't know if it's possible for a .pbc file to change/extend Parrot's
defaults; even if it is, I'm not entirely sure how to get that
information encoded into the .pbc .

Pm

@p6rt
Copy link
Author

p6rt commented Sep 26, 2009

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Sep 26, 2009

From @pmichaud

On Sat Sep 26 10​:55​:52 2009, pmichaud wrote​:

The problem is that Rakudo needs to have its dynamic PMCs and opcodes
available in a place where the installed Parrot can find them.

BTW, these are the perl6_group.so and perl6_ops*.so files on Linux.

Pm

@p6rt
Copy link
Author

p6rt commented Oct 14, 2011

From @coke

On Tue Aug 18 01​:38​:48 2009, mlenz@​physik.uni-wuerzburg.de wrote​:

Since the ins2 branch merge, you can't run the non-installed 'perl6'
fakexecutable from anywhere else than the build tree.

$ ./rakudo/perl6 -e 'say "hi"'
Null PMC access in isa()
current instr.​: 'parrot;P6metaclass;register' pc 633
(runtime/parrot/library/P6object.pir​:430)
called from Sub 'perl6;Perl6Role;onload' pc 5091
(src/classes/Signature.pir​:412)
called from Sub '_block138' pc -1 ((unknown file)​:-1)

(this has been reported on IRC independently a few times on linux and
MacOS)

Usually I'd just recommend installing Rakudo (which works from any
directory then), but there's a case where that doesn't work​:
Rakudo installs into the same --prefix directory as parrot, so if you
have a system wide parrot installation and no root privileges, you can't
get Rakudo running outside the build dir now.

I don't think this is our problem. I think this is the user's problem.

I think having the user install their own copy if they don't have rights to
the system directory is a fine answer.

The perl5 community is encouraging users to avoid the system perl for a
variety of reasons, it's very easy to do with tools like perlbrew. We make
it very easy with Configure.pl.

So either the non-installed rakudo should be made to work, or rakudo's
Configure.pl should get its own (optional) --prefix to enable local
installs.

Cheers,
Moritz

--prefix now exists (though probably didn't when the ticket was opened)

I'll close this ticket in a few days unless I hear some objections.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Oct 20, 2011

From @coke

No objections, closing ticket.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Oct 20, 2011

@coke - Status changed from 'open' to 'resolved'

@p6rt p6rt closed this as completed Oct 20, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant