-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Don't use -G to build shared object on Solaris #757
Comments
Having done a bit of research it looks like you're right about this, but I don't have solaris boxes where I could test it. The only thing I'm concerned about is whether the change might cause a regression in very old/obscure versions of Solaris. In other words, can we simply change Do you happen to know? |
Hi Michael,
Ah, OK. Just my 2 cents here... I help maintain some other libraries. My rule of thumb is, don't break the common case for the obscure case. Make the obscure case the special case so things "just work" for the common case. In this context, the common case is modern Solaris like 11.3 or 11.4, and the obscure case is Solaris 9. As far as testing, I can give you SSH access to my test machines. For Solaris I use 11.3 i86pc (x86_64). It is a Core i5 4th gen, so you have AES, RDRAND and AVX. I need your OpenCSW provides free access to Solaris 9 through Solaris 11 on both Sparc and i86pc. See Upstream Maintainers to request an account. I believe the GCC Compile Farm (Cfarm) provides access to the same machines via OpenCSW. gcc210 is Solaris 10/Sparc, and gcc211 is Solaris 11/Sparc. Accounts are free to FOSS developers. See Request an Account for the Cfarm. I advise against running Solaris in a VM. Use real hardware instead. Solaris' virtual memory manager is different than Linux. The Solaris memory manager does not oversubscribe memory, and allocations are always backed by RAM. So a Solaris guest is a hog that causes the host's memory manager to work extra hard when Solaris allocates big chunks of RAM. The host's disk i/o goes wild when the guest is Solaris.
Sorry, I'm not sure. And I should probably say, use |
For what it is worth, here is how I patch the hiredis recipe in my build scripts:
|
Yeah we're on the same page, and it certainly seems like Ideally we can make the change without breaking builds that are currently compiling although we have some leeway here since we're still pre 1.0.0. |
What do you think about the change in 23e3bd4. I can't use I'm somewhat concerned about the portability of |
Closing via #796 |
Please don't use
-G
to build the shared object on Solaris. Instead, use-shared
.Here's the result of using
-G
:The failed self-test showed up when testing Unbound.
The text was updated successfully, but these errors were encountered: