From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: Python3 Date: Sat, 28 Jan 2017 18:48:48 +0100 Message-ID: <79370944-ee1a-5886-0b9f-bce8c4e42747@ipfire.org> In-Reply-To: <598bd5cf-edf5-f382-ccf0-8ee02de5a87b@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3333427303446185339==" List-Id: --===============3333427303446185339== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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, >=20 > sorry guys, but this won't build here: >=20 > Its always (_build.packages.log): >=20 > ... > Jan 28 00:04:45: Building python3 Python-3.6.0.tar.xz checksum OK > + cd /usr/src/lfs > + make -f python3 LFS_BASEDIR=3D/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.cpyth= on-36.opt-1.pyc: > Cannot stat: No such file or directory > tar: > usr/lib/python3.6/__pycache__/_sysconfigdata_m_linux_x86_64-linux-gnu.cpyth= on-36.opt-2.pyc: > Cannot stat: No such file or directory > tar: > usr/lib/python3.6/__pycache__/_sysconfigdata_m_linux_x86_64-linux-gnu.cpyth= on-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 ... >=20 > E.g., script is searching for: >=20 > _sysconfigdata_m_linux_x86_64-linux-gnu.cpython-36.opt-1.pyc > ^^^^^^ > It builds: >=20 > _sysconfigdata_m_linux_i386-linux-gnu.cpython-36.opt-1.pyc > ^^^^ > "Fixes for rootfile" (or something similar?) needed!? >=20 > Best, > Matthias >=20 > On 27.01.2017 13:33, Michael Tremer wrote: >> Hi, >>=20 >> thank you for submitting this. >>=20 >> 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. >>=20 >> However, with adding Python 3 to the core system, it didn't fit into the 7= 00MB >> 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. >>=20 >> Best, >> -Michael >>=20 >> On Mon, 2017-01-23 at 16:17 +0100, Jonatan Schlag wrote: >>> Hi, >>> the following patches include python3 in ipfire.=20 >>>=20 >>> Unfortunately, the flash image build no more. The build fails with a=20 >>> tar=20 >>> 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=20 >>> to find a solution. >>>=20 >>> Regards Jonatan >>>=20 >>=20 >=20 >=20 --===============3333427303446185339==--