From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14321] scanpypi doesn't work with the pyinstaller module
Date: Thu, 04 Nov 2021 17:09:21 +0000 [thread overview]
Message-ID: <bug-14321-163-6TgnSFcflD@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14321-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14321
--- Comment #2 from Kevin <kr886q@att.com> ---
I started down this rabbit hole when trying to create a executable(written in
python) to run on a target device (aarch64) with uclibc (basic busybox). I was
able to virtualize the target arch with docker/buildx but could not find a
suitable image that had uclibc, gcc, python, and other needed things to cross
compile.
I then tried to use buildroot (running in ubuntu container) to create an image
and run in docker but ran into some trouble and decided to pivot.
I discovered that the Rpi3 has the same chip (cortex A53) as my target device.
So I used buildroot to create an image and flash it to the Rpi3. Now I have the
correct toolchain and everything I need EXCEPT pyinstaller, to cross compile.
Due to certain restrictions I am unable to cross compile on the target device.
also this is my first experience going deeper into linux than just the basic
terminal commands, so my apologies.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-04 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 14:33 [Buildroot] [Bug 14321] New: Error: Could not install package {PACKAGE}: 'name' bugzilla
2021-11-04 15:38 ` [Buildroot] [Bug 14321] " bugzilla
2021-11-04 15:38 ` [Buildroot] [Bug 14321] scanpypi doesn't work with the pyinstaller module bugzilla
2021-11-04 17:09 ` bugzilla [this message]
2021-11-04 17:36 ` bugzilla
2021-11-05 15:19 ` bugzilla
2021-11-05 23:24 ` bugzilla
2021-11-06 11:04 ` bugzilla
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=bug-14321-163-6TgnSFcflD@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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