Thanks for the confirmation and the advice, Peter.
I have gone with my original workaround, using
./configure --with-uninst-gii=../libgii-1.0.2
--with-extra-libs=../libgii-1.0.2/gg/.libs:../libgii-1.0.2/g
ii/.libs CC=icc
CXX=icpc
which means that I can build for the standard location, but
the libraries
and configuration files can be installed in a different
location on the
build machine.
-----Original Message-----
From: Peter Rosin [mailto:peda lysator.liu.se]
Sent: 06 November 2007 09:37
To: ggi-userslists.sourceforge.net
Cc: Morrell Richard
Subject: Re: [ggi-users] Possible bug configuring GGI with
the
--with-uninst-gii option
On Tue, Nov 06, 2007 at 10:17:23AM +0100, Peter Rosin
wrote:
> On Tue, Oct 23, 2007 at 03:06:12PM +0100, Morrell
Richard wrote:
> > Thanks for your reply, Christoph.
> >
> > I'm still not sure about the use of --prefix,
though.
> >
> > If I configure GII and GGI with
--prefix=/home/developer/ggi, on machine
> > "build" and do a make and a "make
install" for both, I will get the
> > libraries installed in /home/developer/ggi/lib,
the configuration files
> > installed in /home/developer/ggi/etc, and so on.
> >
> > If I then copy these files to /usr/local/lib and
/usr/local/etc on
machine
> > "target" (which does not have a
development environment) then, as I
> > understand it, the libraries will look for their
configuration files in
> > /home/developer/ggi/etc. This directory does not
exist on the target
> > machine, so the libraries will not find them.
> >
> > Is this a correct understanding of how --prefix
works (fixes the
location of
> > the configuration files at library build time) ?
>
> Yes, you are correct. The path to the config file is
compiled into the
> library. Which of course also means that DESTDIR
installs are broken
> and that the --with-uninst-* configure options are not
really that
> useful.
>
> I think the small program patchlib in the libggi tree
(in the root
> of the source tree) can be used to alter the location
of where the
> libraries will look for thier respective config files.
>
> Patchlib will look for the cookie pAtHTAg an write the
path after
> that cookie. Beware though, libgii has seen some
changes so it
> doesn't add any padding after the original path.
Therefore, with
> libgii you can only write a shorter path than the
originally
> configured path. This is not a problem with libggi
which has
> sufficient padding for and non-insane path.
Hmm, I took a quick peek at the patchlib source and it can't
be
used to patch libgii as it will always clobber things after
the
originally configured path (unless you originally configure
a path
with 256+ characters)
Sorry for the previous bad advise, but you can still do it
manually
with an editor, just look up pAtHTAg and fill in your
desired path
directly afterwards...
Maybe something like
sed -e
's,pAtHTAg...................,pAtHTAg/usr/local/etc/ggix00,
'
works? But x00 for the string terminator is a GNU sed
extension...
Cheers,
Peter
This email, including any attachment, is a confidential
communication
intended solely for the use of the individual or entity to
whom it is
addressed. It contains information which is private and may
be proprietary
or covered by legal professional privilege. If you have
received this email
in error, please notify the sender upon receipt, and
immediately delete it
from your system.
Anything contained in this email that is not connected with
the businesses
of this company is neither endorsed by nor is the liability
of this company.
Whilst we have taken reasonable precautions to ensure that
any attachment to
this email has been swept for viruses, we cannot accept
liability for any
damage sustained as a result of software viruses, and would
advise that you
carry out your own virus checks before opening any
attachment.
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
ggi-users mailing list
ggi-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ggi-users
|
