James C. Sutherland wrote:
> Let me try this again.
>
> I have a f90 subroutine that performs file IO. I would like to link
> that with a C++ driver.
>
> If I use a fortran driver, I am able to set the binary format via
> set( CMAKE_Fortran_FLAGS "-fconvert=big-endian" )
> This results in
Isn't that a compiler flag? You would have to specify that
at compile time, not link time.
Regards,
Arjen
On 2009-04-01 01:33, James C. Sutherland wrote:
Alin,
Thank you for your patience. I now have this set via
set( CMAKE_EXE_LINKER_FLAGS "-mbig-endian" )
However, this does not seem to af
Elena,
Try to compile and link by hand. For example - write one CPP, one F90, then
compile them with flags you want and link them with flags you want. After you
find out, what you need, you may start experimenting with CMake flags.
gmake VERBOSE=1
can help you alot to see what is happening du
Alin,
Thank you for your patience. I now have this set via
set( CMAKE_EXE_LINKER_FLAGS "-mbig-endian" )
However, this does not seem to affect the reading of the big-endian
binary file (which is in read in fortran). Perhaps I am still not
setting it properly?
James
On Mar 31, 20
man g++
add_definition is a preprocessor directive not linking flag
Alin
--
__
"If the Universities will not study useless subjects, who will?"
G. F. FitzGerald, Nature, 45/46, 392 (1892)
_
Let me try this again.
I have a f90 subroutine that performs file IO. I would like to link
that with a C++ driver.
If I use a fortran driver, I am able to set the binary format via
set( CMAKE_Fortran_FLAGS "-fconvert=big-endian" )
This results in file IO in big-endian format.
When u
g++ knows of -mbig-endian not -f
g++ --help -v provides no information on any endian operations.___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-to
If you want to pass something to g++ linker, you should do this with
-Wl,--my-special-flag
Denis
> > Should not the flag be passed to the linker? So in
> this case the linker flags are read from the c++ compiler
> flags?
> >
>
> I tried adding
> add_definitions( ${CMAKE_Fortran_FLAGS}
Hi,
g++ knows of -mbig-endian not -f
Anyhow is just a thought.
Alin
--
__
"If the Universities will not study useless subjects, who will?"
G. F. FitzGerald, Nature, 45/46, 392 (1892)
Should not the flag be passed to the linker? So in this case the
linker flags are read from the c++ compiler flags?
I tried adding
add_definitions( ${CMAKE_Fortran_FLAGS} )
But the g++ linker complained about an unrecognized option (the -
fconvert=big-endian option).
When linking
Hi,
Should not the flag be passed to the linker? So in this case the linker flags
are read from the c++ compiler flags?
regards,
Alin
--
__
"If the Universities will not study useless subjects, who will?"
I am trying to compile a mixed f90/C++ program linked with g++.
The fortran compiler flags don't seem to be automatically passed
through to the g++ linker.
For example, I want to do:
set( CMAKE_Fortran_FLAGS "-fconvert=big-endian" )
When I do this for a fortran program (linked with g
12 matches
Mail list logo