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

rakudobrew build moar fail #6363

Closed
p6rt opened this issue Jun 26, 2017 · 6 comments
Closed

rakudobrew build moar fail #6363

p6rt opened this issue Jun 26, 2017 · 6 comments

Comments

@p6rt
Copy link

p6rt commented Jun 26, 2017

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

Searchable as RT131657$

@p6rt
Copy link
Author

p6rt commented Jun 26, 2017

From frank576frank576@gmail.com

rakudobrew build perl6 fail

platform :
Orange Pi PC (H3 Quad-core Cortex-A7 H.265/HEVC 4K)
DISTRIB_ID=Ubuntu 15.04 vivid

https://gist.github.com/freakcoco/7d4b7f634288b9534fd926d9f0316e9c

@p6rt
Copy link
Author

p6rt commented Jun 28, 2017

From @zoffixznet

On Mon, 26 Jun 2017 04​:45​:38 -0700, frank576frank576@​gmail.com wrote​:

rakudobrew build perl6 fail

platform :
Orange Pi PC (H3 Quad-core Cortex-A7 H.265/HEVC 4K)
DISTRIB_ID=Ubuntu 15.04 vivid

https://gist.github.com/freakcoco/7d4b7f634288b9534fd926d9f0316e9c

Hi,

Did you ever successfully install Perl 6 on this system in the past? Is it 32-bit?

Can you try installing a release instead of a dev commit​:

  rakudobrew build moar 2017.06

Cheers,
ZZ

@p6rt
Copy link
Author

p6rt commented Jun 28, 2017

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

@p6rt
Copy link
Author

p6rt commented Jun 28, 2017

From @timo

the problem here is that we have a flag to ensure gcc explodes at us
when we write code on linux that'd immediately explode on windows due to
MSVC being somewhat archaic, but that flag is also set for third-party
code, and since the arm dyncall stuff only gets tested once every few
months at best, we never noticed.

this most likely wants a fix that throws out the flag for third party
code in moarvm's repository

until then you could just remove all occurences of
-Werror=declaration-after-statement from all "Makefile" files and re-build

On 26/06/17 13​:45, é»�家å�� (via RT) wrote​:

# New Ticket Created by �家�
# Please include the string​: [perl #​131657]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=131657 >

rakudobrew build perl6 fail

platform :
Orange Pi PC (H3 Quad-core Cortex-A7 H.265/HEVC 4K)
DISTRIB_ID=Ubuntu 15.04 vivid

https://gist.github.com/freakcoco/7d4b7f634288b9534fd926d9f0316e9c

@p6rt
Copy link
Author

p6rt commented Jul 6, 2017

From @zoffixznet

On Wed, 28 Jun 2017 14​:45​:56 -0700, timo wrote​:

the problem here is that we have a flag to ensure gcc explodes at us
when we write code on linux that'd immediately explode on windows due to
MSVC being somewhat archaic, but that flag is also set for third-party
code, and since the arm dyncall stuff only gets tested once every few
months at best, we never noticed.

this most likely wants a fix that throws out the flag for third party
code in moarvm's repository

until then you could just remove all occurences of
-Werror=declaration-after-statement from all "Makefile" files and re-build

On 26/06/17 13​:45, é»�家å�� (via RT) wrote​:

# New Ticket Created by �家�
# Please include the string​: [perl #​131657]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=131657 >

rakudobrew build perl6 fail

platform :
Orange Pi PC (H3 Quad-core Cortex-A7 H.265/HEVC 4K)
DISTRIB_ID=Ubuntu 15.04 vivid

https://gist.github.com/freakcoco/7d4b7f634288b9534fd926d9f0316e9c

Moved this to MoarVM's ticket queue​: MoarVM/MoarVM#610

@p6rt
Copy link
Author

p6rt commented Jul 6, 2017

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

@p6rt p6rt closed this as completed Jul 6, 2017
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