From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Python3
Date: Sat, 28 Jan 2017 18:48:48 +0100 [thread overview]
Message-ID: <79370944-ee1a-5886-0b9f-bce8c4e42747@ipfire.org> (raw)
In-Reply-To: <598bd5cf-edf5-f382-ccf0-8ee02de5a87b@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2854 bytes --]
Hi,
Ok, got it:
"x86_64 refers to 64-bit processors. i386 refers to 32-bit processors."
Replaced all "x86_64" in ".../config/rootfiles/packages/i586/python3"
with "i386" and this seemed to work.
Sent rootfile...
Best,
Matthias
On 28.01.2017 09:33, Matthias Fischer wrote:
> Hi,
>
> sorry guys, but this won't build here:
>
> Its always (_build.packages.log):
>
> ...
> Jan 28 00:04:45: Building python3 Python-3.6.0.tar.xz checksum OK
> + cd /usr/src/lfs
> + make -f python3 LFS_BASEDIR=/usr/src dist
> '/usr/src/config/rootfiles/packages/i586/python3' ->
> '/install/packages/package/ROOTFILES'
> tar:
> usr/lib/python3.6/__pycache__/_sysconfigdata_m_linux_x86_64-linux-gnu.cpython-36.opt-1.pyc:
> Cannot stat: No such file or directory
> tar:
> usr/lib/python3.6/__pycache__/_sysconfigdata_m_linux_x86_64-linux-gnu.cpython-36.opt-2.pyc:
> Cannot stat: No such file or directory
> tar:
> usr/lib/python3.6/__pycache__/_sysconfigdata_m_linux_x86_64-linux-gnu.cpython-36.pyc:
> Cannot stat: No such file or directory
> tar: usr/lib/python3.6/_sysconfigdata_m_linux_x86_64-linux-gnu.py:
> Cannot stat: No such file or directory
> ... and so on ...
>
> E.g., script is searching for:
>
> _sysconfigdata_m_linux_x86_64-linux-gnu.cpython-36.opt-1.pyc
> ^^^^^^
> It builds:
>
> _sysconfigdata_m_linux_i386-linux-gnu.cpython-36.opt-1.pyc
> ^^^^
> "Fixes for rootfile" (or something similar?) needed!?
>
> Best,
> Matthias
>
> On 27.01.2017 13:33, Michael Tremer wrote:
>> Hi,
>>
>> thank you for submitting this.
>>
>> I merged this and for me, the flash image couldn't be generated either. The
>> reason for that is that we allocate a partition of a fixed size (which is
>> ~700MB) right now. The system is extracted onto that partition and all is put
>> into the image which then is small enough to fit on a 1GB storage device. As
>> soon as the system boots up for the first time, it increases the partition to
>> maximum size.
>>
>> However, with adding Python 3 to the core system, it didn't fit into the 700MB
>> any more. I therefore made it an add-on package which is still rather huge
>> (~20MB). Is there any requirement this should be in the core distribution? AFAIK
>> nothing is using this by default, hence it could easily be an add-on.
>>
>> Best,
>> -Michael
>>
>> On Mon, 2017-01-23 at 16:17 +0100, Jonatan Schlag wrote:
>>> Hi,
>>> the following patches include python3 in ipfire.
>>>
>>> Unfortunately, the flash image build no more. The build fails with a
>>> tar
>>> error complaining about to less disk space. I did not found out what the
>>> problem is, so somebody else has to investigate time into this problem
>>> to find a solution.
>>>
>>> Regards Jonatan
>>>
>>
>
>
next prev parent reply other threads:[~2017-01-28 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 15:17 Python3 Jonatan Schlag
2017-01-23 15:17 ` [PATCH 1/2] Prepare for python3 Jonatan Schlag
2017-01-27 12:33 ` Python3 Michael Tremer
2017-01-28 8:33 ` Python3 Matthias Fischer
2017-01-28 17:48 ` Matthias Fischer [this message]
2017-01-29 19:24 ` Python3 Michael Tremer
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=79370944-ee1a-5886-0b9f-bce8c4e42747@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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