On Fri, 6 May 2011 11:03:47 +0100, Stroller wrote:

> > Portage should run lafilefixer on its own these days. The fixlafiles
> > is one of the default FEATURES.

Portage has its own code for this, lafilefixer can be uninstalled.
>
> I only read of that on this list in the last few weeks, so had assumed
> it had come of ~x86, but not yet x86.

emerge --info | grep fixlafiles

will tell you whether your portage has it.


--
Neil Bothwick

"Be strict when sending and tolerant when receiving."
RFC 1958 - Architectural Principles of the Internet - section 3.9

I successfuly installed lafilefixer and then ran it, however, the problem persists

2011/5/5 Stroller <stroller@stellar.eclipse.co.uk>


On 5/5/2011, at 3:00am, Rafael Barrera Oro wrote:
...The thing is that emerging mirrorselect has the following outcome:

* QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths** ERROR: dev-util/dialog-1.1.20100428 failed:** * soiled libtool library files found

Have you run `lafilefixer`?
I run `sudo bash -c 'lafilefixer --justfixit && revdep-rebuild'` after every upgrade.
It may not be necessary every time, but it won't break anything. Probably worth a go.

Package is dev-util/lafilefixer if it's not already installed.
Stroller.

2011/5/6 Kevin McCarthy <signals@gentoo.org>

On Fri, May 06, 2011 at 12:32:50PM -0300, Rafael Barrera Oro wrote:

> I successfuly installed lafilefixer and then ran it, however, the problem

> persists

>

> 2011/5/5 Stroller <stroller@stellar.eclipse.co.uk>

>

> >

> > On 5/5/2011, at 3:00am, Rafael Barrera Oro wrote:

> >

> > ...

> > The thing is that emerging mirrorselect has the following outcome:

> >

> > * QA Notice: libdialog.la appears to contain PORTAGE_TMPDIR paths

> > �* ERROR: dev-util/dialog-1.1.20100428 failed:

> > �* � soiled libtool library files found



Hmm, this is a strange one. It would probably help to take a look in

libdialog.la to see what's getting set to PORTAGE_TMPDIR. Once emerge

has failed to merge dev-util/dialog it should leave the workdir in

/var/tmp/portage. Can you post the contents of:



/var/tmp/portage/dev-util/dialog-1.1.20100428/work/dialog-1.1-20100428/libdialog.la



to the list? If you don't have a /v/t/p/dev-util/dialog-1.1.20100428

directory after failing to emerge it, try *TEMPORARILY* using the

keepwork feature:



FEATURES="keepwork" emerge -1 dev-util/dialog



It's bad to use keepwork when you aren't debugging, so DO NOT put it in

your make.conf.



Hopefully looking at the .la file will help us narrow down what is

happening.



--

Kevin McCarthy <signals@gentoo.org>


Attached to this message are the contents of the afforementioned file, thanks for the help!!!
# libdialog.la - a libtool library file
# Generated by libtool (GNU libtool) 2.2.10
#
# Please DO NOT delete this file!
# It is necessary for linking the library.

# The name that we can dlopen(3).
dlname='libdialog.so.7'

# Names of this library.
library_names='libdialog.so.7.0.1 libdialog.so.7 libdialog.so'

# The name of the static archive.
old_library='libdialog.a'

# Linker flags that can not go in dependency_libs.
inherited_linker_flags='

# Libraries that this one depends upon.
dependency_libs=' -L/usr/lib -lncursesw -lm'

# Names of additional weak libraries provided by this library
weak_library_names='

# Version information for libdialog.
current=7
age=0
revision=1

# Is this an already installed library?
installed=no

# Should we warn about portability when linking against -modules?
shouldnotlink=no

# Files to dlopen/dlpreopen
dlopen='
dlpreopen='

# Directory that this library needs to be installed in:
libdir='/var/tmp/portage/dev-util/dialog-1.1.20100428/image//usr/lib'

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



Hmm... It looks like libtool is being called to link the library when

DESTDIR is set. It shouldn't be set during the compile phase, only

during the install phase. I wonder if the library is failing to be built

for some reason during compile, so make tries to build it in the

ebuild's install phase? I guess I'll need to see the entire build.log

for it before I can know for sure:



/var/tmp/portage/dev-util/dialog-1.1.20100428/temp/build.log



--

Kevin McCarthy <signals@gentoo.org>


By all means, attached to this mail is the build log, thanks, sincerely

On Fri, 6 May 2011 12:34:29 -0400, Kevin McCarthy wrote:

> [application/pgp-signature (490 bytes)]

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.


--
Neil Bothwick

It's no use crying over spilt milk -- it only makes it salty for the cat.

On Fri, May 6, 2011 at 1:57 PM, Kevin McCarthy <signals@gentoo.org> 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-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>
>

What does the outpute of "date" show for your current date? this looks
like your clock/cmos battery is dead. I had one keep me from emerging
anything because the system would go into a loop trying to emeerge
things like glibc.

James Wall

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

On Fri, May 06, 2011 at 11:50:02PM +0200, Neil Bothwick wrote:
> On Fri, 6 May 2011 12:34:29 -0400, Kevin McCarthy wrote:
>
> > [application/pgp-signature (490 bytes)]
>
> 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.
>

Speaking of that, I always get that notice "the PGP signature could
not be verified" on your mails, Neil.

--
caveat utilitor

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.

--
caveat utilitor

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