public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neroden at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/14871] New: Non-unified-tree ordinary cross-compiler builds default to stupid names for tools
Date: Wed, 07 Apr 2004 02:04:00 -0000	[thread overview]
Message-ID: <20040407020349.14871.neroden@gcc.gnu.org> (raw)

>From Makefile.tpl: 
 
USUAL_AS_FOR_TARGET = ` \ 
  if [ -f $$r/gas/as-new ] ; then \ 
    echo $$r/gas/as-new ; \ 
... 
    if [ '$(host)' = '$(target)' ] ; then \ 
      echo $(AS); \ 
    else \ 
       echo as | sed '$(program_transform_name)' ; \ 
^^^^^^^^^^^^^^^ 
This isn't really what we're looking for, since program_transform_name is 
for the *newly built* tools, and the user may be supplying something weird, 
but it says nothing about where to find preexisting tools.  We should trust 
configure's choice, which is found using NCN_STRICT_TARGET_TOOL, and is 
essentially $(target_alias)-as (unless it was set by the user in some 
other way, of course). 
 
I have a patch for this already. 
 
     fi; \ 
   fi` 
 
Similarly for the other tools.  :-P

-- 
           Summary: Non-unified-tree ordinary cross-compiler builds default
                    to stupid names for tools
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Keywords: build
          Severity: minor
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: neroden at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: *
  GCC host triplet: *
GCC target triplet: *


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


             reply	other threads:[~2004-04-07  2:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07  2:04 neroden at gcc dot gnu dot org [this message]
2004-04-09  5:15 ` [Bug bootstrap/14871] " neroden at gcc dot gnu dot org
2004-04-09  5:15 ` cvs-commit at gcc dot gnu dot org
2004-05-26 20:56 ` pinskia at gcc dot gnu dot org
2004-08-25  4:13 ` pinskia at gcc dot gnu dot 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=20040407020349.14871.neroden@gcc.gnu.org \
    --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).