[PATCH 1/1] Fix compilation on armhf/Musl

[PATCH 1/1] Fix compilation on armhf/Musl

[Clayton Craft]

[-- Attachment #1: Type: text/plain, Size: 616 bytes --]

The following patch is needed to successfully build ofono on armhf with
musl (in place of libc)


diff --git a/gril/parcel.h b/gril/parcel.h
index e5592ae1..46887890 100644
--- a/gril/parcel.h
+++ b/gril/parcel.h
@@ -23,6 +23,7 @@
 #define __PARCEL_H

 #include <stdlib.h>
+#include <stdint.h>

 struct parcel {
        char *data;
diff --git a/plugins/gemalto.c b/plugins/gemalto.c
index 011713e6..45ec0cf9 100644
--- a/plugins/gemalto.c
+++ b/plugins/gemalto.c
@@ -25,6 +25,7 @@

 #include <errno.h>
 #include <stdlib.h>
+#include <stdint.h>

 #include <glib.h>
 #include <gatchat.h>

Re: [PATCH 1/1] Fix compilation on armhf/Musl

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 427 bytes --]

Hi Clayton,

On 09/08/2017 11:18 AM, Clayton Craft wrote:
> The following patch is needed to successfully build ofono on armhf with
> musl (in place of libc)
> 
> 

Applied.  Please note that I had to hand-apply this patch since it 
didn't apply cleanly.  Are you using the latest git?

Also, I split this into two commits per our Patch submission guidelines. 
  See 'HACKING' document in git.

Regards,
-Denis

Re: [PATCH 1/1] Fix compilation on armhf/Musl

[Clayton Craft]

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

>Applied.  Please note that I had to hand-apply this patch since 
>it didn't apply cleanly.  Are you using the latest git?

Hmm, I am using the latest git (well as of earlier this morning).


>Also, I split this into two commits per our Patch submission 
>guidelines.  See 'HACKING' document in git.

Shoot, I'm sorry. I will re-read the HACKING document :)

-Clayton


On Fri, Sep 08, 2017 at 12:11:52PM -0500, Denis Kenzior wrote:
>Hi Clayton,
>
>On 09/08/2017 11:18 AM, Clayton Craft wrote:
>>The following patch is needed to successfully build ofono on armhf with
>>musl (in place of libc)
>>
>>
>
>Applied.  Please note that I had to hand-apply this patch since 
>it didn't apply cleanly.  Are you using the latest git?
>
>Also, I split this into two commits per our Patch submission 
>guidelines.  See 'HACKING' document in git.
>
>Regards,
>-Denis