public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harry Powell <harry@mrc-lmb.cam.ac.uk>
To: gcc-help@gcc.gnu.org
Subject: linking problem with gfortran 4.2.0
Date: Fri, 09 Jun 2006 08:42:00 -0000	[thread overview]
Message-ID: <Pine.OSF.4.44.0606090922290.501999-100000@alf1.lmb.internal> (raw)
In-Reply-To: <4782372.post@talk.nabble.com>

Hi

Sorry if this has been answered elsewhere, but I can't find an obvious
reference to it. If this requires an RTFM, could you give me a clue where
in TFM? I found a reference to __gfortran_filename, __gfortran_ioparm, &
__gfortran_line in a discussion on threads but this didn't give an
obvious reason why I was suddenly encountering this error.

Note that the _only_ difference in my two builds is the compiler. All
libraries, flags, etc are identical (so it may just mean that I need to
add another library - but which one?).

I have been trying to build my code on an Intel iMac - with gfortran 4.0.3
compilation & linking goes okay and the executable is usable (though there
are some unwanted features introduced by small bugs in the compiler, which
I believe may have been addressed in newer versions).  With gfortran 4.2.0
I get the following error on linking (in both cases I use the command
"gfortran" for the linking, but this seems to explicitly invoke odcctools
in 4.2.0);

/sw/lib/odcctools/bin/ld: Undefined symbols:
__gfortran_filename
__gfortran_ioparm
__gfortran_line
collect2: ld returned 1 exit status
make[2]: *** [ipmosflm] Error 1
make[1]: *** [all] Error 2
make: *** [all] Error 2

The gfortran 4.2.0 was installed from the "unstable" branch of fink
(gcc4, 2:4.1.999-20060527).

**************************************************************
Compiler/linker details:

mosflm> /usr/local/bin/gfortran -v
Using built-in specs.
Target: i386-apple-darwin8.5.3
Configured with: ../gcc-4.0.3/configure --enable-languages=fortran
Thread model: posix
gcc version 4.0.3

mosflm> /sw/bin/gfortran -v
Using built-in specs.
Target: i386-apple-darwin8
Configured with: ../gcc-4.2-20060527/configure --prefix=/sw
--prefix=/sw/lib/gcc4 --disable-multilib
--enable-languages=c,c++,fortran,objc,java
--infodir=/sw/lib/gcc4/share/info --with-gmp=/sw --with-included-gettext
--host=i386-apple-darwin8 --with-as=/sw/lib/odcctools/bin/as
--with-ld=/sw/lib/odcctools/bin/ld --with-nm=/sw/lib/odcctools/bin/nm
Thread model: posix
gcc version 4.2.0 20060527 (experimental)

mosflm> /sw/lib/odcctools/bin/ld -v
Apple Computer, Inc. version odcctools-590.36od13
**************************************************************

I tried to do "make bootstrap" with gcc 4.1.1 to try that version, but
the build of the compiler failed (so that's another problem. ho hum...)

Harry
-- 
Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC Centre, Hills
Road, Cambridge, CB2 2QH


  reply	other threads:[~2006-06-09  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 20:50 ASM + CPP with gcc/gpp revis
2006-06-09  8:42 ` Harry Powell [this message]
2006-06-09 13:04   ` linking problem with gfortran 4.2.0 Tim Prince
2006-06-09 14:34     ` Harry Powell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.OSF.4.44.0606090922290.501999-100000@alf1.lmb.internal \
    --to=harry@mrc-lmb.cam.ac.uk \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).