QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths
 

On Fri, May 06, 2011 at 03:25:31PM -0300, Rafael Barrera Oro wrote:
> 2011/5/6 Kevin McCarthy <signals@gentoo.org>
>
> > On Fri, May 06, 2011 at 01:45:01PM -0300, Rafael Barrera Oro wrote:
> > >
> > > Attached to this message are the contents of the afforementioned file,
> > > thanks for the help!!!

This seems like cause for alarm:

> >>> Unpacking source...
> >>> Unpacking dialog-1.1-20100428.tgz to /var/tmp/portage/dev-util/dialog-1.1.20100428/work
> tar: dialog-1.1-20100428/aclocal.m4: time stamp 2010-04-28 17:36:28 is 252636716.880100597 s in the future

Something is definitely wrong with your clock.

Then we have this:

> >>> Source configured.
> >>> Compiling source in /var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-20100428 ...
> make
> make: Warning: File `trace.c' has modification time 2.4e+08 s in the future

Here is the libtool link from the compile phase. It looks correct, but
notice that it warns you about the clock problems:

> libtool: link: i686-pc-linux-gnu-gcc -Wl,-O1 -Wl,--as-needed -o .libs/dialog .libs/dialog.o -L/var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-20100428 /var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-20100428/.libs/libdialog.so -L/usr/lib -lncursesw -lm
> make: warning: Clock skew detected. Your build may be incomplete.
> >>> Source compiled.
> >>> Test phase [not enabled]: dev-util/dialog-1.1.20100428
>

Then in the install phase, you will see that make can't figure out what
is up-to-date (because the clock is off) so it decides everything needs
to be rebuilt.

> >>> Install dialog-1.1.20100428 into /var/tmp/portage/dev-util/dialog-1.1.20100428/image/ category dev-util
---8<---SNIP---8<---
> make: Warning: File `trace.c' has modification time 2.4e+08 s in the future
> /usr/bin/libtool --tag=CC --mode=compile i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/ncursesw -D_XOPEN_SOURCE_EXTENDED -DHAVE_CONFIG_H -I. -I. -DLOCALEDIR="/usr/share/locale" -c trace.c

In the install phase, DESTDIR is set to the PORTAGE_TEMP directory and
libtool is called with -rpath set to the temp dir. This is what's
causing the QA warning. The problem is that we aren't supposed to be
building anything at this point. It is the INSTALL phase after all:

> /usr/bin/libtool --tag=CC --mode=link i686-pc-linux-gnu-gcc -rpath /var/tmp/portage/dev-util/dialog-1.1.20100428/image//usr/lib -version-info `cut -f1 ./VERSION` -Wl,-O1 -Wl,--as-needed -o libdialog.la trace.lo rc.lo calendar.lo fselect.lo timebox.lo formbox.lo guage.lo pause.lo progressbox.lo tailbox.lo mixedform.lo mixedgauge.lo arrows.lo buttons.lo checklist.lo columns.lo dlg_keys.lo editbox.lo inputbox.lo inputstr.lo menubox.lo mouse.lo mousewget.lo msgbox.lo textbox.lo ui_getc.lo util.lo version.lo yesno.lo -L/usr/lib -lncursesw -lm

So, the short of it is that you need to fix your clock. It needs to be
set reasonably close to the actual time and the timezone needs to be set
correctly as well. You might also look into net-misc/ntp to set the
clock from the network.

If your clock is set correctly, there's something horribly wrong and it
will require additional troubleshooting.

--
Kevin McCarthy <signals@gentoo.org>

QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths
 

On Fri, May 06, 2011 at 10:45:31PM +0100, Neil Bothwick wrote:
> Kevin, can you upload your PGP/GPG key to a public keyserver, otherwise
> the only point of signing your mails is to cause mailers to slow down
> while trying to check a signature against an unavailable key.

I know what you mean. I hate it when mutt stalls for ages while GPG
looks for the key. My key is in subkeys.pgp.net and I *thought* the
major keyservers exchanged keys. Is there a particular keyserver you
would like me to upload it to?

I suppose there's no reason I even need to sign messages to the list.
It's just a habit to sign e-mail.

--
Kevin McCarthy <signals@gentoo.org>

QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths
 

On Mon, May 09, 2011 at 10:44:10AM -0300, Rafael Barrera Oro wrote:
>
> Considering the confusing nature of the error and the easyness which it is
> fixed with, should'n it be in a faq or something?
>

Well, I suppose the handbook could be changed to explain that no only do
you have to set the timezone and UTC/local settings for you clock, but
you also have to make sure it is set. Unfortunately, adding this
specific problem to a FAQ is problematic because there are dozens of
errors and problems that can come from a mis-set clock. It would be
difficult to cover them all.

--
Kevin McCarthy <signals@gentoo.org>