From: Toon Moene <toon@moene.indiv.nluug.nl>
To: f.braennstroem@gmx.de
Cc: gcc-help@gcc.gnu.org
Subject: Re: multiple definition of `MAIN__'
Date: Tue, 30 Dec 2003 13:50:00 -0000 [thread overview]
Message-ID: <3FF18424.80608@moene.indiv.nluug.nl> (raw)
In-Reply-To: <1072736184.2717.19.camel@rechner1.ddorf.de>
Fabian Braennstroem wrote:
> THAT is the correct error-message:
>
> save_vel.o(.text+0xcd1): In function `MAIN__':
> : multiple definition of `MAIN__'
> main.o(.text+0x0): first defined here
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/../../../../i686-pc-linux-gnu/bin/ld: Warning: size of symbol `MAIN__' changed from 5155 in main.o to 5 in save_vel.o
> save_pres.o(.text+0x763): In function `MAIN__':
> : multiple definition of `MAIN__'
> main.o(.text+0x0): first defined here
> collect2: ld returned 1 exit status
> make: *** [calc_les_03_cube] Error 1
Ah, this is a slightly different problem. Somehow, g77 thinks there is
a main program in the file save_vel.f - this can happen if you have a
single (extraneous) END statement for instance.
If you can't find the problem, send me (and only me - not the list) the
whole file save_vel.f and I'll take a look.
Cheers,
--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://gcc.gnu.org/fortran/ (under construction)
next prev parent reply other threads:[~2003-12-30 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 18:58 Fabian Braennstroem
2003-12-28 19:59 ` Fabian Braennstroem
2003-12-28 20:22 ` SORRY again, " Fabian Braennstroem
2003-12-29 13:03 ` Toon Moene
2003-12-29 22:15 ` Fabian Braennstroem
2003-12-30 13:50 ` Toon Moene [this message]
2003-12-31 9:08 ` Fabian Braennstroem
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=3FF18424.80608@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=f.braennstroem@gmx.de \
--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).