JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for COMP-FORTRAN-90 Archives


COMP-FORTRAN-90 Archives

COMP-FORTRAN-90 Archives


COMP-FORTRAN-90@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

COMP-FORTRAN-90 Home

COMP-FORTRAN-90 Home

COMP-FORTRAN-90  2000

COMP-FORTRAN-90 2000

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Lahey lf95 Express and gcc on Linux x86 [LONG]

From:

José Luis Gómez Dans <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Thu, 26 Oct 2000 19:39:17 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (101 lines)

Hi!
	FIrst of all, I've been posting and asking about this all day
today, and looking for a mailing list, without actually noticing there
was one in mailbase mentioned in the first paragraph of the fortran
90/95 news... brrrrr brrrr. I also hope this question isn't off-topic,
since it's probably more a gcc question than a ftn90 question :-)

	My apologies if you get this question twice (I also posted in
comp.lang.fortran).

	Anyway, I have some code (several modules) written with Lahey
lf95 express for Linux. They all compile fine (loads of assembler
warnings, but the code is OK), and produce the right results. I now want
to have a GUI for this software and started coding it in C to make use
of GTK+. As it is, I want to make use of the fortran code. Basically,
the interfacing should be straightforward, as I just pass a struct to
the fortran function that does everything. This is the first bit that
puzzled me, but more on that later.

	I read Lahey's manual on mixed language programming. It all
looks clear: you can call the subroutines within a module with the
syntax 
	modulename@subroutinename_(parameter list)
	So I compiled my module without linking with 
	$ lf95 -c modulename.f90 @imsllf95.cmd
(I link against the IMSL libraries as well, so they need to be included
here), which produces the modulename.o file as expected. I then wrote
a simple test program to call that function in C:
extern void modulename@subroutinename_(struct thing *);
void MAIN__(void)
  {
	modulename@subroutinename_(my_variable);
  }
	This is then compiled with gcc 2.95.2:
$ gcc -c -Wall -o f95wrap.o f95wrap.c
/tmp/ccKcRmel.s: Assembler messages:
/tmp/ccKcRmel.s:22: Error: bad reloc specifier in expression
/tmp/ccKcRmel.s:22: Error: ignoring junk `subroutinename_' after
expression

	So, gcc (in fact, as) dosn't understand the "@" as part of the
function name. Now, I defined the subroutine name simply as
subroutinename_():
gcc -c -Wall -o f95wrap.o f95wrap.c
	Hooray! This compiles without a single warning. Let's now
compile the f90 and C together with lf95...

$ lf95 -o prog SAR.o f95wrap.o @imsllf95.cmd
/usr/bin/lf95: sourcedir/y/bin/lf95: No such file or directory
/usr/local/lf9555/bin/../lib/libfj9i6.so: the use of `tempnam' is
dangerous, better use `mkstemp'
f95wrap.o: In function `MAIN__':
f95wrap.o(.text+0x1c): undefined reference to `process_sar_data_'

	The first few lines are normal, and seem to be there
irrespective of any program that I compile. Usually, loads of warnings
are issued for the assembly, but it looks as if it works :). The problem
here is that it doesn't recognize the process_sar_data_ subroutine. I
then decided to look into the symbols in the object file, using nm
(nm (1) - list symbols from object files.). The output of this command
is quite exhaustive, but of interest (I think):

$nm SAR.o
[...]
00002c8 R .jwe_ssn_sar_processing.process_sar_data_
[...]
00004210 T sar_processing.process_sar_data_
[...]

	So it looks as if the references have a dot (.) and not an
"@"!!!! Back to the C program, change the @ for the dot, and it won't
even compile (parse error):
$ gcc -c -Wall -o f95wrap.o f95wrap.c
f95wrap.c:15: parse error before `.'
f95wrap.c: In function `MAIN__':
f95wrap.c:20: `sar_processing' undeclared (first use in this function)
f95wrap.c:20: (Each undeclared identifier is reported only once
f95wrap.c:20: for each function it appears in.)

	So this is where I struggle at the moment. I can easily call
subroutines that aren't inside a module (just the underscore is needed),
but as soon as they're in a module, no hope. I have also tried to get
rid of the modules, but that would be equivalent to starting from
scratch...

	Can anyone shed any light on this? I am at a complete loss.

		Thank you,
		José



-- 
José L Gómez Dans			PhD student
					Radar & Communications Group
					Department of Electronic Engineering
					University of Sheffield UK


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
February 2023
November 2022
September 2022
February 2022
January 2022
June 2021
November 2020
September 2020
June 2020
May 2020
April 2020
December 2019
October 2019
September 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
April 2015
March 2015
January 2015
December 2014
November 2014
October 2014
August 2014
July 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
July 2013
June 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
August 2010
July 2010
June 2010
March 2010
February 2010
January 2010
December 2009
October 2009
August 2009
July 2009
June 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager