From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Knowing whether the target is multicore
Date: Wed, 11 Dec 2013 07:35:20 +0200 [thread overview]
Message-ID: <20131211053520.GD1217@tarshish> (raw)
In-Reply-To: <CA+-urNRh5WARfiTZXAiULdXmxTErbdJSGWTnRHjiTr_uEyEoeA@mail.gmail.com>
Hi Frank,
On Tue, Dec 10, 2013 at 04:55:37PM -0500, Frank Hunleth wrote:
> From what I can tell, the answer is no, but I was wondering if there
> was any way of knowing in a package's .mk file whether the target is
> single or multicore.
>
> The reason that I'm asking is that I'm currently working with the
> Erlang package. The Erlang configure script can be told whether to
> build a VM that supports multi-core or not. By default, it builds VMs
> for both cases. This works, but takes quite a bit longer to compile
> and adds to the target image size. I'd like to be able to set this
> appropriately, and it seems like this would be better accomplished
> using an arch-specific BR2_ variable rather than something in the
> Erlang package's Config.in.
Whether a target is SMP or not depends on architecture and kernel
configuration, and that might be outside of Buildroot control when not
building the kernel internally. In my opinion, there should be a config option
allowing the user to select the SMP version or the UP one (or both).
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2013-12-11 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 21:55 [Buildroot] Knowing whether the target is multicore Frank Hunleth
2013-12-11 5:35 ` Baruch Siach [this message]
2013-12-12 4:42 ` Frank Hunleth
2013-12-12 7:32 ` Thomas Petazzoni
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=20131211053520.GD1217@tarshish \
--to=baruch@tkos.co.il \
--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