public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dep, Khushil (GE Money)" <Khushil.Dep@ge.com>
To: "Tim Prince" <tprince@computer.org>, "tsah marco" <tsahmarco@gmail.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: First Compilation of GCC
Date: Mon, 10 Dec 2007 13:49:00 -0000	[thread overview]
Message-ID: <D5C95A553071344EBDB133B851C31DDE73C162@LONMLVEM07.e2k.ad.ge.com> (raw)
In-Reply-To: <475D36DF.3070905@computer.org>

Ah yes - the chicken and egg problem :-) Has anyone come up with an
answer to that one btw ;-) 

-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Tim Prince
Sent: 10 December 2007 12:54
To: tsah marco
Cc: gcc-help@gcc.gnu.org
Subject: Re: First Compilation of GCC

tsah marco wrote:

>> i am working with suse 10.3 and trying to configure gcc-4.1.2, i am 
>> working with AMD TURION proccessor on the host and on the target,
>>
>> my first step was:
>> cd /opt/gcc
>> tar zxvf gcc-4.1.2.tar.gz
>> then i am trying to configure by:
>> ./configure --prefix=/opt/gcc-4.1.2 --exec-prefix=/opt/gcc-4.1.2 
>> --bindir=/opt/gcc-4.1.2/bin

>> configure: error: no acceptable cc found in $PATH
>>
>> what is the problem with my ./configure, i  add the current path 
>> /opt/gcc/gcc-4.1.2  to the PATH.
>> and still the same problem,
>> any idea ?

Start by using the gcc which is an optional part of your SUSE
installation.  If you didn't install it, open up YaST and install from
your DVD.  Then, read the instructions before attempting the configure
of the source code version.


  reply	other threads:[~2007-12-10 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <23dcc150712100425u3c990605g2d3f9e949e309e8e@mail.gmail.com>
2007-12-10 12:37 ` tsah marco
2007-12-10 13:02   ` Tim Prince
2007-12-10 13:49     ` Dep, Khushil (GE Money) [this message]
2007-12-10 18:29       ` Brian Dessent
2007-12-11 14:19         ` Dep, Khushil (GE Money)

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=D5C95A553071344EBDB133B851C31DDE73C162@LONMLVEM07.e2k.ad.ge.com \
    --to=khushil.dep@ge.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=tprince@computer.org \
    --cc=tsahmarco@gmail.com \
    /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).