Thanks again and again Ralph...
well I am at a lost with what happened... I wasn't running autoreconf
but diligently (or badly ? :) )typing the whole set of : libtoolize,
aclocal -I m4, autoconf, automake
I changed the else to what you suggested, ran autoreconf and it worked
when running confi
* Eve-Marie Devaliere wrote on Tue, Feb 01, 2011 at 09:37:04PM CET:
> first of all even with my
> AC_CONFIG_MACRO_DIR([m4]) in configure.ac (before macro calls)
> and ACLOCAL_AMFLAGS= -I m4 in Makefile.am (top one) , I still need to run
> aclocal with the '-I m4' else it doesn't recognize
> AX_F9
oops I think I spoke a little too fast. autoconf was not giving me
errors anymore but configure is still not happy
first of all even with my
AC_CONFIG_MACRO_DIR([m4]) in configure.ac (before macro calls)
and ACLOCAL_AMFLAGS= -I m4 in Makefile.am (top one) , I still need to run
aclocal wit
Thanks Chris, you were right on it. I had downloaded it from sourceforge
but yes it was apparently an older file
Thanks,
Cheers,
Eve-Marie
Christopher Hulbert said the following on 1/31/2011 12:40 PM:
> On Mon, Jan 31, 2011 at 12:21 PM, Eve-Marie Devaliere
> wrote:
>> Thanks Ralph! I am now
On Mon, Jan 31, 2011 at 12:21 PM, Eve-Marie Devaliere
wrote:
> Thanks Ralph! I am now trying to make my package more portable so I am
> working on the part below
>
>> Do you need the package to be very portable? If so, I suggest you go to
>> the Autoconf Macro Archive and grab two Fortran-related
Thanks Ralph! I am now trying to make my package more portable so I am
working on the part below
> Do you need the package to be very portable? If so, I suggest you go to
> the Autoconf Macro Archive and grab two Fortran-related macros,
> AX_F90_MODULE_EXTENSION and AX_F90_MODULE_FLAG.
>
> We the
On Tue, Jan 18, 2011 at 9:48 AM, Eve-Marie Devaliere
wrote:
> Good morning,
> Thanks all for your posts
> I haven't written the package and I am just trying to use autoconf to
> make the install easier...Just to say that I am trying to make sense of
> the package too... :) They are using modul
Good morning,
Thanks all for your posts
I haven't written the package and I am just trying to use autoconf to
make the install easier...Just to say that I am trying to make sense of
the package too... :) They are using modules so for each f90 file I need
a .o and .mod the -c -02... flags ar
On Fri, Jan 14, 2011 at 4:43 PM, Eve-Marie Devaliere
wrote:
> Hello Ralph and all,
>
> I think I have updated autoconf succesfully...
> Now it says:
> configure: error: Fortran compiler cannot create executables
Are you still passing "-c" in FCFLAGS as you indicated in your first 2
posts? If so,
- Original Message -
> As previously if I use -g only as my FCFLAGS instead of -c -O2
> -convert
> big_endian -free -assume byterecl , configure runs fine but then of
> course make doesn't
Try removing "-c" in FCFLAGS.
A.Chan
___
Autoco
On 01/14/11 13:43, Eve-Marie Devaliere wrote:
> configure:2486: checking whether the Fortran compiler works
> configure:2508: ifort -c -O2 -convert big_endian -free -assume
> byterecl conftest.f >&5
> configure:2512: $? = 0
> configure:2550: result: no
> configure: failed program was:
> |
Hello Ralph and all,
I think I have updated autoconf succesfully...
Now it says:
configure: error: Fortran compiler cannot create executables
If I check the log it says:
checking for Fortran compiler version
$FC --version >&5
configure:2460: ifort --version >&5
ifort (IFORT) 12.0.0 20101006
Copyr
ohh yes this look like the same issue indeed
yes I do have an old version...
I am trying to get the IT team to do it since this is how it works here
at NOAA... but I may be able to try installing in a local directory...
Thanks again!
Eve-Marie
Ralf Wildenhues said the following on 1/14/2011 2:
* Eve-Marie Devaliere wrote on Fri, Jan 14, 2011 at 08:07:47PM CET:
> well it is looking for b.out
> ---
> configure:1840: $? = 0
> configure:1854: checking for Fortran compiler default output file name
> configure:1857: ifort -c -O2 -convert big_endian -free -assume
> byterecl conftest.f >&
Hello Eve-Marie,
addressing the remaining part of your question:
* Eve-Marie Devaliere wrote on Fri, Jan 14, 2011 at 05:32:58PM CET:
> I have created my makefiles and configure.ac...
> I have read in the tutorial that FCFLAG had to be set to -g (unless it
> is g77).. Well I need to create *.mod a
Thanks Paul!
well it is looking for b.out
---
configure:1840: $? = 0
configure:1854: checking for Fortran compiler default output file name
configure:1857: ifort -c -O2 -convert big_endian -free -assume
byterecl conftest.f >&5
configure:1860: $? = 0
configure:1908: result: b.out
configure:19
On 01/14/11 09:23, Eve-Marie Devaliere wrote:
> checking whether the Fortran compiler works... configure: error: cannot
> run Fortran compiled programs.
Please check the output log: it should have a copy of the program
that couldn't run, along with how it was compiled and built.
This should let yo
I am sorry I think I figured out my own typo... it should be FCFLAGS not
FC_FLAGS... (For some reasons they had FC_FLAGS in their original program)
Now if I export FCFLAGS before running configure I can't even configure
; it is saying
checking whether the Fortran compiler works... configure: error:
Good morning autoconf community,
I am a newbie to autoconf and while I have made some good progress I am
hitting a road block.
I am taking this project from someone else and trying to use autoconf to
package it rather than the manual approach they had.
I have created my makefiles and configure.a
19 matches
Mail list logo
