Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/gmpc: needs -lm
Date: Fri, 8 Nov 2019 22:04:42 +0100	[thread overview]
Message-ID: <20191108220442.4b596996@windsurf> (raw)
In-Reply-To: <20191029214046.14722-1-fontaine.fabrice@gmail.com>

On Tue, 29 Oct 2019 22:40:45 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> gmpc forgets to link with -lm:
> 
> /home/buildroot/autobuild/instance-2/output-1/host/opt/ext-toolchain/bin/../lib/gcc/mips-linux-gnu/5.3.0/../../../../mips-linux-gnu/bin/ld: GmpcVolume.o: undefined reference to symbol 'ceil@@GLIBC_2.0'
> /home/buildroot/autobuild/instance-2/output-1/host/mips64el-buildroot-linux-gnu/sysroot/soft-float/el/lib64/libm.so.6: error adding symbols: DSO missing from command line
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/a79e0487135ad90530595d5c6ecc32f9c8cea7c4
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

We need to understand why this is happening now. This package has not
been modified since July 2017, but suddenly, on October 21, 2019, it
started failing like this. Why? Was there a change in one of the
dependencies, that is no longer linked with libm, and that causes this
problem ?

I think I already asked this in the past: when you fix an issue, don't
just fix the issue, but explain why the issue is happening, especially
in situations like these.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2019-11-08 21:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 21:40 [Buildroot] [PATCH 1/2] package/gmpc: needs -lm Fabrice Fontaine
2019-10-29 21:40 ` [Buildroot] [PATCH 2/2] package/gmpc: fix build with NLS Fabrice Fontaine
2019-11-08 21:04 ` Thomas Petazzoni [this message]
2019-11-08 21:28   ` [Buildroot] [PATCH 1/2] package/gmpc: needs -lm Peter Seiderer
2019-11-17 19:45     ` Arnout Vandecappelle
2019-11-17 20:20       ` Peter Seiderer
2019-11-17 20:48         ` Peter Seiderer
2019-11-17 20:54           ` Arnout Vandecappelle
2019-11-18 22:42             ` Peter Seiderer
2019-11-18 22:47               ` Thomas Petazzoni
2019-11-19 16:18                 ` Thomas Preston
2019-11-19 17:58                   ` Fabrice Fontaine
2019-11-19 18:31                     ` Thomas Preston
2019-11-19 18:42                     ` Peter Seiderer
2019-11-21 18:14                       ` Thomas Preston

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=20191108220442.4b596996@windsurf \
    --to=thomas.petazzoni@bootlin.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