-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
Problem compiling under ppc64le #800
Comments
Just ignore this warning via -W flag ? Seems like your compiler is too strict here to compile BoringSSL |
Guess that requires editing build scripts, I'll try to find it. Thanks. |
Deleted all Werror I have found in pom.xml of the boringssl-static project that fails to compile, yet the error above still appears. From where it does pull that Werror flag? |
Maybe just add |
Cool, but where as it seems it ignored all my pom.xml changes. |
Add to the pom.xml. Maybe your compiler set some defaults. |
I think the problem is in the created build script that I have no control over in the pom:
|
It's as if I should edit generate |
I think I need to raise this with boringssl project. |
if you can provide a way for me to reproduce I might be able to help. I think it should be possible to fix this within our build scripts |
I think that would require providing a machine with this architecture, OS, and software versions? Architecture is the most problematic, I once tried qemu ppc64le on my x86-64 and it was slowing down to a crawl... Or maybe it would trigger as well on x86-64, as only software/OS causes it? |
Let's see first what boringssl people will say about it. |
Still it's puzzling, I understand the flags to compiler go via those *Flags variables but I can't see my added or removed flags affect the build:
|
Please show me the diff |
I think I have found it by correct backtracking. It seems to compile. Will soon show my diff. Thank you for persevering with amateurish me. |
So while removing Werror flags was easy (just search & replace), adding the no-error one in the right place was more tricky as it required finding the right place :) I have simply added it in wrong place yesterday (too many cflags variables all over the pom). |
Can this be added to upstream tcnative? Maybe even make it tied to this specific architecture/OS? |
I think we can just add it without tie to to a specific platform. Want to do a PR ? |
I finally have to do it for the first time, never did, and always end up like a pleb who doesn't know how to make a PR :) |
So give me a while please... |
Yes, was reading through that. I understand I need the fork variant, as I'm not able to create my own branch here? |
YesAm 20.07.2023 um 11:36 schrieb morvael ***@***.***>:
Yes, was reading through that. I understand I need the fork variant, as I'm not able to create my own branch here?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Motivation: We need ignore a warning when compiling on some platforms when building BoringSSL as otherwise the compilation fails. Modifications: Adds -Wno-error=stringop-overflow flag to BoringSSL compilation so that it starts working again on specific OS/architecture configuration. Result: Fixes #800
Note BoringSSL no longer supports ppcle64: |
@davidben thanks for clarify. |
I do not think I use it in any way, I just need tcnative project to compile, to later compile netty, and finally get epoll native jar with the linux-ppcle_64 classifier. @normanmaurer can I delete the forked repo now? |
For a long time I'm compiling each version of Netty (incl. tcnative) on my own, to create the missing epoll library for ppc64le. Upgraded from 4.1.86.Final to 4.1.94.Final (tcnative 2.0.61.Final) and it stopped compiling, because of Werror flag, which then breaks compilation after this warning:
OS:
CentOS Linux release 8.5.2111
Linux 4.18.0-348.7.1.el8_5.ppc64le #1 SMP Wed Dec 22 13:41:57 UTC 2021 ppc64le ppc64le ppc64le GNU/Linux
GCC:
gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)
The text was updated successfully, but these errors were encountered: