From: John Gilmore <gnu@toad.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Doug Evans <dje@google.com>,
Meador Inge <meadori@codesourcery.com>,
gdb@sourceware.org
Subject: Re: Using Py_SetPythonHome
Date: Thu, 04 Oct 2012 07:33:00 -0000 [thread overview]
Message-ID: <201210040732.q947Wok7025038@new.toad.com> (raw)
In-Reply-To: <20121003175343.GA14317@host2.jankratochvil.net>
Package management is a sinkhole, unfortunately. The OLPC project has
unfortunately discovered that despite the great support in the GNU
tools for cross-compilation, the Fedora package management tools are
completely incapable of cross-compilation. So now that they are
making hardware with three architectures to build software for (i386,
i686, and ARM), they need to dedicate three kinds of hardware to
building their Fedora-based releases. They can't make an OS image on
a fast x86 machine that will install or boot on an ARM.(*)
(I think Debian/Ubuntu package managers suffer from the same problem;
they all assume they're running "native", they run package-specific
shell scripts that think they're running in the target environment,
etc.)
I recommend NOT assuming that package managers are the cat's pajamas
and that therefore we can all skip the ability to usefully build from
source.
Having seen this Py_SetPythonHome discussion drag on for what seems
months (I think it's the most frequent subject line in the mailing
list), and yet I still don't understand why y'all care, perhaps someone
should try to write up a solid proposal that explains what the hell is
going on, with pros and cons listed and generally agreed upon. That
might help point a path to making a decision that sticks for a while.
John
(*): They can run builds under QEMU on x86, emulating the ARM
instruction set, using a set of native ARM compilers and a full ARM
GNU/Linux virtual machine, and make the ARM builds that way. Indeed they
do -- it's only a 2- to 3-times slowdown, which is far easier than
rewriting the package management subsystem for cross-compilation and
then getting the changes adopted "upstream" into Fedora. And far, far
easier than building fast hardware based on an available ARM chip.
next prev parent reply other threads:[~2012-10-04 7:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 23:23 Meador Inge
2012-09-17 17:07 ` Joel Brobecker
2012-09-17 17:46 ` Jan Kratochvil
2012-09-18 19:38 ` Doug Evans
2012-09-19 8:04 ` Jan Kratochvil
2012-09-21 15:37 ` Joel Brobecker
2012-09-21 15:44 ` Jan Kratochvil
2012-09-21 15:58 ` Joel Brobecker
2012-09-21 17:28 ` Jan Kratochvil
2012-10-02 13:09 ` Joel Brobecker
2012-10-03 15:13 ` Jan Kratochvil
2012-10-03 15:14 ` Jan Kratochvil
2012-10-03 15:39 ` Joel Brobecker
2012-10-03 17:44 ` Eli Zaretskii
2012-10-03 17:54 ` Jan Kratochvil
2012-10-03 17:57 ` Paul_Koning
2012-10-03 18:35 ` Eli Zaretskii
2012-10-03 18:43 ` Jan Kratochvil
2012-10-03 18:52 ` Eli Zaretskii
2012-10-03 19:03 ` Jan Kratochvil
2012-10-03 19:10 ` Eli Zaretskii
2012-10-03 19:54 ` Paul_Koning
2012-10-03 20:04 ` Jan Kratochvil
2012-10-03 20:11 ` Alfred M. Szmidt
2012-10-03 18:40 ` Eli Zaretskii
2012-10-03 19:26 ` Terekhov, Mikhail
2012-10-04 7:33 ` John Gilmore [this message]
2012-10-11 8:42 ` Jan Kratochvil
2012-10-11 14:54 ` Doug Evans
2012-09-21 15:55 ` Meador Inge
2012-09-21 16:01 ` Jan Kratochvil
2012-09-21 16:36 ` Doug Evans
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=201210040732.q947Wok7025038@new.toad.com \
--to=gnu@toad.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=meadori@codesourcery.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).