Help with compiling bonobo please.

["Stephen J. Turnbull" <turnbull@example.com>]

>>>>> "Antony" == Antony Stace <antony@example.com> writes:

    Antony> It seems that the bonobo configure script is looking at

    Antony> /usr/bin/orbit-config

Is this a literal, hard-coded into the bonobo configure?  If so, you
should complain to the bonobo people.  What should happen is that
configure picks this up by searching the PATH.

    Antony> Should I

    Antony> 1.  Change the variable ac_default_prefix in both scripts
    Antony> to /usr/bin or

    Antony> 2.  Change the variable ac_default_prefix in
    Antony> /tmp/bon/bonobo-0.26/configure or

No.  Never touch the autoconf scripts unless you know what you're
doing.

    Antony> 3.  Something else since this will break something.

First, use `./configure --help' to find out if there is an option
specifically to deal with this.  Manipulating PATH may also help.

The obvious thing is to use `./configure --prefix=/usr'.  This will
create Makefiles to install binaries in /usr/bin, admin binaries in
/usr/sbin, libraries in /usr/lib, man pages in /usr/man, ... you get
the idea.  The prefix variable applies only to the install process;
configure searches for the necessary libraries etc without consulting
$prefix.

But first, what are you worried about breaking?  If you're not worried
about your ORBit 0.5.1 installation, and you want to overwrite it,
just use `./configure --prefix=/usr' when building ORBit.  The problem
is that this will very possibly confuse your package manager when you
try to upgrade to ORBit 0.5.5 from the Linux vendor.  (It mostly
doesn't, but it could.)  If you want to continue using ORBit 0.5.1
with most of your software, but the new ORBit with bonobo, it will be
difficult.  It probably doesn't much matter what you do with bonobo if
you opt to replace your old ORBit with 0.5.4.

If you do not, I would put the new ORBit not in /usr/local, but in
/usr/local/ORBit-0.5.4 (you just invoke ORBit's configure with
`./configure --prefix=/usr/local/ORBit-0.5.4').  (/usr/local is a good
place for stanard stuff not provided by the vendor.  But if you plan
to run multiple versions of a given package depending on the
application, use package- and version-specific paths.)  Then if you're
lucky, invoking bonobo's configure with

	  PATH=/usr/local/ORBit-0.5.4/bin:$PATH ./configure

will win (that's what these $PACKAGE-config scripts are supposed to do
for you).

If not, you probably need to give bonobo's configure some options like
--with-local-prefix or more specifically --with-includes and
--with-libraries, and then you'll probably need to wrap the bonobo
stuff with a script that sets the environment variables
LD_LIBRARY_PATH and PATH.

I recommend you just overwrite ORBit and pray.

-- 
University of Tsukuba                Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences       Tel/fax: +81 (298) 53-5091
_________________  _________________  _________________  _________________
What are those straight lines for?  "XEmacs rules."