Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] erlang: always use Buildroot's zlib
Date: Wed, 24 Oct 2018 13:58:25 +0200	[thread overview]
Message-ID: <87efcfblpa.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181012141149.72489-1-fhunleth@troodon-software.com> (Frank Hunleth's message of "Fri, 12 Oct 2018 10:11:49 -0400")

>>>>> "Frank" == Frank Hunleth <fhunleth@troodon-software.com> writes:

 > While Erlang includes a version of zlib, it's intended for Windows and
 > there's an expectation that non-Windows platforms provide it. It's also
 > not as regularly updated as the one in Buildroot. This change makes
 > Erlang always use a Buildroot-provided zlib.

 > Fixes this compile error:

 >  CC	/home/buildroot/autobuild/run/instance-0/output/build/erlang-21.0/erts/emulator/zlib/obj/x86_64-buildroot-linux-musl/opt/adler32.o
 > In file included from zlib/adler32.c:11:0:
 > zlib/zutil.h:172:39: error: "_LFS64_LARGEFILE" is not defined [-Werror=undef]
 >      (!defined(_LARGEFILE64_SOURCE) || _LFS64_LARGEFILE-0 == 0)
 >                                        ^~~~~~~~~~~~~~~~

 > See http://autobuild.buildroot.net/results/fc633f80c7c36a90e641487f5a888fbb767c2a54/.

 > Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>

Committed to 2018.02.x and 2018.08.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2018-10-24 11:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 14:11 [Buildroot] [PATCH 1/1] erlang: always use Buildroot's zlib Frank Hunleth
2018-10-14 20:48 ` Peter Korsgaard
2018-10-24 11:58 ` Peter Korsgaard [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=87efcfblpa.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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