| 30 Mar 2026 | |||
| timo | i'll try a simple modification of an opensuse one i still have here | 21:26 | |
| grayeul | I am running a build using 'mock' -- if you have access to that, it might not be too hard. | 21:28 | |
| I'm wondering if something went wrong when I built moarvm -- and the problem is there -- but it seems like that ran without problem. | |||
| timo | is the /usr/bin/moar the moar you have just built? | 21:31 | |
| grayeul | I can possibly see about getting a container of some sort setup.... but I'm about out of juice, after messing with this most of the day.... I'll try doing that tomorrow and report back here... | ||
| timo | i have a Containerfile that successfully compiles and installs a moarvm and nqp | ||
| grayeul | Yes, I think so... I built that into an rpm first... and then have installed that rpm into the chroot where I'm working to build nqp | ||
| timo | gist.github.com/timo/61cc9129b7c6d...80f810e680 | 21:32 | |
| grayeul | if you have any environment based on rpm.... I could certainly get you that rpm (for moarvm) -- and then possibly you could try it. | ||
| timo | i do have a rocky linux 10 container that i was using to look for the cause of the crashes in Sparrow6 | 21:35 | |
| not container, VM. | |||
| i would prefer getting the srpm over the rpm probably, but having the rpm that gives that error could be interesting too | 21:36 | ||
| grayeul | all seemed to be working (for this...) on rocky10 | 21:37 | |
| timo | build log in the gist | ||
| ah right, i wouldn't be able to see the problem on 10 anyway then | |||
| i am chronically short on SSD space :( | |||
| can you also give me more of the output? maybe including the build of the moarvm package as well? | 21:38 | ||
| grayeul | yeah... I'm not sure if this is helpful or not -- but you could look at: copr.fedorainfracloud.org/coprs/gr...oj/builds/ and I think you can see the build logs, etc for moar, and the failed one for nqp | 21:39 | |
| or you can see the moar build log (successful) here: rpa.st/7MCDU | 21:41 | ||
| and the failed nqp build here: rpa.st/6T6EA | 21:42 | ||
| timo | --no-silent-build for nqp would be helpful to get the executed commands in the output | 21:51 | |
| grayeul | I'll see what I can do -- but probably not until tomorrow... thanks for taking the time to look.. | 21:52 | |
| timo | sure | ||
| the "illegal option" is a reaction to when the given option isn't found in a hash, maybe something's really wrong with hashes for some reason? | 21:53 | ||
| [Coke] | FYI, we did just release 2026.03 | ||
| don't expect it to fix your issues, but might as well use the latest one. | 21:54 | ||
| grayeul | OK -- I think I kicked off another build on copr, with the --no-silent-build option... but sometimes it takes a while to get a builder. | 21:56 | |
| I did see that you had released 2026.03 -- but (after successfully building moarvm/nqp/rakudo on rocky10) -- when I tried 2026.03 that failed with a different error (on 10). I figured I'd stick with 2026.02 to get going on 9, then go back and see what was up with 2026.03.... | 21:58 | ||
| timo | huh. | ||
| well, that doesn't bode well | |||
| copr-dist-git.fedorainfracloud.org...oarvm.git/ should i be able to see this? gives me a 500 internal server error | 21:59 | ||
| grayeul | well, I'm pretty sure... it did -- can't seem to find that build right now, so I need to re-check. | ||
| timo | but i can see the log of the ongoing build live in front of me now | 22:01 | |
| grayeul | no -- that's not a valid URL -- I'm fairly new to copr, so haven't figured out how to navigate everywhere... but, on the main project page you should see the cmd: `#> dnf copr enable grayeul/TestProj` which should let you enable that as a repository, then can use dnf commands to pull down git/x86_64 rpms. | ||
| [Coke] | grayeul: makes sense, thanks. | 22:02 | |
| timo | ok, it does look like the output from --no-silent-build is what we would expect | ||
| grayeul | I think there is also a Download repo button at: #> dnf copr enable grayeul/TestProj that will give you a .repo file that can be used. You might have some luck with that. | ||
| already failed in the same way I see.... | 22:03 | ||
| ok -- I'm done for today.... cya | |||
| [Coke] | ~~ | ||
| Thanks for bringing this to us! | |||
| timo | gnite | ||
| 31 Mar 2026 | |||
| patrickb | Quick status update: I have any-break support (i.e. break on all possible break positions) working in the debug server. Next: hunt an occasional dead lock or seg fault in moar I observe about 1 in 4 times during startup of a debug session. | 09:06 | |
| tellable6 | 2026-03-28T21:26:47Z #raku-dev <[Coke]> patrickb 2026.03 is ready for binary releases. | ||
| librasteve_ | rakudoweekly.blog/2026/03/31/2026-...lease-191/ | 11:37 | |
| grayeul | timo: (and others) - I've modified your container file for building moarvm/nqp and changed it to be more like the rpm build I'm trying to work out. One of the main diffs is relying on installed rpms for the 3rdparth dependencies. Maybe there are some version differences there that are having an impact. | 15:42 | |
| In any case, with this file: gist.github.com/grayeul/b9e6d1fe45...67ee7df9cb which tries to build 2026.03 -- even on Rocky9 I'm getting the error I mentioned the other day. `/usr/bin/ld: ./libmoar.so: undefined reference to `mp_expt_n'` | 15:43 | ||
| So, I'm also using 'mock' to build the rpm from a src.rpm. And when I do that for moarvm.2026.02 it works (at least without error) but when I try using the above container for 2026.02, I get an error that it can't find /usr/bin/moar when it tries to run a chmod. It didn't seem to complain about building or copying moar to /usr/bin -- and I don't see that error with mock, so not sure what is up with that. | 15:46 | ||
| ah -- I now see in the 2026.03 changelog, that libtommath requirement is 1.3.0 -- and Rocky9 only has 1.2.0 and 2026.03 says it requires mimalloc 2.2.7, which is not available (via std repos) for Rocky9 *or* Rocky10 | 15:59 | ||
| Update: gist.github.com/grayeul/d0d395e2a8...55ec22c7f1 shows a container build that appears to succeed for moarvm, but fails for nqp on Rocky9 (timo: this is what you asked for yesterday) | 16:23 | ||
| [Coke] | ah, you're not building 3rdparty/ but are using system versions? we could also have modifications in our versions (but not sure if we do) | 16:38 | |
| grayeul | right -- but trying to determine if/where that is a specific problem.... | 16:59 | |
| I could potentially build static versions... and include whatever 3rdparty stuff is in your submodules... seemed 'cleaner' (but not necessarily easier) to use system-provided versions. But that *will* make it harder to update when dependencies change. | 17:01 | ||