From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/dependencies
Date: Wed, 22 Aug 2007 05:46:32 +0200 [thread overview]
Message-ID: <1187754393.4494.9.camel@86-115-11-152> (raw)
In-Reply-To: <20070821231340.GT11697@aon.at>
> >
> >Oh, Oh... Yes!
> >
> >It would be nice to have a 64-128 CPU build server making the problem
> > dead obvious :-)
>
> Since you're most likely I/O bound anyway (you most likely don't build
> in a ramdisk or something that is vaguely fast for IO) there's no point
> in letting your one to eight cores be idle. No need for a 512 CPU box to
> make that obvious.
> >
> >Whatabout:
> >
> >HOSTTOOLS:=host-sed host-lzma
> >ifeq ($(BR2_STRIP_sstrip),y)
> >HOSTTOOLS+=sstrip_host
> >endif
>
> Except that "HOSTTOOLS" is a too generic name, yes.
>
> MAYBE_HOST_PREREQ is what i would have used (since lzma should also be
> conditional). Care to do this?
>
Sure, but skip the "MAYBE_" since the variable contains
the dependencies.
If no BR2_* is set it is emtpy.
> >dependencies: $(HOSTTOOLS)
>
> TIA,
--
Best Regards,
Ulf Samuelsson
next prev parent reply other threads:[~2007-08-22 3:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 20:14 [Buildroot] svn commit: trunk/buildroot/toolchain/dependencies aldot at uclibc.org
2007-08-21 20:12 ` Ulf Samuelsson
2007-08-21 20:25 ` Bernhard Fischer
2007-08-21 20:58 ` Ulf Samuelsson
2007-08-21 23:13 ` Bernhard Fischer
2007-08-22 3:46 ` Ulf Samuelsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-01 21:20 jacmet at uclibc.org
2008-09-04 2:30 hamish at uclibc.org
2008-06-18 13:11 jacmet at uclibc.org
2007-06-26 13:26 aldot at uclibc.org
2007-06-05 7:38 aldot at uclibc.org
2007-05-11 12:50 aldot at uclibc.org
2007-03-21 18:15 aldot at uclibc.org
2007-03-21 10:54 aldot at uclibc.org
2007-03-12 8:55 aldot at uclibc.org
2007-03-08 16:44 aldot at uclibc.org
2007-02-16 9:34 aldot at uclibc.org
2007-02-15 14:30 aldot at uclibc.org
2007-02-15 14:07 aldot at uclibc.org
2007-02-12 10:42 aldot at uclibc.org
2007-02-09 17:28 aldot at uclibc.org
2007-02-09 12:32 aldot at uclibc.org
2007-01-21 22:31 aldot at uclibc.org
2007-01-20 13:06 aldot at uclibc.org
2007-01-19 17:11 aldot at uclibc.org
2006-12-13 9:17 aldot at uclibc.org
2006-12-13 7:25 andersen at uclibc.org
2006-12-13 7:21 andersen at uclibc.org
2006-11-29 10:39 aldot at uclibc.org
2006-11-28 10:06 aldot at uclibc.org
2006-07-18 16:54 andersen
2006-07-18 16:42 andersen
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=1187754393.4494.9.camel@86-115-11-152 \
--to=ulf@atmel.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