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
make: *** [gen/moar/stage1/nqpmo.moarvm] Segmentation fault #81
Comments
|
I installed a openSUSE 13.1 x86_64 in a virtualbox VM an I am unable to reproduce your issue. Is there a way I can get your build scripts/tools? I'd need a short guide though since I am not familiar with any of these. |
I just checked in revision 5 which only updates the source archive and bumps the version number from 2014.01 to 2014.02, no functional change in specfile/patches or similar, so that you can simply check it out and run the build.
https://en.opensuse.org/openSUSE:Build_Service_Tutorial#Perform_the_local_build |
|
I just get the following: |
|
okay, got around that... |
|
good news: |
|
How can I make it build moarvm/nqp HEAD? |
|
Just replace the source tarball, |
|
Okay, so I branched our moarvm repo, updated to 2014.04 and adapted the spec file. After that I committed my changes. Now I want to branch nqp to do the same, but: |
|
I'd love to trigger a rebuild... https://build.opensuse.org/package/show/home:froggs:branches:home:ldieckow:branches:devel:languages:parrot/moarvm |
|
This is getting complex :/ |
|
@daxim I know what is wrong now -.- It looks like we are compiling against a version of libuv and then linking against another one. (Or perhaps we compile with CFLAGS set which were not in place when libuv was built). I made a test by stripping moarvm.spec a bit by letting it link against these libs statically. This way I can build nqp, so I guess I am able now to debug that now on my machine. Probably the solution is to remove libuv's, linenoise's and dyncall's headers from MoarVM repository, and use the headers of the installed libs... Btw, it seems like my branch https://build.opensuse.org/project/show/home:froggs:branches:home:ldieckow:branches:devel:languages:parrot causes problems to your nqp, the page at https://build.opensuse.org/package/show/home:ldieckow:branches:devel:languages:parrot/nqp shows a conflict. |
|
Or perhaps the more sane solution is to link these three libs statically, and just not to install their header files. Because we keep libuv at a certain version (v0.11.19), and you provide v0.11.21. |
|
See #123, both seem to be because of the same problem, and hopefully fixed now. |
|
Due to changes in the upstream devel:languages:parrot build project, I don't have a working build environment for repro anymore. Due to #123, I believe it's fixed, closing. |
nqp build log:
FROGGS requested moarvm details:
build log https://build.opensuse.org/package/live_build_log/home:ldieckow:branches:devel:languages:parrot/moarvm/openSUSE_13.1/x86_64
spec file https://build.opensuse.org/package/view_file/home:ldieckow:branches:devel:languages:parrot/moarvm/moarvm.spec?expand=1
packages http://software.opensuse.org/download.html?project=home%3Aldieckow%3Abranches%3Adevel%3Alanguages%3Aparrot&package=moarvm
The text was updated successfully, but these errors were encountered: