FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 05-09-2011, 01:44 PM
Rafael Barrera Oro
 
Default QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths

I can't believe it!!!
Since the purpose of the whole installation was to start using a machine that has been abandoned for some time i paid no attention to a CMOS alert that came up on the screen the first time i turned it on, shrugging it off as one more error message of a machine aproaching the end of its useful life. After reading your*responses*i went straight to the CMOS clock and, non surprisingly, it was not set correctly, i corrected the time and date and the weird errors dissapeared.*

I can't say i fully understand why the unset clock caused this but i do can say that this was a tough one and never would have figured it out without your expertise, so thanks, much obliged

Considering the confusing nature of the error and the easyness which it is fixed with, should'n it be in a faq or something?
truly yours
Rafael


2011/5/6 Mick <michaelkintzios@gmail.com>

On Friday 06 May 2011 19:57:36 Kevin McCarthy wrote:

> 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-201004

> > >>> 28 ...

> >

> > 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.



*O_O



Thanks for an excellent and very educational explanation! *I don't think I've

come across anything like this clock skew generated problem before. *I'll know

what to look for in the future.



The OP may also want to check out chrony in case he's using a laptop.

--

Regards,

Mick
 
Old 05-09-2011, 01:44 PM
Rafael Barrera Oro
 
Default QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths

I can't believe it!!!
Since the purpose of the whole installation was to start using a machine that has been abandoned for some time i paid no attention to a CMOS alert that came up on the screen the first time i turned it on, shrugging it off as one more error message of a machine aproaching the end of its useful life. After reading your*responses*i went straight to the CMOS clock and, non surprisingly, it was not set correctly, i corrected the time and date and the weird errors dissapeared.*

I can't say i fully understand why the unset clock caused this but i do can say that this was a tough one and never would have figured it out without your expertise, so thanks, much obliged

Considering the confusing nature of the error and the easyness which it is fixed with, should'n it be in a faq or something?
truly yours
Rafael


2011/5/6 Mick <michaelkintzios@gmail.com>

On Friday 06 May 2011 19:57:36 Kevin McCarthy wrote:

> 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-201004

> > >>> 28 ...

> >

> > 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.



*O_O



Thanks for an excellent and very educational explanation! *I don't think I've

come across anything like this clock skew generated problem before. *I'll know

what to look for in the future.



The OP may also want to check out chrony in case he's using a laptop.

--

Regards,

Mick
 
Old 05-10-2011, 12:24 AM
Indi
 
Default QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths

On Sat, May 07, 2011 at 11:20:02AM +0200, Mick wrote:
> On Saturday 07 May 2011 01:40:54 Indi wrote:
> > On Sat, May 07, 2011 at 02:10:01AM +0200, Indi wrote:
> > > Speaking of that, I always get that notice "the PGP signature could
> > > not be verified" on your mails, Neil.
> >
> > Never mind, sorry -- that was my configuration needed updating.
>
> Just a thought - I had to change the default public key server the other day,
> because connecting to it was timing out. Not sure if it was the
> subkeys.pgp.net that I was having trouble with. Now it seems to work fine
> again and it finds said key:
>
> =======================================
> $ gpg --keyserver hkp://subkeys.pgp.net --search-keys signals@gentoo.org
> gpg: enabled debug flags: memstat
> gpg: searching for "signals@gentoo.org" from hkp server subkeys.pgp.net
> (1) Kevin McCarthy <signals@gentoo.org>
> 2048 bit RSA key D0AE2DE8, created: 2011-02-22
> Keys 1-1 of 1 for "signals@gentoo.org". Enter number(s), N)ext, or Q)uit > Q
> =======================================
> --
> Regards,
> Mick

Thanks, but it was self-induced -- shot myself in the foot
fooling about with .muttrc and failing to proofread all the
changes properly.

--
caveat utilitor
 

Thread Tools




All times are GMT. The time now is 07:01 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org