-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Android Things 1.06 with Termux changes #3312
Conversation
configure.ac
Outdated
@@ -89,6 +89,8 @@ fi | |||
# Check whether to build a with debug symbols | |||
LIBZMQ_CHECK_ENABLE_DEBUG | |||
|
|||
AC_CHECK_LIB([atomic],[__atomic_load_4],[LIBS="${LIBS} -latomic"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will always enable this linking, which is not right. There's a section that checks the host os, and looks for android, you should add it there instead with the appropriate checks for "android things"
thanks - please send a separate PR with a relicensing grant, see bottom of PR template: https://github.com/zeromq/libzmq/blob/master/.github/PULL_REQUEST_TEMPLATE.md |
actually I double checked, and there's already an m4 test to see if linking to latomic is needed, so check the log instead and see why it is not triggering: https://github.com/zeromq/libzmq/pull/3083/files |
Can I reply in this email? Is there a stakeholder for the tipc change? I
don’t see a way to test the positive case (when tipc is present)
…On Wed, Nov 21, 2018 at 12:00 PM Luca Boccassi ***@***.***> wrote:
actually I double checked, and there's already an m4 test to see if
linking to latomic is needed, so check the log instead and see why it is
not triggering: https://github.com/zeromq/libzmq/pull/3083/files
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3312 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGPPbhRLV1JCtAPtp9fwZPUjRjTBf5E4ks5uxYamgaJpZM4YsUnb>
.
|
the tipc change is fine, it's the latomic one that is not as it overwrites the work done by the linked pr in acinclude.m4 |
from configure which means this should be triggered. [AC_MSG_RESULT(yes) ; libzmq_cv_has_atomic_instrisics="yes" LIBS="-latomic" ; $1], My understanding is in the current version LIBS= was factored into the test case in the new change? https://github.com/PIDriverAssist/libzmq/blob/4f48c5615ecbbd70423e163151a3448e75570f99/acinclude.m4#L694 changed at If you can confirm my perception, a thought is to reinstate setting LIBS under condition that linking is not static? |
LIBS is already been set (or rather, it's not reset back if it's needed), so the problem must be something else |
if you build with make V=1 what's the actual content of *FLAGS? |
|
are you passing all the cross compilation flags for autoconf? |
I'm compiling on device. Would they be relevant? (Termux on android) |
I'm not sure. I don't have the device to try it, so I'll merge as-is. |
Thank you. I think we will need another iteration as we understand this more. I'm thinking the branches should condition upon presence of atomic intrinsic and whether or not libzmq is statically compiled [based upon the notes] (none of this logic is encapsulated by lower level tools?) but I will read more to confirm this. |
Ok, feel free to send more pull requests |
* include atomic when needed * update for tipc * moved check under android * added license
Please consider the following changes to the configuration scripts. After making the changes below ( macro to check for libatomic and enhanced verification for tipc[I don't have a tipc unit to verify with but inserted the line that was causing an error on this configuration into configure.ac]) I was able to compile with termux under Android 1.06 and succesfully use test cases
[still had to manually change configure script to use bash in this context but think that may normally be encapsulated in termux build scripts]
./configure --prefix=/data/data/com.termux/files/usr
This effort was necessitated to recompile libzmq from scratch in support of addressing this issue zeromq/pyzmq#1240