-
Notifications
You must be signed in to change notification settings - Fork 37
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
amd64 Void Linux musl build failed, same problem with gcc12 & llvm/clang12 #125
Comments
checked gcc6 available in the repos, looks like a very similar problem happens: gcc6-output.txt |
hmm.... gcc6 works fine for me on most systems, I don't know which other compiler did you attempt. |
How can you do the compiling with Musl? Could you share your mozconfig? |
I compile with the following mozconfig on 3.17 Alpine linux. Compilation fails for errors inside mozspell/hunspell.
|
|
You should be able to use my optimization string having -O2, tested on multiple platforms, then it disables specific optimisations which may cause issues (but don't anymore on gcc 13/gcc14 on Linux 64bit). Otherwise you can use -O1. |
@awilfox I was able to import certain header fixes, this improved situation on FreeBSD and OpenBSD where now a GCC build works (but not a clang build). The MUSL error was identical to the Clang. Still, worth a test if you want to check out dev with and without your fix.. |
Hi, a list of packages for that are needed to build in Alpine would be helpful ;) I'm about to try to compile ArcticFox yet again |
After several weeks experimenting with Pale Moon, it compiled, but didn't execute due to linking errors I assume (it was unable to find the liblgpllibs which lie in the same dir). I gave up and decided to try this browser, because I don't think Pale Moon devs will provide any help when I show them my config (too different from the default). So, I'm here, trying to build this browser with the following config, not too far from what is the default linux-amd64 in the repo:
With the following result (seems like it was truncated for some reason, but you can see the final error I suppose). I'm in no way an expert in C or C++, so I have no idea what is the problem here, but it was the same regardless of whether I used clang or gcc. I would prefer to use clang because it has more security hardening options, but if it can't be helped and I need gcc then sure, I will use it.
The text was updated successfully, but these errors were encountered: