public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Drew Bliss <drewb@valvesoftware.com>
To: "'crossgcc@sourceware.org'" <crossgcc@sourceware.org>
Subject: crosstool-ng 1.19.0 fails to build i686-unknown-mingw32
Date: Mon, 20 Jan 2014 23:50:00 -0000	[thread overview]
Message-ID: <081118858EAEC94C9E4EE628510B31CD13227D62@exchange10.valvesoftware.com> (raw)

This is the same issue that Daniel Pauli mailed about in Mar 2013 but there didn't seem to be a reply.  Does anybody know what the problem is here?

From: Daniel Pauli <dapaulid at gmail dot com>
To: crossgcc at sourceware dot org
Date: Wed, 6 Mar 2013 19:47:25 +0100
Subject: crosstool-ng 1.18.0 fails to build i686-unknown-mingw32 for gcc 4.7.2
Hey there

I'm trying to build the i686-unknown-mingw32 sample for gcc 4.7.2 but
it fails at the following step:

[ALL  ]    The directory that should contain system headers does not exist:
[ALL  ]      /home/user/x-tools/i686-unknown-mingw32/i686-unknown-mingw32/sysroot/mingw/include
[ERROR]    make[2]: *** [stmp-fixinc] Error 1
[ALL  ]    rm gcc.pod
[ALL  ]    make[2]: Leaving directory
`/home/user/crosstool-ng-1.18.0/test/.build/i686-unknown-mingw32/build/build-cc-core-pass-1/gcc'
[ERROR]    make[1]: *** [all-gcc] Error 2
[ALL  ]    make[1]: Leaving directory
`/home/user/crosstool-ng-1.18.0/test/.build/i686-unknown-mingw32/build/build-cc-core-pass-1'
[ERROR]
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing pass-1 core C compiler'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR]  >>        called from: do_cc_core_backend[scripts/build/cc/gcc.sh@448]
[ERROR]  >>        called from: do_cc_core_pass_1[scripts/build/cc/gcc.sh@101]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@632]


--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2014-01-20 23:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 23:50 Drew Bliss [this message]
2014-01-21  0:18 ` Ray Donnelly
2014-01-21  0:18   ` Ray Donnelly
2014-01-21  0:32     ` Drew Bliss
2014-01-30 14:22       ` Soloff, Steven M          Belcan Engineering Group, Cincinnati, Ohio
2014-01-30 14:43         ` Ray Donnelly
2014-01-30 18:15           ` [External] " Soloff, Steven M          Belcan Engineering Group, Cincinnati, Ohio

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=081118858EAEC94C9E4EE628510B31CD13227D62@exchange10.valvesoftware.com \
    --to=drewb@valvesoftware.com \
    --cc=crossgcc@sourceware.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).