From: evanation <evanation.ru@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Cross GCC (MULTILIB_OSDIRNAMES m32)
Date: Tue, 20 Oct 2020 17:36:06 +1100 [thread overview]
Message-ID: <CADROohMO-bO1vYYk1RT-iLfBprD492YhnZEDb00sYEetsTmpsA@mail.gmail.com> (raw)
If build gcc with the --with-build-sysroot=$sysroot_dir parameter, then the
built gcc -m32 will look for libraries in $sysroot_dir/lib32 and
$sysroot_dir/usr/lib32, if there are such directories there. But if build
with the --without-headers parameter and without --with-build-sysroot then
how to make the assembled gcc -m32 look in $sysroot_dir/lib32? Only edit
gcc/config/i386/t-linux64 file?
My building parametres:
configure \
--build=$(../"$srcdir"/config.guess) \
--host=$(../"$srcdir"/config.guess) \
--target=$_target \
--prefix=$_prefix \
--with-sysroot=$_sysroot \
--with-newlib \
--disable-nls \
--enable-multilib \
--with-multilib-list=m64,m32,mx32 \
--disable-shared \
--disable-threads \
--enable-languages=c,c++
P.S. Sorry for my English
next reply other threads:[~2020-10-20 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 6:36 evanation [this message]
2020-10-20 7:51 ` evanation
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=CADROohMO-bO1vYYk1RT-iLfBprD492YhnZEDb00sYEetsTmpsA@mail.gmail.com \
--to=evanation.ru@gmail.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).