Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/socat: fix musl build
Date: Tue, 26 Jan 2016 22:43:40 +0100	[thread overview]
Message-ID: <20160126224340.14a8a5bc@free-electrons.com> (raw)
In-Reply-To: <1453636704-20771-1-git-send-email-bernd.kuhls@t-online.de>

Bernd,

On Sun, 24 Jan 2016 12:58:24 +0100, Bernd Kuhls wrote:

> +--- socat-1.7.2.4.orig/sysincludes.h
> ++++ socat-1.7.2.4/sysincludes.h
> +@@ -134,7 +134,7 @@
> + #include <netpacket/packet.h>
> + #endif
> + #if HAVE_NETINET_IF_ETHER_H
> +-#include <netinet/if_ether.h>
> ++#include <linux/if_ether.h>

This looks wrong: the configure check now verifies if
<netinet/if_ether.h> exists, if that's the case,
HAVE_NETINET_IF_ETHER_H is defined, but the code includes
<linux/if_ether.h> ? Not good.

> diff --git a/package/socat/0003-netdb-internal.patch b/package/socat/0003-netdb-internal.patch
> new file mode 100644
> index 0000000..44bd65f
> --- /dev/null
> +++ b/package/socat/0003-netdb-internal.patch
> @@ -0,0 +1,20 @@
> +Fix musl build
> +
> +Downloaded from
> +http://git.alpinelinux.org/cgit/aports/tree/main/socat/netdb-internal.patch
> +
> +Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> +
> +--- socat-1.7.2.4.orig/compat.h
> ++++ socat-1.7.2.4/compat.h
> +@@ -656,6 +656,10 @@
> + #  define NETDB_INTERNAL h_NETDB_INTERNAL
> + #endif
> + 
> ++#if !defined(NETDB_INTERNAL)
> ++#  define NETDB_INTERNAL (-1)
> ++#endif

This also looks suspicious, and at the very least needs some proper
patch description.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-01-26 21:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 11:58 [Buildroot] [PATCH 1/1] package/socat: fix musl build Bernd Kuhls
2016-01-26 21:43 ` Thomas Petazzoni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160126224340.14a8a5bc@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox