Hi,
I disabled the wireless-tools (default) cross build (mark for stage 1).
Committed revision 32687.
Committed revision 32688.
There is no need for it during bootstrap and this (hides) your error.
I'll test build 7.0 for the parted error. You could just rename the
build/.../var/adm/logs/3-parted.err to .log and t2 will continue
with the next package for now.
Yours,
Jüri Izberg wrote:
2009/3/20 René Rebe <[email protected]>:
Ok, good to know. However, I just noticed from your log
that you cross build your target. I guess you build the p4
optimized minimal target on a x86 CPU that is capable
of running the resulting executables? In that case you should
not cross build. This will avoid a lot of the cross build
complexity (and this packages will likely just build natively),
but also protect your host system be running most of the
package builds sandboxed.
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
Hmm strange i looked on my config and i have not selected cross build there.
i added my config file here as attachment
and yes i try to build the p4
optimized minimal target on a x86 CPU
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
Managing Directors: Susanne Klaus, René Rebe
Location: Berlin, Amtsgericht Charlottenburg HRB 105 123 B
Tax-ID#: DE251602478
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2