public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: LIU Hao <lh_mouse@126.com>
To: "bootmgr@163.com" <bootmgr@163.com>, gcc-help@gcc.gnu.org
Subject: Re: Failed to compile gcc cross toolchain.
Date: Mon, 2 Aug 2021 22:19:43 +0800	[thread overview]
Message-ID: <2a2ceca7-aa7e-efa6-73bd-48a791fae058@126.com> (raw)
In-Reply-To: <21dc227d.2029.17b04d5ecc4.Coremail.bootmgr@163.com>


[-- Attachment #1.1: Type: text/plain, Size: 1034 bytes --]

在 8/2/21 11:08 AM, bootmgr--- via Gcc-help 写道:
> I'm failed to compile libstdc++.
> Configured by ../gcc-11.2.0/configure --disable-multilib --disable-nls --enable-graphite --enable-languages=c,c++,lto  --enable-mingw-wildcard --enable-threads=mcf --enable-version-specific-runtime-libs --disable-libstdcxx-pch --enable-fully-dynamic-string --enable-large-address-aware --enable-vtable-verify --target=x86_64-w64-mingw32 --with-sysroot=/usr/local
> Build: x86_64-linux-gnu Target:x86_64-w64-mingw32 Host: x86_64-linux-gnu
> 
> 

While I do have a hunk for the source file in question [1], failure to find `<cstdlib>` is indeed 
something unusual. It is most likely that you didn't install c++ headers into the correct directory, 
so your (stage1 I guess) compiler failed to find them.


[1] 
https://github.com/lhmouse/MINGW-packages-dev/blob/ddafe5bc97e027627900b95a96eacbcabdc889d7/mingw-w64-gcc-git/9000-gcc-10-branch-Added-mcf-thread-model-support-from-mcfgthread.patch#L218


-- 
Best regards,
LIU Hao


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  parent reply	other threads:[~2021-08-02 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  3:08 bootmgr
2021-08-02  6:16 ` Jonathan Yong
2021-08-02 14:19 ` LIU Hao [this message]
2021-08-03  4:50   ` bootmgr

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=2a2ceca7-aa7e-efa6-73bd-48a791fae058@126.com \
    --to=lh_mouse@126.com \
    --cc=bootmgr@163.com \
    --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).