Gentoo Archives: gentoo-user

From: Rafael Barrera Oro <borafael@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths
Date: Mon, 09 May 2011 13:45:48
Message-Id: BANLkTim4AGPZLf0+MeHoyMindc7nDXU0ow@mail.gmail.com
In Reply to: Re: [gentoo-user] QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths by Mick
1 I can't believe it!!!
2
3 Since the purpose of the whole installation was to start using a machine
4 that has been abandoned for some time i paid no attention to a CMOS alert
5 that came up on the screen the first time i turned it on, shrugging it off
6 as one more error message of a machine aproaching the end of its useful
7 life. After reading your responses i went straight to the CMOS clock and,
8 non surprisingly, it was not set correctly, i corrected the time and date
9 and the weird errors dissapeared.
10
11 I can't say i fully understand why the unset clock caused this but i do can
12 say that this was a tough one and never would have figured it out without
13 your expertise, so thanks, much obliged
14
15 Considering the confusing nature of the error and the easyness which it is
16 fixed with, should'n it be in a faq or something?
17
18 truly yours
19
20 Rafael
21
22
23 2011/5/6 Mick <michaelkintzios@×××××.com>
24
25 > On Friday 06 May 2011 19:57:36 Kevin McCarthy wrote:
26 > > On Fri, May 06, 2011 at 03:25:31PM -0300, Rafael Barrera Oro wrote:
27 > > > 2011/5/6 Kevin McCarthy <signals@g.o>
28 > > >
29 > > > > On Fri, May 06, 2011 at 01:45:01PM -0300, Rafael Barrera Oro wrote:
30 > > > > > Attached to this message are the contents of the afforementioned
31 > > > > > file, thanks for the help!!!
32 > >
33 > > This seems like cause for alarm:
34 > > > >>> Unpacking source...
35 > > > >>> Unpacking dialog-1.1-20100428.tgz to
36 > > > >>> /var/tmp/portage/dev-util/dialog-1.1.20100428/work
37 > > >
38 > > > tar: dialog-1.1-20100428/aclocal.m4: time stamp 2010-04-28 17:36:28 is
39 > > > 252636716.880100597 s in the future
40 > >
41 > > Something is definitely wrong with your clock.
42 > >
43 > > Then we have this:
44 > > > >>> Source configured.
45 > > > >>> Compiling source in
46 > > > >>>
47 > /var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-201004
48 > > > >>> 28 ...
49 > > >
50 > > > make
51 > > > make: Warning: File `trace.c' has modification time 2.4e+08 s in the
52 > > > future
53 > >
54 > > Here is the libtool link from the compile phase. It looks correct, but
55 > >
56 > > notice that it warns you about the clock problems:
57 > > > libtool: link: i686-pc-linux-gnu-gcc -Wl,-O1 -Wl,--as-needed -o
58 > > > .libs/dialog .libs/dialog.o
59 > > >
60 > -L/var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-20100428
61 > > >
62 > /var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-20100428/.
63 > > > libs/libdialog.so -L/usr/lib -lncursesw -lm make: warning: Clock skew
64 > > > detected. Your build may be incomplete.
65 > > >
66 > > > >>> Source compiled.
67 > > > >>> Test phase [not enabled]: dev-util/dialog-1.1.20100428
68 > >
69 > > Then in the install phase, you will see that make can't figure out what
70 > > is up-to-date (because the clock is off) so it decides everything needs
71 > > to be rebuilt.
72 > >
73 > > > >>> Install dialog-1.1.20100428 into
74 > > > >>> /var/tmp/portage/dev-util/dialog-1.1.20100428/image/ category
75 > > > >>> dev-util
76 > >
77 > > ---8<---SNIP---8<---
78 > >
79 > > > make: Warning: File `trace.c' has modification time 2.4e+08 s in the
80 > > > future /usr/bin/libtool --tag=CC --mode=compile i686-pc-linux-gnu-gcc
81 > > > -O2 -march=i686 -pipe -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
82 > > > -I/usr/include/ncursesw -D_XOPEN_SOURCE_EXTENDED -DHAVE_CONFIG_H -I.
83 > -I.
84 > > > -DLOCALEDIR=\"/usr/share/locale\" -c trace.c
85 > >
86 > > In the install phase, DESTDIR is set to the PORTAGE_TEMP directory and
87 > > libtool is called with -rpath set to the temp dir. This is what's
88 > > causing the QA warning. The problem is that we aren't supposed to be
89 > >
90 > > building anything at this point. It is the INSTALL phase after all:
91 > > > /usr/bin/libtool --tag=CC --mode=link i686-pc-linux-gnu-gcc -rpath
92 > > > /var/tmp/portage/dev-util/dialog-1.1.20100428/image//usr/lib
93 > > > -version-info `cut -f1 ./VERSION` -Wl,-O1 -Wl,--as-needed -o
94 > > > libdialog.la trace.lo rc.lo calendar.lo fselect.lo timebox.lo
95 > formbox.lo
96 > > > guage.lo pause.lo progressbox.lo tailbox.lo mixedform.lo mixedgauge.lo
97 > > > arrows.lo buttons.lo checklist.lo columns.lo dlg_keys.lo editbox.lo
98 > > > inputbox.lo inputstr.lo menubox.lo mouse.lo mousewget.lo msgbox.lo
99 > > > textbox.lo ui_getc.lo util.lo version.lo yesno.lo -L/usr/lib -lncursesw
100 > > > -lm
101 > >
102 > > So, the short of it is that you need to fix your clock. It needs to be
103 > > set reasonably close to the actual time and the timezone needs to be set
104 > > correctly as well. You might also look into net-misc/ntp to set the
105 > > clock from the network.
106 > >
107 > > If your clock is set correctly, there's something horribly wrong and it
108 > > will require additional troubleshooting.
109 >
110 > O_O
111 >
112 > Thanks for an excellent and very educational explanation! I don't think
113 > I've
114 > come across anything like this clock skew generated problem before. I'll
115 > know
116 > what to look for in the future.
117 >
118 > The OP may also want to check out chrony in case he's using a laptop.
119 > --
120 > Regards,
121 > Mick
122 >

Replies