> Bruce Momjian <maillist@candle.pha.pa.us> writes:
> >> Oh ... OK, that looks like a garden-variety configure bug (one too many
> >> levels of quoting, or some such). I can look at this if no one else
> >> beats me to it.
>
> > It replaces @libdir@ with ${exec_prefix}/lib. It appears the
> > configure code expects the replacement to occour in a Makefile, so
> > ${exec_prefix} can be replaced in Makefile.global. However,
> > $exec_prefix is not in Makefile.global, so maybe it is just a problem
> > with configure that $exec_prefix is replace before @libdir@, and
> > libdir's that contain exec_prefix have a problem.
>
> configure is designed to generate makefiles that look like this:
>
> exec_prefix=/usr/local
> bindir=${exec_prefix}/bin
> libdir=${exec_prefix}/lib
>
> with the notion that this will simplify after-the-fact hand tweaking
> of install destinations in the makefile if you feed a need to do that.
> So that's why libdir's default definition looks the way it does.
Tom, I like your fix in configure.in better than adding a silly
Makefile�rule. Yours is much cleaner. You just created an
expanded_libdir in configure.in and let that be expanded in the *.in
files. Great.
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026