From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: Matthias Klose <doko@ubuntu.com>, Binutils <binutils@sourceware.org>
Subject: Re: how should I configure my buuild for i386-*linux*
Date: Wed, 4 May 2022 00:29:32 -0700 [thread overview]
Message-ID: <2a2f06b6-5a0c-4cdc-b4ef-2fcd21e3d9f6@oracle.com> (raw)
In-Reply-To: <f8472aa2-e8a4-9569-da7c-5cb06e2731e7@ubuntu.com>
On 5/3/22 16:42, Matthias Klose wrote:
> On 04.05.22 01:31, Vladimir Mezentsev via Binutils wrote:
>> Hi,
>>
>> If I am on x86_64-*-linux* and want to build the i386-*linux*
>> libraries (for example, libopcodes or libbfd),
>> how should I configure my buuild ?
>>
>> The same question is for the aarch64-*-linux* host.
>
> you could have a look at the Debian build logs, e.g. look for the
> amd64 build log which also builds the binutils for i686 and aarch64
> hosted on x86_64:
>
> https://buildd.debian.org/status/package.php?p=binutils
> (click on the "Installed" cell for the amd64 build log, then search
> for --target=i686-linux-gnu and --target=aarch64-linux-gnu
I can reproduce a problem in the gprofng build.
But after this configuration:
mkdir builddir-i386
cd builddir-i386 \
&& env CC="x86_64-linux-gnu-gcc" CXX="x86_64-linux-gnu-g++" \
DEB_TARGET_MULTIARCH=i386-linux-gnu DEB_TARGET_MULTIARCH64=x86_64-linux-gnu DEB_TARGET_MULTIARCHX32=x86_64-linux-gnux32 \
../configure \
--disable-silent-rules --enable-obsolete --enable-shared --enable-plugins --enable-threads --with-system-zlib --prefix=/usr --enable-deterministic-archives --disable-compressed-debug-sections --enable-new-dtags --disable-x86-used-note --with-gold-ldflags=-static-libstdc++ --build=x86_64-linux-gnu --host=x86_64-linux-gnu --with-pkgversion="GNU Binutils for Debian" --disable-werror --enable-initfini-array --enable-ld=default --enable-gold \
--enable-targets=x86_64-linux-gnu,x86_64-linux-gnux32,x86_64-pep \
--with-sysroot=/ \
--libdir=/usr/lib/i386-linux-gnu \
--enable-ld=default --enable-gold \
--target=i686-linux-gnu
All binaries are the 64-bit binaries.
-m32 is not passed to gcc.
Is it expected ?
Thank you,
-Vladimir
>
>> Is it possible to build on Arm for Intel platform ?
>
> I am only building on aarch64, same as above, click the arm64 build
> log and search for --target=x86_64-linux-gnu.
>
> Matthias
next prev parent reply other threads:[~2022-05-04 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 23:31 Vladimir Mezentsev
2022-05-03 23:42 ` Matthias Klose
2022-05-04 7:29 ` Vladimir Mezentsev [this message]
2022-05-07 13:30 ` Nick Alcock
2022-05-07 14:21 ` Andreas Schwab
2022-05-09 12:01 ` Nick Alcock
2022-05-09 12:13 ` Christian Groessler
2022-05-17 12:33 ` Nick Alcock
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=2a2f06b6-5a0c-4cdc-b4ef-2fcd21e3d9f6@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=binutils@sourceware.org \
--cc=doko@ubuntu.com \
/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).