public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eisoab at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49438] error during make
Date: Thu, 16 Jun 2011 17:57:00 -0000	[thread overview]
Message-ID: <bug-49438-4-WorpRPYFOs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49438-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49438

--- Comment #5 from eisoab at gmail dot com 2011-06-16 17:56:10 UTC ---
sgk at troutmask dot apl.washington.edu wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49438
>
> --- Comment #4 from Steve Kargl<sgk at troutmask dot apl.washington.edu>  2011-06-16 17:52:39 UTC ---
> On Thu, Jun 16, 2011 at 05:36:35PM +0000, eisoab at gmail dot com wrote:
>>
>>> What is the configure command line you used to configure
>>> the gcc?
>>>
>>>
>> nothing. just ../configure
sorry that was incorrect, I meant

../gcc-4.5.3/configure

I'm using a gcc-4.5.3-build dir next to gcc-4.5.3

Eiso

>>
>
> This appears to mean that you are trying to build
> gcc within its source tree.  That is not support.
> Please the instructions for building gcc.
>
>>
>> I probably have to remove the old gmp version right?
>>
>
> This would certainly ensure that the old versions are
> not found and used.
>


  parent reply	other threads:[~2011-06-16 17:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 12:53 [Bug fortran/49438] New: " eisoab at gmail dot com
2011-06-16 13:40 ` [Bug fortran/49438] " burnus at gcc dot gnu.org
2011-06-16 16:32 ` kargl at gcc dot gnu.org
2011-06-16 17:36 ` eisoab at gmail dot com
2011-06-16 17:53 ` sgk at troutmask dot apl.washington.edu
2011-06-16 17:57 ` eisoab at gmail dot com [this message]
2011-06-16 18:08 ` eisoab at gmail dot com
2011-07-24 18:42 ` dfranke at gcc dot gnu.org
2011-11-07 22:48 ` fxcoudert at gcc dot gnu.org
2011-11-07 22:53 ` fxcoudert at gcc dot gnu.org

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=bug-49438-4-WorpRPYFOs@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).