Re: linker question

Re: linker question

[Mumit Khan]

On Mon, 4 Jan 1999, Timothy Kohl wrote:

> Thanks, that worked, well at least I know that it's trying to do the compilation.
> I guess that egcs is not a full F90 compiler, either that or I'm not using
> the correct switches.
> 

In fact, far from it; g77 is a f77 compiler, with some of the popular 
extensions, a few of which are in f90, but it's definitely not a f90
compiler.

Regards,
Mumit

Re: linker question

[Dave Love]

>>>>> "TK" == Timothy Kohl <tkohl@it.bu.edu> writes:

 TK> This may sound like a naive question but it's one the
 TK> documentation wasn't clear about. How much of Fortran 90 does
 TK> egcs handle?

Please suggest how we could improve the docs, like what you were
looking for that might have led to the node `Fortran 90 Features'.
Thanks.

Re: linker question

[Timothy Kohl]

> Timothy Kohl <tkohl@it.bu.edu> writes:
> 
> > $ /software/egcs/bin/bin/g77 -ff90 f90_tools.f90
> > /usr/bin/ld:f90_tools.f90: file format not recognized; treating as linker script
> > /usr/bin/ld:f90_tools.f90:1: parse error
> > collect2: ld returned 1 exit status
> > $

 
> It looks like ".f90" is not recognized by the driver as a suffix for a
> Fortran input file.  I suggest you rename the files to have a ".f"
> suffix.  If you can't do that, adding "-x f77" to the command line
> before the .f90 files should do the trick.  ("f77" is the internally
> used name of the language, even if you're using an option to get the
> Fortran 90 dialect.)
 
Thanks, that worked, well at least I know that it's trying to do the compilation.
I guess that egcs is not a full F90 compiler, either that or I'm not using
the correct switches.

				Thanks,
					TK

linker question

[Timothy Kohl]

Hi,

I recently installed egcs 1.1.1 on an Alpha Linux box for one of our users.
This person tried compiling an f90 program but kept getting the following error
message:

$ /software/egcs/bin/bin/g77 -ff90 f90_tools.f90
/usr/bin/ld:f90_tools.f90: file format not recognized; treating as linker script
/usr/bin/ld:f90_tools.f90:1: parse error
collect2: ld returned 1 exit status
$

This may sound like a naive question but it's one the documentation wasn't 
clear about. How much of Fortran 90 does egcs handle?
(i.e. Is egcs really an F90 compiler?)

The version of gld in use is GNU ld version 2.9.1 (with BFD 2.9.1.0.15)
My question is this, do I need to install a new gld? 
If so, where can I find source for gld?

Any info would be appreciated.

		Thanks,
	
			-TK

Re: linker question

[Ken Raeburn]

Timothy Kohl <tkohl@it.bu.edu> writes:

> $ /software/egcs/bin/bin/g77 -ff90 f90_tools.f90
> /usr/bin/ld:f90_tools.f90: file format not recognized; treating as linker script
> /usr/bin/ld:f90_tools.f90:1: parse error
> collect2: ld returned 1 exit status
> $

It looks like ".f90" is not recognized by the driver as a suffix for a
Fortran input file.  I suggest you rename the files to have a ".f"
suffix.  If you can't do that, adding "-x f77" to the command line
before the .f90 files should do the trick.  ("f77" is the internally
used name of the language, even if you're using an option to get the
Fortran 90 dialect.)

> The version of gld in use is GNU ld version 2.9.1 (with BFD 2.9.1.0.15)
> My question is this, do I need to install a new gld? 
> If so, where can I find source for gld?

It's not a linker issue.  The g77 driver passes files with
unrecognized suffixes through to the linker, and the linker doesn't
(and never will) know what to do with a Fortran source file.

Re: linker question

[H . J . Lu]

On Sun, Jun 17, 2001 at 12:43:01AM +0200, Arkadiusz Miskiewicz wrote:
> 
> Hi,
> 
> I tried to compile gcc 3.0 (20010615 snap) but unfortunately:
> ...
> /home/users/builder/rpm/BUILD/gcc-3.0-20010615/obj-i686-pld-linux/gcc/xgcc
> -B/home/users/builder/rpm/BUILD/gcc-3.0-20010615/obj-i686-pld-linux/gcc/
> -B/usr/i686-pld-linux/bin/ -B/usr/i686-pld-linux/lib/ -isystem
> /usr/i686-pld-linux/include -shared  .libs/prims.o .libs/posix.o ........
> .libs/posix-threads.o -Wl,--whole-archive
> ../libffi/.libs/libfficonvenience.a ./libltdl/.libs/libltdlc.a
> -Wl,--no-whole-archive
> -L/home/users/builder/rpm/BUILD/gcc-3.0-20010615/obj-i686-pld-linux/i686-pld-linux/libjava
> ../libffi/.libs/libfficonvenience.a -lpthread
> ./libltdl/.libs/libltdlc.a -ldl   -lc  -Wl,-soname -Wl,libgcj.so.2 -o
> .libs/libgcj.so.2.0.0
> /usr/bin/ld: .libs/libgcj.so.2.0.0: undefined versioned symbol name
> __register_frame_info@@GLIBC_2.0/usr/bin/ld: failed to set dynamic
> section sizes: Bad value
> collect2: ld returned 1 exit status
> make[3]: *** [libgcj.la] Error 1
> 
> [misiek@arm misiek]$ objdump -T /lib/libc.so.6  | grep _register_frame_info
> 000fb090 g    DF .text	0000007a  GLIBC_2.0   __register_frame_info_table
> 000fafd4 g    DF .text	0000007e  GLIBC_2.0   __register_frame_info
> 
> glibc-2.2.3-3
> gcc-2.95.3-1
> binutils-2.11.90.0.15-1
> 2.4.5 on x86
> 
> Any suggestions?

I believe gcc 3.0 is broken.


H.J.