You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Migrated from rt.perl.org#122734 (status was 'open')
Searchable as RT122734$
The text was updated successfully, but these errors were encountered: