ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] libXt "failed dependencies"


From: Stuart Hughes
Subject: Re: [Ltib] libXt "failed dependencies"
Date: Tue, 14 Jul 2009 08:42:09 +0100
User-agent: Thunderbird 2.0.0.16 (X11/20080707)

Hi Alan,

I can explain the difference in behaviour. When running -m scdeploy, the rpm file in installed with a "fabricated" spec file that has:

Autoreqprov     : no

This effectively disables the provides/requires checks that happen in a normal run. This is something you would want during package development.

The real question is why you're failing this dependency.  Run:

ls -l rootfs/libc*

You should see libc.so.6 in there and it should be a link to a real file (for example: libc-2.3.6.so). If it is not there, then base_libs has not been installed. If it is, then for some reason base_libs has not inserted this provide into the rpm database. You can check with:
rpm --root `pwd`/rootfs -q base_libs --provides | grep libc.so

Regards, Stuart


Alan Carvalho de Assis wrote:
Hi Stuart, (this is not devaju this time :)

There is some issue compiling libXt, it always fail when compiling
automatically by LTIB, but works when compiling by "./ltib -p libXt -m
(prep, scbuild,scdeploy).

This is the error message:

Build time for libXt: 71 seconds

sudo /opt/ltib/usr/bin/rpm --root /home/ltib/rootfs --dbpath
/var/lib/rpm -e --allmatches --nodeps --noscripts --define '_tmppath
/tmp/ltib' libXt 2>/dev/null
sudo /opt/ltib/usr/bin/rpm --root /home/ltib/rootfs --dbpath
/var/lib/rpm --prefix / --ignorearch -ivh --force --excludedocs
--noscripts --define '_tmppath /tmp/ltib'
/home/ltib/rpm/RPMS/arm/libXt-1.0.4-5.arm.rpm
error: failed dependencies:
        libc.so.6(GLIBC_2.0)   is needed by libXt-1.0.4-5
        libc.so.6(GLIBC_2.1)   is needed by libXt-1.0.4-5


f_buildrpms() returned an error, exiting
traceback:
 main:555


Started: Mon Jul 13 14:29:56 2009
Ended:   Mon Jul 13 15:00:08 2009
Elapsed: 1812 seconds


Build Failed





reply via email to

[Prev in Thread] Current Thread [Next in Thread]