A Floorp fork with custom branding and opinionated settings ๐ (mirrored from GitLab)
This constantly always fails to build because it cannot find the library its suppose to use for wasm32-wasi on a file called `'bits/socket.h'` I have `wasm32-sdk` installed, and the directory where that specific library points to IS in fact in `/usr/include/bits/socket.h` but according to `/usr/share/wasi-sysroot/include/wasm32-wasi/sys/socket.h:27:10` it says its not found. Now how that be? What sort of weird build system are we using here if it can't even find the file it needs from its own SDK? I have pretty much ever other WASI LLVM compiler runtime installed, so it shouldn't be having issues finding this file during compile time. --- Compile log ``` 0:55.04 In file included from /usr/share/wasi-sysroot/include/wasm32-wasi/arpa/inet.h:9: 0:55.04 In file included from /usr/share/wasi-sysroot/include/wasm32-wasi/netinet/in.h:10: 0:55.05 /usr/share/wasi-sysroot/include/wasm32-wasi/sys/socket.h:27:10: fatal error: 'bits/socket.h' file not found 0:55.05 27 | #include <bits/socket.h> 0:55.05 | ^~~~~~~~~~~~~~~ 0:55.05 1 error generated. ``` --- What even happened to the build pipeline? I can see it's failing on the Build Pipeline, and its been like this for months anything I try update or build FireDragon from the AUR repossess or build from source. I can compile Floorp browser from source just fine, but not for FireDragon. I think you should probably just drop wasm32-wasi from the build, because it's causing more issues than it's worth having, and you only really need it if you compiling for Windows platforms, and is just not needed on Linux. If you need it to compile for Windows, then it should be set as an Optional Dependency, and not require it when compiling on Linux. This will simplify the build source and reduce compile times, because the build pipeline will just keep failing if you don't.
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by alkaris2 and has received 2 comments.