public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmh at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/40191]  New: fails to build a cross-compiler in-tree
Date: Mon, 18 May 2009 20:42:00 -0000	[thread overview]
Message-ID: <bug-40191-12496@http.gcc.gnu.org/bugzilla/> (raw)

I found this when building a i586-mingw32 cross-compiler directly in srcdir. 
Build fails with:

make[2]: Entering directory `/tmp/trunk/i586-mingw32msvc/libgcc'
Makefile:143: ../.././gcc/libgcc.mvars: No such file or directory
make[2]: *** No rule to make target `../.././gcc/libgcc.mvars'.  Stop.

This happens because ${host_subdir} gets the wrong path (fallbacks to "."). 
The check in acx.m4 doesn't take into account that ${host_noncanonical} changes
its meaning when we switched from gcc/ to libgcc/.

Patch attached.


-- 
           Summary: fails to build a cross-compiler in-tree
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Keywords: build, patch
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rmh at gcc dot gnu dot org


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


             reply	other threads:[~2009-05-18 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 20:42 rmh at gcc dot gnu dot org [this message]
2009-05-18 20:43 ` [Bug target/40191] " pinskia at gcc dot gnu dot org
2009-05-18 20:45 ` rmh at gcc dot gnu dot org
2009-07-28 22:11 ` rmh 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=bug-40191-12496@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).