From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4 v3] package/kvm-unit-tests: introduce _ARCH_SUPPORTS
Date: Mon, 10 Jul 2017 23:47:41 +0200 [thread overview]
Message-ID: <20170710234741.554c7a44@windsurf.lan> (raw)
In-Reply-To: <20170710162056.GB3014@scaer>
Hello,
On Mon, 10 Jul 2017 18:20:56 +0200, Yann E. MORIN wrote:
> > What about the x86_64 dependency on a host compiler >= 4.5 ?
>
> In the manual, it is said that one should not add a comment about a
> dependency on the host toolchain...
The manual says one thing, reality says another:
package/collectd/Config.in:comment "write_prometheus needs a toolchain w/ C++, host gcc >= 4.5"
package/cppcms/Config.in:comment "icu support needs a toolchain w/ gcc >= 4.8, host gcc >= 4.8"
package/icu/Config.in:comment "icu needs a toolchain w/ C++, wchar, threads, gcc >= 4.8, host gcc >= 4.8"
package/kodi/Config.in:comment "kodi needs python w/ .py modules, a uClibc or glibc toolchain w/ C++, locale, threads, wchar, dynamic library, gcc >= 4.8, host gcc >= 4.6"
package/mfgtools/Config.in.host:comment "mfgtools needs host gcc >= 4.8"
package/midori/Config.in:comment "midori needs libgtk3 and a glibc toolchain w/ C++, gcc >= 4.9, host gcc >= 4.8"
package/php/Config.ext:comment "intl support needs a toolchain w/ C++, wchar, threads, gcc >= 4.8, host gcc >= 4.8"
package/protobuf-c/Config.in:comment "protobuf-c needs a toolchain w/ C++, threads, host gcc >= 4.5"
package/python-mwscrape2slob/Config.in:comment "python-mwscrape2slob needs a toolchain w/ C++, gcc >= 4.8, host gcc >= 4.8"
package/python-pyicu/Config.in:comment "python-pyicu needs a toolchain w/ C++, gcc >= 4.8, host gcc >= 4.8"
package/python-slob/Config.in:comment "python-slob needs a toolchain w/ C++, gcc >= 4.8, host gcc >= 4.8"
package/qt5/qt5base/Config.in:comment "icu support needs a toolchain w/ gcc >= 4.8, host gcc >= 4.8"
package/qt5/qt5webkit/Config.in:comment "qt5webkit needs a toolchain w/ dynamic library, gcc >= 4.8, host gcc >= 4.8"
package/riemann-c-client/Config.in:comment "riemann-c-client needs a toolchain w/ C++, threads, host gcc >= 4.5"
package/webkitgtk/Config.in:comment "webkitgtk needs libgtk3 and a glibc toolchain w/ C++, gcc >= 4.9, host gcc >= 4.8"
I'm not sure why we would not add Config.in comment for dependencies on
the host toolchain. What's the reasoning for *not* adding such
dependencies ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-10 21:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 9:29 [Buildroot] [PATCH 0/4 v3] arch/arm: introduce big.LITTLE configurations Yann E. MORIN
2017-07-09 9:29 ` [Buildroot] [PATCH 1/4 v3] arch/arm: fix -mcpu default values for AArch64 Yann E. MORIN
2017-07-10 16:04 ` Thomas Petazzoni
2017-07-10 16:18 ` Tomov, Pavel
2017-07-10 16:22 ` Yann E. MORIN
2017-07-19 13:59 ` Peter Korsgaard
2017-07-09 9:29 ` [Buildroot] [PATCH 2/4 v3] package/kvm-unit-tests: introduce _ARCH_SUPPORTS Yann E. MORIN
2017-07-10 16:09 ` Thomas Petazzoni
2017-07-10 16:20 ` Yann E. MORIN
2017-07-10 19:56 ` Arnout Vandecappelle
2017-07-10 20:10 ` Yann E. MORIN
2017-07-10 20:12 ` Arnout Vandecappelle
2017-07-10 20:19 ` Yann E. MORIN
2017-07-10 21:47 ` Thomas Petazzoni [this message]
2017-07-10 21:57 ` Yann E. MORIN
2017-07-11 21:14 ` Arnout Vandecappelle
2017-07-22 21:28 ` Thomas Petazzoni
2017-07-22 21:49 ` Yann E. MORIN
2017-07-09 9:30 ` [Buildroot] [PATCH 3/4 v3] arch/arm: add big.LITTLE cpu variants Yann E. MORIN
2017-07-22 21:29 ` Thomas Petazzoni
2017-07-09 9:30 ` [Buildroot] [PATCH 4/4 v3] package/kvm-unit-test: available for big.LITTLE arm cores too Yann E. MORIN
2017-07-22 21:29 ` Thomas Petazzoni
2017-07-22 21:50 ` 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=20170710234741.554c7a44@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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.