Bruce Korb <bruce.k...@gmail.com> writes:
> On 10/10/13 13:50, Eric Bavier wrote:
>> Why not use LIBGUILE_PATH=`guile-config info libdir` instead?
>
> Because, cleverly, not all distributions distribute (install)
> guile-config.
I suggested the guile-config option because I saw that guile-config was
already being used in one of the configure paths.
> A better question is why doesn't Guile provide a guile.m4 file that derives
> all the information one might need? They can supply it to gnulib, if they
> don't want to provide it themselves.
I can forward the question to the guile developers.
> Meanwhile, I will add --with-libguile-path that overrides the derived
> LIBGUILE_PATH value.
That should work, as long as you make the intent of the option clear
enough.
Also, I was wondering, since the problem is essentially that the the
current method picks the wrong path from "-L${path1} -L${path2}",
couldn't the configure macro do a loop over all paths and look for the
one that has a bin directory containing the executables needed by
autogen?
> Cheers - Bruce
--
Eric Bavier, Scientific Libraries, Cray Inc.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Autogen-users mailing list
Autogen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/autogen-users
