On 07/01/2016 08:31 PM, scsijon wrote:
On 06/30/2016 08:00 PM, scsijon wrote:
On 06/27/2016 07:12 PM, René Rebe wrote:
Hi,
/cut
Actually, when I think more about it after reading your comments, the
manual sections some more, and some blfs etc. docs, I think my problems
may be relating to it failing during Stage 1 and onward, and then
restarting the build with existing build left in situ, rather than
deleting the build and starting again after fixing the problem.
I'm now thinking that the problem cause is that on a restart for stages
1+, the build is NOT performing a chroot to the new environment when
necessary and starting again from there, but is attempting to continue
to build within the stage0 environment, that would seem to explain the
problems ocurring.
As a test i've done a couple of "very tacky" temporary script
alterations for workarounds and disabled a couple of packages that
normally continually fail. After changing the Config gnome2 variable to
usr, it seems to be building correctly and the packaes are showing in
the var/adm/flists to be in the right places if I don't stop the build,
(at least to the start of stage 2 so far) and so i'll leave it at least
overnight and check to see what happens. I do know, as i've tested that
already, that if the build fails or stops before stage 5 it fails again
and gives the error I mentioned if I just attempt to get it to continue
by using ./script/Build-Target again, whether I use a ./script/Clean
-cache or not beforehand.
This may mean as i'm beginning to understanding it, the problem could be
fixed by adding in ?Build-Target (or where-ever it needs to be), a check
of what stage being built and performing a chroot into where-ever it
should before the build continues. But where and what scripting is
needed, I have no idea, hopefully Rene does.
Part of another email I sent to BarryK and Rene:-
> With my tests with T2 failing to build properly. So far I am finding
> if it stops or is interupted between stage 1 and stage 3 (haven't set
> anything to try for stage 4 yet) it's not restarting INSIDE the
> toolchain but back as if your starting again at stage 0 but with the
> correct current/failed/next package (as if it's not doing the first
> chroot), BUT if you interupt during stage 5+ it seems to be able to
> know and chroot to the correct place to restart. Sorry Rene, but it's
> something for you to fix. But it might get a number of problems that
> have been appearing for a while, done with and out of the system
> permanently if you can.
And todays missive is:-
Having played around "somewhat' to the destructive point of having to
reload T2 from my archive, I think I can roughly explain the cause of
the problem!
If I interupt a build in stage 0 it will restart and build ok to
conclusion as long as it doesn't fail again at a higher stage.
If I interupt it or cause it to fail past stage 0, i.e. stages 1 to
stage 4 inclusively, and restart it without deleting or clearing Build
so it builds from the beginning, when it starts again it seems to be
running as stage 0 UNTIL IT STEPS UP to the next stage, when it seems to
sort itself out and unless another package is affected it goes on and
completes the build. However, as a second point of fail, if any of the
packages that use gnome2-conf.in are involved it seems to 'bomb' again
anyway after the first stop, and it seems to try to put files out side
the toolchain it's suppose to be using anyway, which of course causes a
fail anyway, i'm not sure why though.
Yeah Rene, it's not technically worded in any meaningfull way, but I
hope the explanation is clear enough for you to get an idea of what i'm
trying to pass over to you. It took about 40computerhrs of failing /
aborting / etc / restarting, and writing notes as I go, to get to me
being able to write this with some certainty as the apparent problem
root cause. If you don't understand it, (as I expect the first time
around,) feed me with what you think I wrote and i'll ammend it until we
understand each other enough.
regards
Hopefully this makes sense
regards
regards and keep up the good T2 work.
----------------------------------------------------------- If you wish
to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
