Bug 684286 - FTBFS - tlibYap.so.5.1.3 not found
Summary: FTBFS - tlibYap.so.5.1.3 not found
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yap
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Pisar
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-11 17:21 UTC by Zenon Panoussis
Modified: 2011-05-13 12:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 13:35:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Zenon Panoussis 2011-03-11 17:21:16 UTC
Building 5.1.3-2.1.el6 breaks thusly:

(cd LGPL/chr ; make install)
make[1]: Entering directory `/root/rpmbuild/BUILD/Yap-5.1.3/LGPL/chr'
../../yap ../../startup -f -l chr_swi_bootstrap.yap \
                      -g "chr_compile_step3('guard_entailment.chr','guard_entailment.pl'),halt." \
                      -z 'halt(1).'
../../yap: error while loading shared libraries: libYap.so.5.1.3: cannot open shared object file: No such file or directory
make[1]: *** [guard_entailment.pl] Error 127
make[1]: Leaving directory `/root/rpmbuild/BUILD/Yap-5.1.3/LGPL/chr'
make: *** [install_data] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.bhxfMH (%install)

In other words, the SRPM depends on the RPM that it is supposed to build. And indeed, installing a pre-built yap RPM "fixes" the build problem. 

At the moment of the breakage there are already two copies of tlibYap.so.5.1.3 on the system:

BUILD/Yap-5.1.3/libYap.so.5.1.3
BUILDROOT/yap-5.1.3-2.1.el6.x86_64/usr/lib64/libYap.so.5.1.3

Thus, the problem seems to be that make is looking in the system libdir instead of in the buildroot libdir.

Comment 2 RHEL Program Management 2011-03-11 17:37:38 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Zenon Panoussis 2011-03-11 20:20:17 UTC
Bumping up to 6.1 to prevent it from making the next release.

Comment 4 Petr Pisar 2011-03-16 13:35:04 UTC
If you experience problems, you can find a tip in Fedora yap package where I made some tunes to build process <http://pkgs.fedoraproject.org/gitweb/?p=yap.git;a=commitdiff;h=7787720472508e9fb1939f6445edaefc4d735da1> (look below `# Hack LGPL/chr' comment).

However in our building environment problem you describe does not present.


Note You need to log in before you can comment on or make changes to this bug.