From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] traceroute: fix 'no rule to make target -lm' error
Date: Tue, 06 Nov 2018 11:07:08 +0100 [thread overview]
Message-ID: <87pnvibjub.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <51e4e1aa-c4c8-0353-dbfa-722756a49f71@mind.be> (Arnout Vandecappelle's message of "Tue, 6 Nov 2018 00:40:38 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
> Muhaha. In other words, -lNAME dependencies are broken for cross-compilation!
> Indeed, this is coded like this in make (remake.c):
Yes :/
At least I think that they are fairly rarely used.
> Bottom line: it looks like Sergio's patch is indeed correct, and moreover, it
> looks like it might be better to add it to TARGET_MAKE_ENV. Note sure if we want
> to take the risk at this point to make such a landslide change?
I am about to cut -rc1, so I don't want to do it on master. I suggest we
merge Sergio's patch (with the above description) and then create a new
patch for next to add it globally to TARGET_MAKE_ENV.
OK?
>> I guess that that is completely unrelated though.
> So this is completely unrelated: it is because the way glob is used in make is
> incompatible with glibc-2.28. But since any distro which has glibc-2.28 also has
> make >= 4.0, it's not so important to fix I guess. OTOH it's just a simple
> upstream patch.
Ok, so not really that important. I'm fine with either adding the patch
or just waiting for the next make bump (that will presumably include
it).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-11-06 10:07 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
2018-11-05 15:25 ` Arnout Vandecappelle
2018-11-05 23:40 ` Arnout Vandecappelle
2018-11-06 10:07 ` Peter Korsgaard [this message]
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=87pnvibjub.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