1 |
On Friday 06 May 2011 19:57:36 Kevin McCarthy wrote: |
2 |
> On Fri, May 06, 2011 at 03:25:31PM -0300, Rafael Barrera Oro wrote: |
3 |
> > 2011/5/6 Kevin McCarthy <signals@g.o> |
4 |
> > |
5 |
> > > On Fri, May 06, 2011 at 01:45:01PM -0300, Rafael Barrera Oro wrote: |
6 |
> > > > Attached to this message are the contents of the afforementioned |
7 |
> > > > file, thanks for the help!!! |
8 |
> |
9 |
> This seems like cause for alarm: |
10 |
> > >>> Unpacking source... |
11 |
> > >>> Unpacking dialog-1.1-20100428.tgz to |
12 |
> > >>> /var/tmp/portage/dev-util/dialog-1.1.20100428/work |
13 |
> > |
14 |
> > tar: dialog-1.1-20100428/aclocal.m4: time stamp 2010-04-28 17:36:28 is |
15 |
> > 252636716.880100597 s in the future |
16 |
> |
17 |
> Something is definitely wrong with your clock. |
18 |
> |
19 |
> Then we have this: |
20 |
> > >>> Source configured. |
21 |
> > >>> Compiling source in |
22 |
> > >>> /var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-201004 |
23 |
> > >>> 28 ... |
24 |
> > |
25 |
> > make |
26 |
> > make: Warning: File `trace.c' has modification time 2.4e+08 s in the |
27 |
> > future |
28 |
> |
29 |
> Here is the libtool link from the compile phase. It looks correct, but |
30 |
> |
31 |
> notice that it warns you about the clock problems: |
32 |
> > libtool: link: i686-pc-linux-gnu-gcc -Wl,-O1 -Wl,--as-needed -o |
33 |
> > .libs/dialog .libs/dialog.o |
34 |
> > -L/var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-20100428 |
35 |
> > /var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-20100428/. |
36 |
> > libs/libdialog.so -L/usr/lib -lncursesw -lm make: warning: Clock skew |
37 |
> > detected. Your build may be incomplete. |
38 |
> > |
39 |
> > >>> Source compiled. |
40 |
> > >>> Test phase [not enabled]: dev-util/dialog-1.1.20100428 |
41 |
> |
42 |
> Then in the install phase, you will see that make can't figure out what |
43 |
> is up-to-date (because the clock is off) so it decides everything needs |
44 |
> to be rebuilt. |
45 |
> |
46 |
> > >>> Install dialog-1.1.20100428 into |
47 |
> > >>> /var/tmp/portage/dev-util/dialog-1.1.20100428/image/ category |
48 |
> > >>> dev-util |
49 |
> |
50 |
> ---8<---SNIP---8<--- |
51 |
> |
52 |
> > make: Warning: File `trace.c' has modification time 2.4e+08 s in the |
53 |
> > future /usr/bin/libtool --tag=CC --mode=compile i686-pc-linux-gnu-gcc |
54 |
> > -O2 -march=i686 -pipe -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 |
55 |
> > -I/usr/include/ncursesw -D_XOPEN_SOURCE_EXTENDED -DHAVE_CONFIG_H -I. -I. |
56 |
> > -DLOCALEDIR=\"/usr/share/locale\" -c trace.c |
57 |
> |
58 |
> In the install phase, DESTDIR is set to the PORTAGE_TEMP directory and |
59 |
> libtool is called with -rpath set to the temp dir. This is what's |
60 |
> causing the QA warning. The problem is that we aren't supposed to be |
61 |
> |
62 |
> building anything at this point. It is the INSTALL phase after all: |
63 |
> > /usr/bin/libtool --tag=CC --mode=link i686-pc-linux-gnu-gcc -rpath |
64 |
> > /var/tmp/portage/dev-util/dialog-1.1.20100428/image//usr/lib |
65 |
> > -version-info `cut -f1 ./VERSION` -Wl,-O1 -Wl,--as-needed -o |
66 |
> > libdialog.la trace.lo rc.lo calendar.lo fselect.lo timebox.lo formbox.lo |
67 |
> > guage.lo pause.lo progressbox.lo tailbox.lo mixedform.lo mixedgauge.lo |
68 |
> > arrows.lo buttons.lo checklist.lo columns.lo dlg_keys.lo editbox.lo |
69 |
> > inputbox.lo inputstr.lo menubox.lo mouse.lo mousewget.lo msgbox.lo |
70 |
> > textbox.lo ui_getc.lo util.lo version.lo yesno.lo -L/usr/lib -lncursesw |
71 |
> > -lm |
72 |
> |
73 |
> So, the short of it is that you need to fix your clock. It needs to be |
74 |
> set reasonably close to the actual time and the timezone needs to be set |
75 |
> correctly as well. You might also look into net-misc/ntp to set the |
76 |
> clock from the network. |
77 |
> |
78 |
> If your clock is set correctly, there's something horribly wrong and it |
79 |
> will require additional troubleshooting. |
80 |
|
81 |
O_O |
82 |
|
83 |
Thanks for an excellent and very educational explanation! I don't think I've |
84 |
come across anything like this clock skew generated problem before. I'll know |
85 |
what to look for in the future. |
86 |
|
87 |
The OP may also want to check out chrony in case he's using a laptop. |
88 |
-- |
89 |
Regards, |
90 |
Mick |