Hi,
> You're right !
>
> Another thing that could be done is to use NTP and ntpdate inside the
> qemu instance. This would avoid the slight delay between date reading
> in qemubuilder and date setting inside the qemu instance. I have no
> idea whether the ntp client is available in base packages,
You're right !
Another thing that could be done is to use NTP and ntpdate inside the
qemu instance. This would avoid the slight delay between date reading
in qemubuilder and date setting inside the qemu instance. I have no
idea whether the ntp client is available in base packages, and whether
you
Hi,
> Patched attached, works here (tm).
>
> > The real fix would be to find out why RTC time is not obtained (time
> > to debug qemu and linux kernel).
>
> This can wait :) PowerPC seems an easier target for me ATM.
>
> JB
Hmmm... I think this code doesn't take timezones into account, so I
re
Hi,
Patched attached, works here (tm).
> The real fix would be to find out why RTC time is not obtained (time
> to debug qemu and linux kernel).
This can wait :) PowerPC seems an easier target for me ATM.
JB
diff --git a/qemubuilder.c b/qemubuilder.c
index 0744651..14ad9d5 100755
--- a/qemubuil
Hi,
> When using qemubuilder --build, the clock inside the qemu instance does
> not appear to be set correctly. This leads to warning messages when
> untaring the sources, followed by a fatal failure when autotools are
> run:
Yup.
> Full log is attached.
>
> Would a call to `date` to set the cu
Package: qemubuilder
Version: 0.39
Severity: normal
Hi,
When using qemubuilder --build, the clock inside the qemu instance does
not appear to be set correctly. This leads to warning messages when
untaring the sources, followed by a fatal failure when autotools are
run:
(...)
dh_testdir
dh_testro
6 matches
Mail list logo
