From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/paho-mqtt-c: bump to version 1.3.2
Date: Tue, 28 Apr 2020 09:09:23 +0200 [thread overview]
Message-ID: <20200428090923.3841df3f@windsurf.home> (raw)
In-Reply-To: <CAPi7W83AsH8BEvr7yiUZAt=JdLnDQg+wL2K_bpbR-FuSM1RiVw@mail.gmail.com>
On Tue, 28 Apr 2020 08:31:35 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> > /home/buildroot/autobuild/instance-1/output-1/host/opt/ext-toolchain/bin/../lib/gcc/powerpc-buildroot-linux-uclibc/8.3.0/../../../../powerpc-buildroot-linux-uclibc/bin/ld: cannot find -lanl
> >
> > which I believe is only provided by glibc. Not sure what the fix is.
> > Making paho-mqtt-c depend on glibc would not be really nice.
> I fixed it upstream with:
> https://github.com/eclipse/paho.mqtt.c/commit/517e8659ab566b15cc409490a432e8935b164de8.
> I'll send a patch.
Excellent, thanks!
> It should be noted that that upstream has the "interesting" idea of
> deleting and recreating git release. For example, 1.3.2 has been
> "re-released" 20 hours ago. It could explain why the hash was wrong
> when this package was bumped.
Gah, very bad. Since you're in touch with upstream, perhaps you could
tell them that this is really bad, and why it is really bad?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-28 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 11:48 [Buildroot] [PATCH 1/1] package/paho-mqtt-c: bump to version 1.3.2 Julien Grossholtz
2020-04-21 19:36 ` Thomas Petazzoni
2020-04-28 5:38 ` Thomas Petazzoni
2020-04-28 6:31 ` Fabrice Fontaine
2020-04-28 7:09 ` Thomas Petazzoni [this message]
2020-04-28 9:21 ` Fabrice Fontaine
2020-05-07 20:57 ` 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=20200428090923.3841df3f@windsurf.home \
--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