From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] python 2 or 3
Date: Thu, 29 May 2014 17:03:14 +0000 (UTC) [thread overview]
Message-ID: <lm7p8h$gel$1@ger.gmane.org> (raw)
In-Reply-To: 20140529081348.e67be25036aefa1f48864236@lavabit.com
On 2014-05-29, rh_ <richard_hubbe11@lavabit.com> wrote:
> On Thu, 29 May 2014 09:23:59 +0200 Peter Korsgaard <jacmet@uclibc.org> wrote:
>
>> I haven't investigated it yet. Do you really want to build a
>> statically linked python?
>
> FWIW, I think I saw that link before I posted. I did intend to build
> a statically linked python
We know. The question is why do you want to build a _statically_
linked python? (As opposed to a dynamically linked one.)
> but have given up for now.
>
> I built a statically linked perl instead. I needed something that
> didn't end with "sh" to write programs. I've been doing more python
> than perl but perl will be fine.
But why does it need to be statically linked?
--
Grant Edwards grant.b.edwards Yow! I didn't order any
at WOO-WOO ... Maybe a YUBBA
gmail.com ... But no WOO-WOO!
prev parent reply other threads:[~2014-05-29 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140528194852.fe13e0e104246a21d4742916@lavabit.com>
2014-05-29 3:25 ` [Buildroot] python 2 or 3 Baruch Siach
2014-05-29 7:23 ` Peter Korsgaard
[not found] ` <20140529081348.e67be25036aefa1f48864236@lavabit.com>
2014-05-29 17:03 ` Grant Edwards [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='lm7p8h$gel$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.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