Sam Steingold wrote:
> checking for pari/pari.h... yes
> ...
> configure:2970: gcc -o conftest.exe -g -O2 conftest.c -lpari >&5
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../../i686-pc-cygwin/bin/ld:
> cannot find -lpari
> collect2: ld returned 1 exit status
On many platforms, gcc by defa
Greetings,
I really love the feature to replace a autoconf variable
with content of a file, ie. using AC_SUBST_FILE.
But this feature would be of even greater value if variable
substitution would take place.
I wonder why this does not take place. Is there a technical
reason for this? Or is i
Greetings,
section 14. - recreating a configuration - of autoconf's
manual shows a rule on how to regenerate a Makefile, ie.
Makefile: Makefile.in config.status
./config.status Makefile
That works fine. However, I have a couple of Makefiles
in subdirectories. So generalized rule is t
Hi!
>subdir=<..>
>
>Makefile : Makefile.in
>cd $(top_builddir) && ./config.status $(subdir)/Makefile
>
> where "subdir" is the relative path name. For instance,
> in "src/Makefile.in" subdir would be "src".
>
> My "problem" is that I have to set "subdir" manually for
> each Makefile.
I really love the feature to replace a autoconf variable
with content of a file, ie. using AC_SUBST_FILE.
But this feature would be of even greater value if variable
substitution would take place.
What variable would you want to substitute? With what value?
Andre Caldas writes:
>> I really love the feature to replace a autoconf variable
>> with content of a file, ie. using AC_SUBST_FILE. But this feature
>> would be of even greater value if variable
>> substitution would take place.
> What variable would you want to substitute? With what value?
