-
Notifications
You must be signed in to change notification settings - Fork 2k
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
pkg/relic: Update to new upstream and remove now obsolete patches #6965
pkg/relic: Update to new upstream and remove now obsolete patches #6965
Conversation
pkg/relic/Makefile
Outdated
cd "$(PKG_BUILDDIR)" && perl $(PKG_DIR)/generate-cmake-xcompile.perl > comp-options.cmake | ||
|
||
$(PKG_BUILDDIR)/Makefile: $(PKG_BUILDDIR)/comp-options.cmake | ||
cd "$(PKG_BUILDDIR)" && COMP="$(filter-out -Werror=old-style-definition -Werror=strict-prototypes, $(CFLAGS) ) " cmake -DCMAKE_TOOLCHAIN_FILE=comp-options.cmake -DCHECK=off -DTESTS=0 -DBENCH=0 -DSHLIB=off -Wno-dev $(RELIC_CONFIG_FLAGS) . | ||
|
||
CFLAGS += -Wno-gnu-zero-variadic-macro-arguments -Wno-unused-function |
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.
you might want to have these CFLAGs to work around the compile errors?!
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.
@tfar any progress? I just tested and the only problem is with variadic-macros
, so if you (re)add the corresponding CFLAGS (as above) to disable the errors it works fine.
If you don't find the time right now to work on this, I'm willing to overtake - if you don't mind?
@tfar can you fix this? |
@smlng @cgundogan can we get this to move forward? |
pkg/relic/Makefile
Outdated
@@ -1,6 +1,6 @@ | |||
PKG_NAME=relic | |||
PKG_URL=https://github.com/relic-toolkit/relic.git | |||
PKG_VERSION=cdcfaeef101d18c3231c3b46359c519dd72682e8 | |||
PKG_URL=https://github.com/tfar/relic.git |
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.
@tfar would you be fine having the relic specific branch under the RIOT organization instead of keeping it in your private Github account? This way, every RIOT maintainer would have write access to it for future changes/fixes,
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.
Sure happy with that. Shall I clone it under the RIOT org?
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.
ping @cgundogan
Changed this to use upstream RELIC master, which should include the RIOT specific changes of my custom branch and #9241 . How about me rebasing this on master and then running the CI tests? |
@tfar yup, rebase + squash + a proper commit message (: |
5fe91e2
to
0e5d085
Compare
The removed patches have been applied upstream.
0e5d085
to
3288f7a
Compare
Squashed the changed. The needs squashing label can be removed. |
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.
ACK
Murdock finally agrees! GO |
No description provided.