From: <roman@kolesnikov.mobi>
To: "Grant Edwards" <grant.b.edwards@gmail.com>, crossgcc@sourceware.org
Subject: RE: 32-bit host vs 64-bit host
Date: Tue, 25 Feb 2014 20:48:00 -0000 [thread overview]
Message-ID: <20140225134757.f955220426e7925665b5897d8ef6e12e.7871ca77e8.wbe@email02.secureserver.net> (raw)
Grant,
>What sort of differences did you find?
I could not compile the standard c library with the 32 bit toolchain on
a 64 bit host, when the same library would build fine on the 32 bit
host. I have ran into this issue many times during the second stage of
the toolchain build on a 64 bit host. Same gcc/glibc sources would
compile on a 32 bit host but would fail on a 64 bit.
R
-------- Original Message --------
Subject: Re: 32-bit host vs 64-bit host
From: Grant Edwards <grant.b.edwards@gmail.com>
Date: Tue, February 25, 2014 1:31 pm
To: crossgcc@sourceware.org
On 2014-02-25, <roman@kolesnikov.mobi> <roman@kolesnikov.mobi> wrote:
> I found the difference in building the libraries and file systems.
What sort of differences did you find?
> Making 32 bit chroot on 64 bit system was an extra nuisance.
You don't need to do that to run an existing 32-bit-host toolchain,
but you might need to do that to build a 32-bit-host toolchain on a
64-bit.
--
Grant Edwards grant.b.edwards Yow! My haircut is totally
at traditional!
gmail.com
--
For unsubscribe information see http://sourceware.org/lists.html#faq
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2014-02-25 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 20:48 roman [this message]
2014-02-25 21:00 ` Grant Edwards
-- strict thread matches above, loose matches on Subject: below --
2014-02-25 19:59 roman
2014-02-25 20:32 ` Grant Edwards
2014-02-24 21:27 Grant Edwards
2014-02-25 2:59 ` Ralf Corsepius
2014-03-02 2:00 ` Bill Pringlemeir
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=20140225134757.f955220426e7925665b5897d8ef6e12e.7871ca77e8.wbe@email02.secureserver.net \
--to=roman@kolesnikov.mobi \
--cc=crossgcc@sourceware.org \
--cc=grant.b.edwards@gmail.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).