From: Nick Clifton <nickc@redhat.com>
To: Keith Emery <k.emery.nbn@internode.on.net>, binutils@sourceware.org
Subject: Re: x86_64-lfs-linux-gnu
Date: Fri, 24 Mar 2023 10:57:21 +0000 [thread overview]
Message-ID: <052e0a20-52cd-f59e-d712-e424fa3cf1e1@redhat.com> (raw)
In-Reply-To: <ef9eb699-4676-0e78-8663-7801b0dfe5c6@internode.on.net>
Hi Keith,
> Can anybody shed some light on why binutils is creating a separate folder hierarchy under a folder "x86_64-lfs-linux-gnu"?
I think that we need to know more about what you are doing.
Can you show us exactly the steps that you are taking when you encounter this issue ?
> The best information I could find was that these are the files that relate to 64bit architectures. But if I'm not building a multi-arch system, shouldn't everything be
> compiled for x86-64bit? I've looked around and tried to find a switch to tell binutils to only build for 64bit. But I cant seem to find anything. Can anybody point me in
> the right direction?
Generally speaking, if a particular target supports both 32-bit and 64-bit
implementations then the binutils will automatically build support for both.
Normally however this should not be an issue. If you only use the 64-bit
features of an architecture then the support for the 32-bit version will
just be ignored.
Cheers
Nick
prev parent reply other threads:[~2023-03-24 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 6:17 x86_64-lfs-linux-gnu Keith Emery
2023-03-24 10:57 ` Nick Clifton [this message]
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=052e0a20-52cd-f59e-d712-e424fa3cf1e1@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=k.emery.nbn@internode.on.net \
/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).