Summary: | dev-qt/qtwebengine-6.8.3: TypeScript compilation failed (musl profile) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lucio Sauer <watermanpaint> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | ionen, watermanpaint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build log |
Description
Lucio Sauer
2025-04-25 08:12:01 UTC
Created attachment 926171 [details]
build log
Error doesn't say much, and built fine on musl when I last tested it (albeit it was 6.9.0 and a llvm-musl profile, but 6.8.3+gcc is fine too afaik). Do you see anything in `dmesg` if haven't rebooted since? Like a node segmentation fault, I ask given ninja is bad at reporting that this happened. TypeScript errors are likely related to net-libs/nodejs failing anyhow, that yours may be broken for some reason is my guess at the moment. (In reply to Ionen Wolkens from comment #2) > Error doesn't say much, and built fine on musl when I last tested it (albeit > it was 6.9.0 and a llvm-musl profile, but 6.8.3+gcc is fine too afaik). > > Do you see anything in `dmesg` if haven't rebooted since? Like a node > segmentation fault, I ask given ninja is bad at reporting that this happened. Sorry, nothing. I am running the musl installation in a lxd container on a glibc host. I don't know if that of interest. > TypeScript errors are likely related to net-libs/nodejs failing anyhow, that > yours may be broken for some reason is my guess at the moment. I'll rebuild nodejs and try compiling qtwebengine again. Guess it's possible lxd is influencing something, but I never used it. Were you able to build it successfully before? (aka qtwebengine-6.8.2 or so) Trying the stable version of nodejs could be interesting too, I think it's the one I used last time I tested musl+gcc (albeit on my llvm-musl, I have 22.14.0 and it works fine). Don't have much more ideas given error says nothing and reproducing may prove difficult. I don't test musl often though, and users rarely report issues to know if there's any "me too". (In reply to Ionen Wolkens from comment #4) > Guess it's possible lxd is influencing something, but I never used it. > > Were you able to build it successfully before? (aka qtwebengine-6.8.2 or so) > > Trying the stable version of nodejs could be interesting too, I think it's > the one I used last time I tested musl+gcc (albeit on my llvm-musl, I have > 22.14.0 and it works fine). Building with stable nodejs-22.13.1 worked! Thanks. |