From: anonymous <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue59] gem install sup on osx 10.6 fails due to .bundle instead of .so being built in xapian-full
Date: Sun, 31 Jan 2010 21:38:24 +0000 [thread overview]
Message-ID: <1264973904.76.0.328276768293.issue59@masanjin.net> (raw)
In-Reply-To: <1264973904.76.0.328276768293.issue59@masanjin.net>
New submission from anonymous:
on a default os X 10.6 machine (after updating rubygems) doing a 'gem sup
install' fails:
The problem is xapian-full is making a .bundle instead of a .so. It's easy to
change to make a .so file (just remove the -bundle and chenge the output to .so,
but I know nothing of Ruby, or how to make ruby gems behave. I can manually
build the .so file, but then doing another 'gem install sup' just replaces the
directory I just fixed. So I don't even know of how to work-around this.
Below is the evil details:
p.cc
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I..
-I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0
-I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0
-fno-strict-aliasing -Wall -Wno-unused -Wno-uninitialized -fvisibility=hidden
-I/Users/tara/.gem/ruby/1.8/gems/xapian-full-1.1.3.1/xapian-core-1.1.3/include
-g -O2 -MT xapian_wrap.lo -MD -MP -MF .deps/xapian_wrap.Tpo -c xapian_wrap.cc
-fno-common -DPIC -o .libs/xapian_wrap.o
mv -f .deps/xapian_wrap.Tpo .deps/xapian_wrap.Plo
/bin/sh ../libtool --tag=CXX --mode=link g++ -fno-strict-aliasing -Wall
-Wno-unused -Wno-uninitialized -fvisibility=hidden
-I/Users/tara/.gem/ruby/1.8/gems/xapian-full-1.1.3.1/xapian-core-1.1.3/include
-g -O2 -avoid-version -module -shrext ".bundle" -o _xapian.la -rpath
/Library/Ruby/Site/1.8/universal-darwin10.0 xapian_wrap.lo
/Users/tara/.gem/ruby/1.8/gems/xapian-full-1.1.3.1/xapian-core-1.1.3/libxapian-1.1.la
-lstdc++
libtool: link: g++ -Wl,-undefined -Wl,dynamic_lookup -o .libs/_xapian.bundle
-bundle .libs/xapian_wrap.o
/Users/tara/.gem/ruby/1.8/gems/xapian-full-1.1.3.1/xapian-core-1.1.3/.libs/libxapian-1.1.dylib
-lz -lstdc++
libtool: link: dsymutil .libs/_xapian.bundle || :
libtool: link: ( cd ".libs" && rm -f "_xapian.la" && ln -s "../_xapian.la"
"_xapian.la" )
mkdir -p lib
cp xapian-bindings-1.1.3/ruby/.libs/_xapian.so lib
cp: xapian-bindings-1.1.3/ruby/.libs/_xapian.so: No such file or directory
rake aborted!
/Users/tara/.gem/ruby/1.8/gems/xapian-full-1.1.3.1/rakefile:6:in `system!'
(See full trace by running task with --trace)
Gem files will remain installed in
/Users/tara/.gem/ruby/1.8/gems/xapian-full-1.1.3.1 for inspection.
Results logged to /Users/tara/.gem/ruby/1.8/gems/xapian-full-1.1.3.1/gem_make.out
tara@mudita ~ % gem install ferret
----------
messages: 144
nosy: anonymous
priority: bug
ruby_version: 1.8.7
status: unread
sup_version: 0.10.2
title: gem install sup on osx 10.6 fails due to .bundle instead of .so being built in xapian-full
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue59>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next parent reply other threads:[~2010-01-31 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 21:38 anonymous [this message]
2010-01-31 22:53 ` Rich Lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1264973904.76.0.328276768293.issue59@masanjin.net \
--to=sup-bugs@masanjin.net \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox