Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] erlang: bump to version 20.0
Date: Tue, 05 Dec 2017 20:34:59 +0100	[thread overview]
Message-ID: <309jfexdr8.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: CAJtjsKYbRp-NcBxLfc-Xner7TUQuA8i3EjuR0QXgq908+Nwt6w@mail.gmail.com

Am Mon, 04 Dec 2017 17:32:31 +0100 schrieb Johan Oudinet:

> What bother me is that I can't find which changes from OTP 19.3 to OTP
> 20.0 could lead to this error.

Hi,

I think I found the commit, added with version 20.0, which causes the 
error: https://github.com/erlang/otp/
commit/640c988fd41f9709b494554b2e5ef1f06f06957e

The autoconf function AC_SEARCH_LIBS adds "-llibrary to LIBS for the 
first library found to contain function" according to the autoconf manual:
https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/
Libraries.html

And this is exactly what happens:

host-erlang-20.0/erts/config.status contains

S["LIBS"]="-lz -lutil -ldl -lm   "

while host-erlang-19.3/erts/config.status lacks -lz:

S["LIBS"]="-lutil -ldl -lm   "

The content of this variable is used to build dyntrace.o with this 
Makefile: lib/runtime_tools/c_src/Makefile.in, line 98.

Unfortunately I do not have more time to look for a fix today.

Regards, Bernd

  reply	other threads:[~2017-12-05 19:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 15:42 [Buildroot] [PATCH 1/1] erlang: bump to version 20.0 Johan Oudinet
2017-11-30 16:31 ` Frank Hunleth
2017-12-01  8:20   ` Thomas Petazzoni
2017-12-01 15:16   ` Johan Oudinet
2017-12-01 15:43     ` Frank Hunleth
2017-12-01 21:46 ` Thomas Petazzoni
2017-12-03  9:59 ` Thomas Petazzoni
2017-12-04 16:32   ` Johan Oudinet
2017-12-05 19:34     ` Bernd Kuhls [this message]
2017-12-06 11:11       ` Johan Oudinet
2017-12-06 14:23     ` Thomas Petazzoni
2017-12-04 17:49   ` Bernd Kuhls
2017-12-05 16:52     ` Johan Oudinet

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=309jfexdr8.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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