On Tuesday 13 March 2007 16:42:25 yokoy wrote:
>
> hi,
>
> yesterday I tried to build a target in trunk. I interupted the build during
> glibc, made a svn up and started the build-target again. The script failed at
> the first packages gzip ( New Revision: 22950) with some errors
> like "gzip.texi:83: Unknown command 'abbr' " and "gzip.texi:84: Misplaced
> { " .
> OK, I thougt the interrupted build of glibc was evil and did a
>
> ./scripts/Build-Pkg -cfg yky-matchbox glibc
>
> to build a correct glibc.
>
> After a short while there was a "Speicherzugriffsfehler" / Signal 11 /
> segmentation fault
>
> Well, not only the build of the package is broken, the whole host-system is
> broken (t2-minimal 6.0.1), too. Also a chroot from a live-cd is not possible,
> again a segfault.
>
> Is it a known problem?
Build-Pkg without further argument INSTALLS INTO THE RUNNING SYSTEM.
When you want to build a single package do Build-Target -job 5-glibc (or so).
All in all, you seldome want to call Build-Pkg manually unless you are a
T2 guru.
You most probably always want to run either Build-Target and Emerge-Pkg.
One could argue that why (the h*ll) we have Build-Pkg lingering around
there in the first place, thats because historically Build-Pkg was used
to indeed build single packages into the system until we introduced
Emerge-Pkg also handling downloads and dependencies.
We should point all this out verbosely in the new Wiki, anyone?
Yours,
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
+49 (0)30 / 255 897 45
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2
