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

Configure failure of Rakudo Star Release 2017.04 on ARM #6213

Closed
p6rt opened this issue May 4, 2017 · 9 comments
Closed

Configure failure of Rakudo Star Release 2017.04 on ARM #6213

p6rt opened this issue May 4, 2017 · 9 comments
Labels

Comments

@p6rt
Copy link

p6rt commented May 4, 2017

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

Searchable as RT131255$

@p6rt
Copy link
Author

p6rt commented May 4, 2017

From 1parrota@gmail.com

Unfortunately, install processes is broken on ARM (R Pi). The
configure process has a compile failure. I've attached the output to
STDERR.

The offending code appears to be identical to the 2012.01 version,
which worked. Did someone change the compiler options?

@p6rt
Copy link
Author

p6rt commented May 4, 2017

From 1parrota@gmail.com

error_log

@p6rt
Copy link
Author

p6rt commented May 5, 2017

From @stmuk

With 2017.04 Rakudo Star you need to pass '--no-telemeh' to MoarVM
Configure.pl. You then also have to Configure.pl nqp and finally
rakudo itself.

On 4 May 2017 at 15​:41, Parrot Raiser <1parrota@​gmail.com> wrote​:

Unfortunately, install processes is broken on ARM (R Pi). The
configure process has a compile failure. I've attached the output to
STDERR.

The offending code appears to be identical to the 2012.01 version,
which worked. Did someone change the compiler options?

--
4096R/EA75174B Steve Mynott <steve.mynott@​gmail.com>

@p6rt
Copy link
Author

p6rt commented May 5, 2017

From @zoffixznet

On Thu, 04 May 2017 07​:41​:10 -0700, 1parrota@​gmail.com wrote​:

Unfortunately, install processes is broken on ARM (R Pi). The
configure process has a compile failure. I've attached the output to
STDERR.

The offending code appears to be identical to the 2012.01 version,
which worked. Did someone change the compiler options?

Yeah, there were some issues this release cycle. I recall the release manager mentioning he'll look into the ARM thing today ( somewhere in https://irclog.perlgeek.de/perl6/2017-05-04#i_14532819 )

@p6rt
Copy link
Author

p6rt commented May 5, 2017

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

@p6rt
Copy link
Author

p6rt commented May 5, 2017

From @zoffixznet

On Fri, 05 May 2017 02​:47​:02 -0700, cpan@​zoffix.com wrote​:

On Thu, 04 May 2017 07​:41​:10 -0700, 1parrota@​gmail.com wrote​:

Unfortunately, install processes is broken on ARM (R Pi). The
configure process has a compile failure. I've attached the output to
STDERR.

The offending code appears to be identical to the 2012.01 version,
which worked. Did someone change the compiler options?

Yeah, there were some issues this release cycle. I recall the release
manager mentioning he'll look into the ARM thing today ( somewhere in
https://irclog.perlgeek.de/perl6/2017-05-04#i_14532819 )

Oh, looks like there was a reply to this ticket but it ended up being another ticket​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=131256

@p6rt
Copy link
Author

p6rt commented May 7, 2017

From @stmuk

On Fri, 05 May 2017 02​:47​:02 -0700, cpan@​zoffix.com wrote​:

On Thu, 04 May 2017 07​:41​:10 -0700, 1parrota@​gmail.com wrote​:

Unfortunately, install processes is broken on ARM (R Pi). The
configure process has a compile failure. I've attached the output to
STDERR.

The offending code appears to be identical to the 2012.01 version,
which worked. Did someone change the compiler options?

Yeah, there were some issues this release cycle. I recall the release
manager mentioning he'll look into the ARM thing today ( somewhere in
https://irclog.perlgeek.de/perl6/2017-05-04#i_14532819 )

Can you try the script at

https://gist.github.com/stmuk/84b49fc92cba789e00112cf6c4ce9bfe

Cheers Steve

@p6rt
Copy link
Author

p6rt commented Jul 12, 2017

From @stmuk

This particular problem with MoarVM is now fixed

@p6rt
Copy link
Author

p6rt commented Jul 12, 2017

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

@p6rt p6rt closed this as completed Jul 12, 2017
@p6rt p6rt added the star 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