Installs on one slice but not the other

49 views
Skip to first unread message

gobigdave

unread,
Apr 2, 2009, 10:01:29 PM4/2/09
to Phusion Passenger Discussions
I have two SliceHost CentOS 5 slices. The first (test) system install
Passenger without a single problem. The other (prod) system fails
every time with:

### In ext/apache2:
g++ -shared SystemTime.o Utils.o Bucket.o Logging.o Configuration.o
CachedFileStat.o Hooks.o mod_passenger.o -fPIC -o mod_passenger.so ../
libboost_oxt.a -fPIC -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -I/usr/
include/apr-1 -I/usr/include/apr-1 -g -pipe -Wall -Wp,-
D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-
size=4 -m64 -mtune=generic -fno-strict-aliasing -I/usr/include/httpd -
D_REENTRANT -I/usr/local/include -fPIC -lapr-1 -laprutil-1 -lpthread -
lstdc++
/usr/bin/ld: skipping incompatible /usr/lib/libaprutil-1.so when
searching for -laprutil-1
/usr/bin/ld: cannot find -laprutil-1
collect2: ld returned 1 exit status
rake aborted!
Command failed with status (1): [g++ -shared SystemTime.o Utils.o
Bucket.o ...]
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.1.3/Rakefile:158
(See full trace by running task with --trace)

Been searching around for a while now, and I did a yum upgrade and
bunches of reinstalls of as many packages as I can think of. All with
no luck. In theory, both of these slices are the same, but obviously
something is messed up.

Any ideas for where I can look?

gobigdave

unread,
Apr 2, 2009, 10:15:03 PM4/2/09
to Phusion Passenger Discussions
I found the answer on a Japanese web site. I couldn't read the text,
but the command was there. The key search was "skipping incompatible /
usr/lib/libaprutil-1.so".

I ran:
yum install e2fsprogs-devel apr-devel apr-util-devel expat-devel

and things worked again.

Steve Yan

unread,
Apr 16, 2009, 3:07:36 PM4/16/09
to Phusion Passenger Discussions
I ran into this same error, even after running:

yum install httpd-devel

which listed and installed apr-util-devel as a dependency. It wasn't
until I ran

yum install apr-util-devel

directory that I was able to fix this error. I'm not sure what yum is
doing in the background that makes this work in the 2nd case,.
Reply all
Reply to author
Forward
0 new messages