From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] mfgtools: bump version to 1.2.91
Date: Sun, 26 May 2019 14:46:28 +0200 [thread overview]
Message-ID: <20190526144628.1f0a246a@windsurf> (raw)
In-Reply-To: <20190525141800.3991-1-bisson.gary@gmail.com>
Hello Gary,
On Sat, 25 May 2019 16:18:00 +0200
Gary Bisson <bisson.gary@gmail.com> wrote:
> NXP deprecated the old mfgtools code, also called mfgtools v2 although
> the releases were named v0.xx.
>
> It has been replaced by the Universal Update Utility (uuu), also called
> mfgtools v3 although the releases are named v1.x.yy.
>
> This new tool actually resides in the same repository in the master
> branch whereas the old one is now in a 'linux' branch.
>
> Since the old tool has issues building lately, let's switch to the new
> one. Note that uuu seems to be cleaner, supports much more features
> (i.MX8/8M/8QXP boot, fastboot etc..) and has a better documentation:
> https://github.com/NXPmicro/mfgtools/wiki
>
> Signed-off-by: Gary Bisson <bisson.gary@gmail.com>
Thanks for this patch. Unfortunately, it fails to build on my system,
with:
[100%] Linking CXX executable uuu
/usr/bin/ld: cannot find -lstdc++
collect2: error: ld returned 1 exit status
This is because it is passing -static-libstdc++ at link time, for some
odd reason.
Do you know why they are doing:
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -static-libstdc++ -static-libgcc")
in uuu/CMakeLists.txt. This seems pretty bogus for something that
should be just a regular user-space program.
Could you have a look into this ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-26 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 14:18 [Buildroot] [PATCH v2] mfgtools: bump version to 1.2.91 Gary Bisson
2019-05-26 12:46 ` Thomas Petazzoni [this message]
2019-05-26 17:10 ` Gary Bisson
2019-05-28 19:14 ` Jörg Krause
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=20190526144628.1f0a246a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.