public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <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:34:38 +0000	[thread overview]
Message-ID: <bug-104057-4-GQLNqYrAML@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 #13 from cqwrteur <unlvsur at live dot com> ---
(In reply to Andrew Pinski from comment #12)
> I don't care about your youtube videos (they are not accessable due to not
> having 
> the steps written down). I need the steps written here in the bug report.

export TARGET=x86_64-ubuntu-linux-gnu
export PREFIX=$HOME/cross/$TARGET
export PATH=$PREFIX:$PATH

../../binutils-gdb/configure --disable-werror --disable-nls --target=$TARGET
--enable-gold --with-python3 --prefix=$PREFIX

../../gcc/configure --disable-nls --disable-werror --target=$TARGET
--prefix=$PREFIX --without-headers --with-newlib --disable-hosted-libstdcxx
--disable-shared --disable-threads --enable-languages=c,c++

Use this to build a x86_64-ubuntu-linux-gnu-gcc to build glibc
glibc 32,64,x32

copy glibc32/lib to $PREFIX/$TARGET/lib/32 and $PREFIX/$TARGET/lib32
copy glibc64/lib to $PREFIX/$TARGET/lib $PREFIX/$TARGET/lib64
copy glibcx32/lib to $PREFIX/$TARGET/lib/x32 $PREFIX/$TARGET/libx32

Then build gcc2.

../../gcc/configure --disable-nls --disable-werror --target=$TARGET
--prefix=$PREFIX --disable-libstdcxx-verbose --enable-languages=c,c++

then copy all files from lib32 to lib (since GCC cannot find 32bit libs in
lib32 for x86_64-linux-gnu)

Done

  parent reply	other threads:[~2022-01-17  1:34 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 [this message]
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
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-GQLNqYrAML@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).