Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 95264 - orbit-2.12.2 fails to install libORBit-2.so.0
Summary: orbit-2.12.2 fails to install libORBit-2.so.0
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-06 14:14 UTC by Jason Frank
Modified: 2005-07-02 14:32 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Frank 2005-06-06 14:14:11 UTC
orbit-2.12.2 appears to not install /usr/lib/libORBit-2.so.0 on at least one of
my boxes.  I get the following message at the end of the emerge:

>>> original instance of package unmerged safely.
//usr/bin/gconftool-2: error while loading shared libraries: libORBit-2.so.0:
cannot open shared object file: No such file or directory
 * Installing GNOME 2 GConf schemas




Reproducible: Always
Steps to Reproduce:
1.emerge orbit
2.
3.

Actual Results:  
No libOrbit-2.so.0 installed 

Expected Results:  
libOrbit-2.so.0 installed 


I don't see it output during the actual merge:
>>> Merging gnome-base/orbit-2.12.2 to /
--- /var/
--- /var/lib/
--- /usr/
--- /usr/bin/
>>> /usr/bin/linc-cleanup-sockets
>>> /usr/bin/orbit-idl-2
--- /usr/include/
--- /usr/include/orbit-2.0/
--- /usr/include/orbit-2.0/orbit-idl/
>>> /usr/include/orbit-2.0/orbit-idl/orbit-idl-backend.h
--- /usr/lib/
--- /usr/lib/pkgconfig/
>>> /usr/lib/pkgconfig/ORBit-idl-2.0.pc
--- /usr/share/
--- /usr/share/doc/
--- /usr/share/doc/orbit-2.12.2/
>>> /usr/share/doc/orbit-2.12.2/AUTHORS.gz
>>> /usr/share/doc/orbit-2.12.2/README.gz
>>> /usr/share/doc/orbit-2.12.2/ChangeLog.gz
>>> /usr/share/doc/orbit-2.12.2/HACKING.gz
>>> /usr/share/doc/orbit-2.12.2/NEWS.gz
>>> /usr/share/doc/orbit-2.12.2/TODO.gz
>>> /usr/share/doc/orbit-2.12.2/MAINTAINERS.gz
>>> Safely unmerging already-installed instance...
--- !mtime obj /usr/share/doc/orbit-2.12.2/TODO.gz
--- !mtime obj /usr/share/doc/orbit-2.12.2/README.gz
--- !mtime obj /usr/share/doc/orbit-2.12.2/NEWS.gz
--- !mtime obj /usr/share/doc/orbit-2.12.2/MAINTAINERS.gz
--- !mtime obj /usr/share/doc/orbit-2.12.2/HACKING.gz
--- !mtime obj /usr/share/doc/orbit-2.12.2/ChangeLog.gz
--- !mtime obj /usr/share/doc/orbit-2.12.2/AUTHORS.gz
--- !mtime obj /usr/lib/pkgconfig/ORBit-idl-2.0.pc
--- !mtime obj /usr/include/orbit-2.0/orbit-idl/orbit-idl-backend.h
--- !mtime obj /usr/bin/orbit-idl-2
--- !mtime obj /usr/bin/linc-cleanup-sockets
--- !empty dir /var/lib
--- !empty dir /var
--- !empty dir /usr/share/doc/orbit-2.12.2
--- !empty dir /usr/share/doc
--- !empty dir /usr/share
--- !empty dir /usr/lib/pkgconfig
--- !empty dir /usr/lib
--- !empty dir /usr/include/orbit-2.0/orbit-idl
--- !empty dir /usr/include/orbit-2.0
--- !empty dir /usr/include
--- !empty dir /usr/bin
--- !empty dir /usr


qpkg doesn't think it's installed:

biggie orbit # qpkg -l orbit | grep so
/usr/lib/libIDL-0.6.so.0.4.4
/usr/lib/libIDL-0.6.so.0 -> libIDL-0.6.so.0.4.4 1074726021
/usr/lib/libIDL.so -> libIDL-0.6.so.0.4.4 1074726021
/usr/lib/libORBit.so.0.5.17
/usr/lib/libORBit.so.0 -> libORBit.so.0.5.17 1074726021
/usr/lib/libORBit.so -> libORBit.so.0.5.17 1074726021
/usr/lib/libORBitutil.so.0.5.17
/usr/lib/libORBitutil.so.0 -> libORBitutil.so.0.5.17 1074726021
/usr/lib/libORBitutil.so -> libORBitutil.so.0.5.17 1074726021
/usr/lib/libIIOP.so.0.5.17
/usr/lib/libIIOP.so.0 -> libIIOP.so.0.5.17 1074726021
/usr/lib/libIIOP.so -> libIIOP.so.0.5.17 1074726021
/usr/lib/libORBitCosNaming.so.0.5.17
/usr/lib/libORBitCosNaming.so.0 -> libORBitCosNaming.so.0.5.17 1074726021
/usr/lib/libORBitCosNaming.so -> libORBitCosNaming.so.0.5.17 1074726021
/usr/bin/linc-cleanup-sockets


ls doesn't think it installed:
/usr/lib/libORBit.so
/usr/lib/libORBit.so.0
/usr/lib/libORBit.so.0.5.17
/usr/lib/libORBitCosNaming.so
/usr/lib/libORBitCosNaming.so.0
/usr/lib/libORBitCosNaming.so.0.5.17
/usr/lib/libORBitutil.so
/usr/lib/libORBitutil.so.0
/usr/lib/libORBitutil.so.0.5.17

And here is what qpkg reports for my packages:
biggie orbit # qpkg -v orbit
gnome-base/ORBit-0.5.17 *
gnome-base/orbit-2.12.2 *
dev-cpp/orbitcpp-1.3.9
dev-perl/CORBA-ORBit-0.4.3-r4
dev-perl/CORBA-ORBit-0.4.7
dev-python/orbit-python-1.99.0-r1
dev-python/orbit-python-0.3.1
dev-python/pyorbit-2.0.0
dev-python/pyorbit-2.0.1
games-action/orbital-eunuchs-sniper-1.29
gnome-base/orbit-0.5.17
gnome-base/orbit-2.10.2
gnome-base/orbit-2.12.0
gnome-base/orbit-2.12.1
gnome-base/orbit-2.12.2
media-gfx/videorbits-2.201

And, finally, here's my emerge info:
Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130,
glibc-2.3.4.20041102-r1, 2.6.10-gentoo-r6 i686)
=================================================================
System uname: 2.6.10-gentoo-r6 i686 Pentium II (Deschutes)
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.5,dev-lang/python-2.2.3-r5 [2.3.5 (#1,
May  5 2023, 20:49:40)]
distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
dev-lang/python:     2.3.5, 2.2.3-r5
sys-apps/sandbox:    [Not Present]
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.9.5, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.8.5-r3
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.16
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -mcpu=pentium2 -funroll-loops -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.1/share/config
/usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config
/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb
/usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -mcpu=pentium2 -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
http://mirror.datapipe.net/gentoo
ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X aalib alsa apache2 apm arts avi berkdb bitmap-fonts bonobo cdr crypt
cups curl dvd dvdr eds emacs emboss encode esd evo fam flac foomaticdb fortran
gd gdbm gif gnome gpm gstreamer gtk gtk2 imagemagick imap imlib ipv6 java jpeg
kde ldap libg++ libwww lirc mad mikmod mmx motif mozilla mp3 mpeg mysql ncurses
net network nls oci8 ogg oggvorbis opengl oss pam pdflib perl png python qt
quicktime readline samba sdl slang snmp spell ssl svga svgalib tcltk tcpd tiff
transcode truetype truetype-fonts type1-fonts usb vorbis xine xinerama xml xml2
xmms xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

If I can provide any more information, please let me know.  I've got another box
that this worked correctly on (P4, with no significant differences), but it is
reproducable on this box
Comment 1 foser (RETIRED) gentoo-dev 2005-06-06 14:23:25 UTC
your system time is set correctly ?
Comment 2 Jason Frank 2005-06-06 14:49:04 UTC
The clock appears to be set correctly.  It's using NTP along with my other
servers and they're all syncronized to the same NTP server.  After confirming
that, I recompiled and had the same problem.  I'll change my date into the
future, and see if that doesn't make a difference.
Comment 3 Jason Frank 2005-06-06 14:59:22 UTC
(In reply to comment #2)
After getting a little trickier, I've found the following problem in my stderr
output from the emerge:

make[6]: Warning: File `/usr/include/libIDL-2.0/libIDL/IDL.h' has modification
time 5.7e+08 s in the future
orbit-idl-backend.c: In function `load_language_backend':

That's interesting, because that makes the date: May 5 2023.  Most likely an
historical problem with the date on this box.

I'm emerging libIDL again, and I'll see where it goes from there.
Comment 4 foser (RETIRED) gentoo-dev 2005-06-06 15:08:22 UTC
This is a problem more often reported.. by now i'm starting to think we should
try to take some measures, but I don't know really how.

See #53901 and others which i can't find right now.
Comment 5 Jason Frank 2005-06-06 15:23:04 UTC
That was the problem.  It's kind of troubling, since an incorrect clock at some
point in the past can sit like a time bomb, and break some future build like
that.  having said that, I would have to guess that this is an upstream issue
though.  Normally a make install attempt to build a target if it does exist, and
throw up if it does.  In this case, it's not doing that.  In any case, my
immediate problem is resolved.  I'll leave it up to you as to whether or not you
close it (to remind you of the issue.)  Thanks for your help.
Comment 6 Nathaniel McCallum (RETIRED) gentoo-dev 2005-07-02 14:32:06 UTC
As stated above, the issue is fixed.