package/lua-curl: add variant definition of lcurl_url_t
PATCH v2 1/1 package/lua-curl: add variant definition of lcurl_url_t
Signed-off-by Francois Perrad <[email protected]>
--- ...dd-variant-definition-of-lcurl_url_t.patch | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 package/lua-curl/0001-add-variant-definition-of-lcurl_url_t.patch
package/lua-curl/0001-add-variant-definition-of-lcurl_url_t.patch new file +40 -0
@@ -0,0 +1,40 @@ +From 28ac0c5e642c9f7e3091a60268745f7cab4cc92b Mon Sep 17 00:00:00 2001 +From: Francois Perrad <[email protected]> +Date: Sat, 23 Feb 2019 15:23:26 +0100 +Subject: [PATCH] add variant definition of lcurl_url_t + +like in lceasy.h + +Signed-off-by: Francois Perrad <[email protected]> +--- + src/lcurlapi.h | 9 +++++++++ + 1 file changed, 9 insertions(+) + +diff --git a/Lua-cURLv3-0.3.9/src/lcurlapi.h b/Lua-cURLv3-0.3.9/src/lcurlapi.h +index 4dd4672..862c94f 100644 +--- a/Lua-cURLv3-0.3.9/src/lcurlapi.h ++++ b/Lua-cURLv3-0.3.9/src/lcurlapi.h +@@ -19,11 +19,20 @@ + + #if LCURL_CURL_VER_GE(7,62,0) + ++#if LCURL_CC_SUPPORT_FORWARD_TYPEDEF + typedef struct lcurl_url_tag { + CURLU *url; + + int err_mode; + }lcurl_url_t; ++#else ++struct lcurl_url_tag { ++ CURLU *url; ++ ++ int err_mode; ++}; ++#define lcurl_url_t struct lcurl_url_tag ++#endif + + int lcurl_url_create(lua_State *L, int error_mode); + +-- +2.17.1 +
Signature · 1 line
2.17.1
PATCH v2 1/1 package/lua-curl: add variant definition of lcurl_url_t
Hello Fran?ois,
Quoted 6 lines · On Sun, 24 Feb 2019 20:51:32 +0100 Francois Perrad <[email protected]> wrote:
Signed-off-by Francois Perrad <[email protected]>--- ...dd-variant-definition-of-lcurl_url_t.patch | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 package/lua-curl/0001-add-variant-definition-of-lcurl_url_t.patch
Your commit messages are really too terse, they should contain more details about the problem. I've extended the commit log and applied to master.
Also, I noticed that packages built by the luarocks infrastructure have code being built during the "installation to target" step, and nothing built in the normal "build" step. Is this expected ? Can this be fixed ?
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com