Hello Navneet,
* Navneet Dalal wrote on Fri, Jun 13, 2008 at 09:13:48AM CEST:
> If my makefile.am looks as following, then it automatically generates
> mybinary_DEPEDENCIES and set it to ../lib/libutil.la
> bin_PROGRAMS= mybinary
> LDADD= ../lib//libutil.la
> mybinary_SOURCES = mybinary.c
Hello Jan,
* Fugitive wrote on Thu, Jun 12, 2008 at 06:42:24PM CEST:
>
> Simply overriding FFLAGS in Makefile.am generates warning from Automake but
> it does the trick.
You can do that, in combination with 'AUTOMAKE_OPTIONS = -Wno-override',
> QUESTION: Is there another way over override FFLAG
Hi all, I am facing a strange problem. Can someone point out where am
I going wrong.
If my makefile.am looks as following, then it automatically generates
mybinary_DEPEDENCIES and set it to ../lib/libutil.la
bin_PROGRAMS= mybinary
LDADD= ../lib//libutil.la
mybinary_SOURCES = mybinary.
I have a package which uses LAPACK. Since many users don't have it
installed, or because it is compiled with another Fortran compiler than the
one that is installed on their system (and hence used as a linker) I end up
getting many questions from people.
I want to go for the solution also used i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kamaljit Singh wrote:
> Hi,
>
> I maintain my build tree separate to src tree which has all the
> Makefile.am's.
> Is it possible that all generated files (including the Makefile.in's and the
> various cache) be in the build tree ?
>
> kamaljit
>
Brian, thanks very much. Your post was very educational for me! My problem
is mostly solved now (I have everything compiling and going into the right
place, anyway), and I only need to clean up the scripts a bit. My main
problem was realizing that for my situation, it was best to not have a
configu
