Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/gmpc: needs -lm
Date: Mon, 18 Nov 2019 23:42:38 +0100	[thread overview]
Message-ID: <20191118234238.363e7c04@gmx.net> (raw)
In-Reply-To: <df61ba8d-99d4-f16b-50ed-3e7ae28e4962@mind.be>

Hello *,

On Sun, 17 Nov 2019 21:54:38 +0100, Arnout Vandecappelle <arnout@mind.be> wrote:

> On 17/11/2019 21:48, Peter Seiderer wrote:
> > Hello *,
> >
> > On Sun, 17 Nov 2019 21:20:01 +0100, Peter Seiderer <ps.report@gmx.net> wrote:
> >
> >> Hello Arnout,
> >>
> >> On Sun, 17 Nov 2019 20:45:19 +0100, Arnout Vandecappelle <arnout@mind.be> wrote:
> >>
> >>> On 08/11/2019 22:28, Peter Seiderer wrote:
> >>>> Hello Fabrice, Thomas,
> >>>>
> >>>> On Fri, 8 Nov 2019 22:04:42 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> >>>>
> >>>>> 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 ?
> >>>
> >>>  It started because of RELRO, I think.
> >>>
> >>>>
> >>>> Maybe the same cause/problem as in the libv4l case regarding libatomic,
> >>>> evaluating vs. not evaluationg the *.la files (see [1])?
> >>>
> >>>  And this one because of PIC_PIE.
> >>
> >> Any hints to one/more related commits (so I can check by reverting if it
> >> changes/fix the problems)?
> >>
> >> Are the RELRO/PIC_PIE options related to evaluating *.la files?
> >
> > Did a quick search by the date (October 21, 2019) and the info from the libv4l
> > case [1] and would suspect the commit 'pkgconf: Add pkgconf system lib and
> > include path' [2], will do a test with this commit reverted....
>
>  Good point. Also there's a failure without PIC_PIE or RELRO [3].

Can confirm, reverting [2] fixes the libv4l and the gmpc linking problems...

Regards,
Peter

>
>  Regards,
>  Arnout
>
> >
> > Regards,
> > Peter
> >
> > [2] https://git.buildroot.net/buildroot/commit/?id=9cc8680fe54c0b8f5008158e36e2157127f03a7e
>
> [3]
> http://autobuild.buildroot.net/results/e7f/e7f37080c20e2131613517c3007b4569c28dbcf2
>
>
> >
> >>
> >> Regards,
> >> Peter
> >>
> >>>
> >>>  Regards,
> >>>  Arnout
> >>>
> >>>>
> >>>> Regards,
> >>>> Peter
> >>>>
> >>>> [1] http://lists.busybox.net/pipermail/buildroot/2019-October/264928.html
> >>>>
> >>>>>
> >>>>> 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
> >>>>
> >>>> _______________________________________________
> >>>> buildroot mailing list
> >>>> buildroot at busybox.net
> >>>> http://lists.busybox.net/mailman/listinfo/buildroot
> >>>>
> >>> _______________________________________________
> >>> buildroot mailing list
> >>> buildroot at busybox.net
> >>> http://lists.busybox.net/mailman/listinfo/buildroot
> >>
> >> _______________________________________________
> >> buildroot mailing list
> >> buildroot at busybox.net
> >> http://lists.busybox.net/mailman/listinfo/buildroot
> >
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2019-11-18 22:42 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 ` [Buildroot] [PATCH 1/2] package/gmpc: needs -lm Thomas Petazzoni
2019-11-08 21:28   ` 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 [this message]
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=20191118234238.363e7c04@gmx.net \
    --to=ps.report@gmx.net \
    --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