Which version of automake is being used in the failure cases?  I'm using
automake 1.4-p2 (automake --version).


The substitution happens correctly for me:

@libdir@/ggi -> /usr/lib/ggi

The only thing that maybe should be added is a ggi_libdir similar to
ggi_confdir.  That way if you don't want /usr/lib/ggi but instead want
/usr/lib/general_graphics_interface you could do so.  But that change
would then be this:

@libdir@/@ggi_libdir@

This wouldn't require all the hacks that are being discussed.

On 06 Jul 2001 09:32:13 -0600, Thayne Harbaugh wrote:
> This disturbs me because the substitution was happening for me - that's
> why I submitted the patch to the list.  I'll look closer.
> 
> On 06 Jul 2001 13:11:44 +0200, Christoph Egger wrote:
> > 
> > On Fri, 6 Jul 2001, Andreas Beck wrote:
> > 
> > > > Another solution is to go back to the original configure.in, where we
> > > > didn't have the ${prefix} problem and force the package maker to
> > > > determine the install-path _before_ compilation, so that $sysconfdir
> > > > wouldn't be changed.
> > > 
> > > Why does the problem occur ? Can anyone explain, why the variables don't 
> > > get expanded in the libggi.conf.in and in the source ?
> > 
> > Because the variables are no longer evaluated/substituted with
> > Thayne's fix as they were before.
> >  
> > > > Perhaps we should provide a script, which asks the package makers,
> > > > which install path he wants to use (of course it should suggest the
> > > > default path). Then the script automatically does the building
> > > > process and generates the package.
> > > 
> > > Hmm - looks like quite a hack. (not worse than my rpm-from-installed-dirs-
> > > hack, though.
> > 
> > Yep.
> >  
> > > Also please note, that there is the patchlib executable built, which is 
> > > intended to allow for patching a binary LibGGI built so that it will
> > > change the path it looks for the primary config file.
> > 
> > Does patchlib only work for libggi or does it work for each lib?
> > 
> > I the last case calling patchlib at install-time would be a good way
> > to solve the conf-file not found error, because we can replace the
> > ${prefix} by the install-path prefix (i.e. /usr/local).
> > 
> > 
> > CU,
> > 
> > Christoph Egger
> > E-Mail: [EMAIL PROTECTED]
> > 
> 
> -- 
> Thayne Harbaugh

-- 
Thayne Harbaugh



Reply via email to