public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/104057] cross compiler multilibs libs path too chaos Date: Mon, 17 Jan 2022 01:40:44 +0000 [thread overview] Message-ID: <bug-104057-4-hQmhKhuGPt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104057-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104057 --- Comment #16 from Andrew Pinski <pinskia at gcc dot gnu.org> --- There are a definitely a few steps missing, Where is the Linux headers installed? How did you configure glibc and install it? I don't see you copying the headers of glibc anywhere. sysroots make it easier to place just the normal OS directory structure under ${prefix}/${target}/sys-root/ which is why it is the recommened way. If sys-root is broken for mingw we should fix that instead.
next prev parent reply other threads:[~2022-01-17 1:40 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-16 23:27 [Bug bootstrap/104057] New: " unlvsur at live dot com 2022-01-16 23:37 ` [Bug bootstrap/104057] " pinskia at gcc dot gnu.org 2022-01-17 1:02 ` unlvsur at live dot com 2022-01-17 1:03 ` unlvsur at live dot com 2022-01-17 1:14 ` pinskia at gcc dot gnu.org 2022-01-17 1:15 ` unlvsur at live dot com 2022-01-17 1:18 ` pinskia at gcc dot gnu.org 2022-01-17 1:19 ` unlvsur at live dot com 2022-01-17 1:20 ` unlvsur at live dot com 2022-01-17 1:20 ` pinskia at gcc dot gnu.org 2022-01-17 1:22 ` pinskia at gcc dot gnu.org 2022-01-17 1:24 ` unlvsur at live dot com 2022-01-17 1:28 ` pinskia at gcc dot gnu.org 2022-01-17 1:34 ` unlvsur at live dot com 2022-01-17 1:35 ` unlvsur at live dot com 2022-01-17 1:40 ` unlvsur at live dot com 2022-01-17 1:40 ` pinskia at gcc dot gnu.org [this message] 2022-01-17 1:41 ` pinskia at gcc dot gnu.org 2022-01-17 1:43 ` unlvsur at live dot com 2022-01-17 1:45 ` unlvsur at live dot com 2022-01-17 1:45 ` unlvsur at live dot com 2022-01-17 1:46 ` unlvsur at live dot com
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-104057-4-hQmhKhuGPt@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: linkBe 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).