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] traceroute: fix 'no rule to make target -lm' error
Date: Sun, 4 Nov 2018 12:26:38 +0100	[thread overview]
Message-ID: <20181104122638.7103719d@windsurf> (raw)
In-Reply-To: <20181104114514.523365ee@windsurf>

Hello,

On Sun, 4 Nov 2018 11:45:14 +0100, Thomas Petazzoni wrote:

> We briefly discussed this patch during the Buildroot Developers
> meeting, and setting VPATH clearly cannot be the right solution, it's a
> big hack. A better solution needs to be found :)

Looking at http://autobuild.buildroot.net/?reason=traceroute% gives
some interesting details:

 - Until May 2018, the problem was happening with external toolchains.

 - Then, there's a big gap, with no traceroute failures at all

 - Since September 11, 2018, the problem started happening again, but
   this time around, only with internal toolchains

I looked at the commits on September 10/11, but couldn't spot anything
that looks obviously related. It is also not clear why the problem
disappeared on May 2018. However, back then, it was happening only on
Matt Weber build machine. Since September, with the internal
toolchains, it is happening on apparently all autobuilder machines.

Weird.

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

  reply	other threads:[~2018-11-04 11:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 22:37 [Buildroot] [PATCH] traceroute: fix 'no rule to make target -lm' error Sergio Prado
2018-11-04 10:45 ` Thomas Petazzoni
2018-11-04 11:26   ` Thomas Petazzoni [this message]
2018-11-05 15:25     ` Arnout Vandecappelle
2018-11-05 23:40       ` Arnout Vandecappelle
2018-11-06 10:07         ` Peter Korsgaard
2018-11-06 10:32           ` Arnout Vandecappelle
2018-11-07 21:08         ` Peter Korsgaard
2018-11-07 21:02 ` Peter Korsgaard
2018-11-25 20:51 ` Peter Korsgaard

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=20181104122638.7103719d@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