public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Langella Raphael" <raphael.langella@steria.cnes.fr>
To: <gcc-help@gcc.gnu.org>
Subject: RE: Wrong assembler used with gcc 4.3.0 on Solaris 9
Date: Wed, 02 Apr 2008 12:41:00 -0000	[thread overview]
Message-ID: <092785B790DCD043BA45401EDA43D9B50210CD80@cst-xch-003.cnesnet.ad.cnes.fr> (raw)
In-Reply-To: <47F32859.1030406@tuliptree.org>

> -----Message d'origine-----
> De : gcc-help-owner@gcc.gnu.org 
> [mailto:gcc-help-owner@gcc.gnu.org] De la part de Jim Wilson
> Envoyé : mercredi 2 avril 2008 08:32
> À : Langella Raphael
> Cc : gcc-help@gcc.gnu.org
> Objet : Re: Wrong assembler used with gcc 4.3.0 on Solaris 9
> 
> Langella Raphael wrote:
> > I don't understand why the default solaris assembler is 
> used instead of the binutils one (which can be found at the 
> very beginning of my PATH).
> 
> GCC has its own built-in paths for finding things.  The best 
> solution here is to always use the same --prefix when 
> configuring binutils and gcc.  And build and install binutils 
> before building and installing gcc. 
>   Then gcc should automatically find binutils and everything 
> should just work.
> 
> If it still doesn't work, you might need to add extra 
> configure options like --with-gnu-as=/path/to/gnu/as, but 
> these aren't needed normally.
> 
> Jim
> 

Thanks for your advice. I've found a solution by setting COMPILER_PATH to my binutils.
To answer Dennis who asked why I don't use the native as and ld, it's because it doesn't work. That's the point of my initial post.

  reply	other threads:[~2008-04-02  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01  9:43 Langella Raphael
2008-04-01 16:39 ` John Morrison
     [not found]   ` <3FAC2F0B26D73F40A8202BB63110F57801AF127E@irvmail.misirvine.printronix      .com>
2008-04-01 17:16     ` Dennis Clarke
2008-04-01 17:32       ` John Morrison
     [not found]         ` <3FAC2F0B26D73F40A8202BB63110F57801AF12BD@irvmail.misirvine.printronix      .com>
2008-04-01 18:14           ` Dennis Clarke
2008-04-01 18:18             ` John Morrison
     [not found]               ` <3FAC2F0B26D73F40A8202BB63110F57801AF1316@irvmail.misirvine.printronix      .com>
2008-04-02  6:32                 ` Dennis Clarke
2008-04-02  7:55   ` Jim Wilson
2008-04-02  6:33 ` Jim Wilson
2008-04-02 12:41   ` Langella Raphael [this message]
     [not found]     ` <092785B790DCD043BA45401EDA43D9B50210CD80@cst-xch-003.cnesnet.ad.cnes.      fr>
2008-04-02 21:46       ` Dennis Clarke

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=092785B790DCD043BA45401EDA43D9B50210CD80@cst-xch-003.cnesnet.ad.cnes.fr \
    --to=raphael.langella@steria.cnes.fr \
    --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).