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

Can't force a rebuild of nqp or vm's from rakudo's configure. #3510

Open
p6rt opened this issue Sep 8, 2014 · 2 comments
Open

Can't force a rebuild of nqp or vm's from rakudo's configure. #3510

p6rt opened this issue Sep 8, 2014 · 2 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Sep 8, 2014

Migrated from rt.perl.org#122734 (status was 'open')

Searchable as RT122734$

@p6rt
Copy link
Author

p6rt commented Sep 8, 2014

From @coke

When installing rakudo somewhere else on your system, we can't force a
rebuild of nqp or the vms without first removing the existing
installed copies (which means we have a period where we'd break the
usage of rakudo for any users on the box.)

The easiest solution I can think of is to add a --force option to
Configure.pl which would force nqp/vm's to be re-built and reinstalled
into the prefix directory, regardless of whether the installed
versions at that prefix were recent enough.

This would also avoid the issue of re-building a VM with different
config options. e.g. rebuilding rakudo-on-moar to use the JIT -
currently if you have a new enough version of moar installed, you
couldn't install a new one with a different JIT option without
removing the installed version first.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Apr 26, 2016

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

@p6rt p6rt added the build label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant