From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/qt5/qt5webengine: don't link with libstdc++.a on the host
Date: Sun, 31 May 2020 15:08:37 +0200 [thread overview]
Message-ID: <20200531150837.67abf9f9@windsurf.home> (raw)
In-Reply-To: <aa6f5047-3c91-e286-7bbe-29d26353b2c1@gmail.com>
On Fri, 29 May 2020 23:48:09 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> > If we have to pass this, doesn't it mean that the host tools are built
> > statically ? Why are they built statically ? They really shouldn't be
> > built statically at all. I believe this is what should be fixed, rather
> > than just avoiding specifically from linking statically with libstdc++.
>
> Without this option host tools are built statically because this option is
> enabled by default.
Can't we remove this, and instead link dynamically the host tools ?
> Adding --no-static-libstdc++ allow to link dynamically with libc.so.6.
--no-static-libstdc++ changes how we link against libc.so.6 ? Shouldn't
it only affect how we link against libstdc++.so ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-05-31 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 15:58 [Buildroot] [PATCH] package/qt5/qt5webengine: don't link with libstdc++.a on the host Romain Naour
2020-05-26 21:02 ` Romain Naour
2020-05-26 21:13 ` Peter Seiderer
2020-05-27 5:19 ` Romain Naour
2020-05-29 21:34 ` Thomas Petazzoni
2020-05-29 21:48 ` Romain Naour
2020-05-31 13:08 ` Thomas Petazzoni [this message]
2020-05-31 13:20 ` Romain Naour
2020-05-31 20:30 ` Yann E. MORIN
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=20200531150837.67abf9f9@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 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.