From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: David Howells <dhowells@redhat.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
monstr@monstr.eu, ralf@linux-mips.org, liqin.linux@gmail.com,
lennox.wu@gmail.com, ysato@users.sourceforge.jp, dalias@libc.org,
davem@davemloft.net, linux-mips@linux-mips.org,
linux-sh@vger.kernel.org, sparclinux@vger.kernel.org,
geert@linux-m68k.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: Unify the various copies of libgcc into lib
Date: Wed, 24 May 2017 13:59:50 +0000 [thread overview]
Message-ID: <20170524135950.GB4230@physik.fu-berlin.de> (raw)
In-Reply-To: <23396.1495633764@warthog.procyon.org.uk>
On Wed, May 24, 2017 at 02:49:24PM +0100, David Howells wrote:
> Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> > ... Unfortunately I don't actually have all these cross compilers setup...
>
> If you have Fedora, you have the following available as standard
> RPMs:
And if you need more than just the cross-compilers (e.g. libraries for
the target architecture), I recommend a Debian Stretch or newer.
Debian's Multi-Arch allows one to install libraries for the target
system onto your build system. I have used that extensively in the
past, for example to bootstrap GHC for various architectures [1].
Adrian
> [1] https://wiki.debian.org/PortsDocs/BootstrappingGHC
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2017-05-24 13:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 22:05 Unify the various copies of libgcc into lib Palmer Dabbelt
2017-05-23 22:05 ` [PATCH 1/7] lib: Add shared copies of some GCC library routines Palmer Dabbelt
2017-05-24 8:52 ` Matt Redfearn
2017-06-03 2:18 ` Palmer Dabbelt
2017-05-23 22:05 ` [PATCH 2/7] m32r: Use lib/ucmpdi2.c Palmer Dabbelt
2017-05-23 22:05 ` [PATCH 3/7] microblaze: Use libgcc files from lib/ Palmer Dabbelt
2017-05-24 11:22 ` kbuild test robot
2017-05-23 22:05 ` [PATCH 4/7] mips: Use lib/{ashldi3,ashrdi3,cmpdi2,lshrdi3,ucmpdi2}.c Palmer Dabbelt
2017-05-24 9:01 ` Matt Redfearn
2017-06-03 2:18 ` Palmer Dabbelt
2017-05-24 11:39 ` kbuild test robot
2017-05-24 11:50 ` kbuild test robot
2017-05-23 22:05 ` [PATCH 5/7] score: " Palmer Dabbelt
2017-05-23 22:05 ` [PATCH 6/7] sh: Use lib/ashldi3,ashrdi3,lshrdi3}.c Palmer Dabbelt
2017-05-24 11:22 ` kbuild test robot
2017-05-24 11:30 ` kbuild test robot
2017-05-23 22:05 ` [PATCH 7/7] sparc: Use lib/{cmpdi2,ucmpdi2}.c Palmer Dabbelt
2017-05-24 9:21 ` Unify the various copies of libgcc into lib Geert Uytterhoeven
2017-06-03 2:59 ` Palmer Dabbelt
2017-05-24 13:49 ` David Howells
2017-05-24 13:59 ` John Paul Adrian Glaubitz [this message]
2017-06-06 19:10 ` Unify the various copies of libgcc into lib v2 Palmer Dabbelt
2017-06-06 19:10 ` [PATCH 1/7] lib: Add shared copies of some GCC library routines Palmer Dabbelt
2017-06-06 19:10 ` [PATCH 2/7] m32r: Use lib/ucmpdi2.c Palmer Dabbelt
2017-06-06 19:10 ` [PATCH 3/7] microblaze: Use libgcc files from lib/ Palmer Dabbelt
2017-06-06 19:10 ` [PATCH 4/7] score: Use lib/{ashldi3,ashrdi3,cmpdi2,lshrdi3,ucmpdi2}.c Palmer Dabbelt
2017-06-06 19:10 ` [PATCH 5/7] sh: Use lib/ashldi3,ashrdi3,lshrdi3}.c Palmer Dabbelt
2017-06-07 19:27 ` kbuild test robot
2017-06-06 19:10 ` [PATCH 6/7] sparc: Use lib/{cmpdi2,ucmpdi2}.c Palmer Dabbelt
2017-06-06 19:10 ` [PATCH 7/7] MIPS: Use generic libgcc intrinsics Palmer Dabbelt
2017-06-09 19:53 ` Ralf Baechle
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=20170524135950.GB4230@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=lennox.wu@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-sh@vger.kernel.org \
--cc=liqin.linux@gmail.com \
--cc=monstr@monstr.eu \
--cc=palmer@dabbelt.com \
--cc=ralf@linux-mips.org \
--cc=sparclinux@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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 NNTP newsgroup(s).