public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Ruottu <kai.ruottu@wippies.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Adding FORTRAN back to gcc tree
Date: Wed, 04 Jan 2012 15:40:00 -0000	[thread overview]
Message-ID: <4F0472C1.2010607@wippies.com> (raw)
In-Reply-To: <mcraa63y15c.fsf@dhcp-172-18-216-180.mtv.corp.google.com>

4.1.2012 16:48, Ian Lance Taylor kirjoitti:
> vikramsp<vikram2rhyme@gmail.com>  writes:
>
>> I have a gcc 4.1.2 source tree which do not have
>> gcc/fortran folder i.e. fortran support is not there.
>> Meant for C/C++ only with ARM arch.
>>
>> NOW I want to add fortran back. I just copied the fortran
>> folder from standard gcc 4.1.2 package and compiled for FORTRAN.
>> but errors are comming e.g.<undefined reference to c_lex>  etc.
>
> Presumably your gcc 4.1.2 source tree has some local changes.  You will
> have to adapt the Fortran frontend to those changes.
>
> If you tell us the exact error messages we might be able to say
> something more useful.  I don't see any references to c_lex in the gcc
> 4.1 Fortran frontend, so I suspect that something else is going on.

I remember it once told by someone that building only Fortran
(--enable-languages=fortran) doesn't work, one must build also
the C compiler (--enable-languages=c,fortran). Maybe this is
the case here?

  reply	other threads:[~2012-01-04 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 12:32 vikramsp
2012-01-04 14:48 ` Ian Lance Taylor
2012-01-04 15:40   ` Kai Ruottu [this message]
2012-01-19 14:07     ` vikramsp
2012-01-18 14:12   ` vikramsp

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=4F0472C1.2010607@wippies.com \
    --to=kai.ruottu@wippies.com \
    --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).