From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=fail reason="body hash did not verify" header.i=@riseup.net header.s=squak header.b=h/DqKn7R; spf=pass (domain: riseup.net, ip: 198.252.153.129, mailfrom: phlamorim@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) by groups.io with SMTP; Tue, 30 Apr 2019 13:47:27 -0700 Received: from capuchin.riseup.net (capuchin-pn.riseup.net [10.0.1.176]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 7F76C1A2F1F; Tue, 30 Apr 2019 13:47:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1556657246; bh=+Hpe7CwpWPExkr75EZP069pRA4eupfRXTH+ug3BS9c8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=h/DqKn7RHE6encR+oOondzVeDDjLchErs2NgWBiDANZnQ3fYChbG+Ps4Ag39LVjNW lR/CF4pNOC0pTTPI+m1dljUrOw3+8lB07xj5QRsZWW2stJdISrYg7sMtHR0OkQfW7z WV49Bl8IzQjO4Aj9daTQJIwKCTYckGA6afHvTFxU= X-Riseup-User-ID: F39648EA5683A2515A65AC9CF9F623EE83EC85E0983B3075330D4FF4F6F70842 Received: from [127.0.0.1] (localhost [127.0.0.1]) by capuchin.riseup.net (Postfix) with ESMTPSA id 50C97120BCE; Tue, 30 Apr 2019 13:47:26 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 30 Apr 2019 13:47:25 -0700 From: phlamorim@riseup.net To: devel@edk2.groups.io, jaben.carsey@intel.com Cc: Leif Lindholm , Daryl McDaniel , Brian Richardson Subject: Re: [edk2-devel] Error building Python In-Reply-To: References: <11299.1556511928716793059@groups.io> <20190429165414.cs2xlp7zpzqej7en@bivouac.eciton.net> Message-ID: <7a4832ab4467b3f67fdb786d45bc37af@riseup.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Im sending the feeback through this thread only, regards we have another at https://edk2.groups.io/g/devel/message/39787 i believe we should keep just this one, i read about MicroPython and the first thing i noticed is GCC toolchain is not listed on support toolchain at the moment, but i tried to compile anyway with the following command: # build -p MicroPythonPkg/MicroPythonPkg.dsc -a X64 -t GCC5 The build finished with success, then i moved 'MicroPythonDxe.efi' and 'micropython.efi' to a fat partition to make a test using OVMF and QEMU, the Python interpreter initialized with success too, and i just tested basic operations like assign and basic arithmetics. The first problem appears when i tried to use import, like in the example of README, i tried to load 'VirtualConsoleDxe.efi' manually and then execute 'micropython.efi' the VirtualConsoleDxe is loaded and interpreter initialized too, but when i tried to do a "import Lib.Uefi.uefi as uefi" the interpreter hangs and the virtual machine rebooted. The sockets module is not supported at the moment on MicroPython as said on README, the application i want to make a prototype relies on network, so i probably should build the StdLib package and try to make a prototype with C, but its worth to notice the MicroPython is finishing the build in current state, i want to know if sockets module will be possible provided in a future release. Thanks, Paulo Amorim=20 On 2019-04-30 13:36, Carsey, Jaben wrote: > Paulo, >=20 > I would urge you to use the minpython instead of the AppPkg python.=20 > The minpython is a python 3 implementation vs. this 2.7 > implementation. New development should not start on a version of > python that is about to go officially EOL. >=20 > That being said, I have not seed that error message before. Maybe > Daryl has a better starting point. >=20 > -Jaben >=20 >> -----Original Message----- >> From: Leif Lindholm [mailto:leif.lindholm@linaro.org] >> Sent: Monday, April 29, 2019 9:54 AM >> To: devel@edk2.groups.io; phlamorim@riseup.net >> Cc: Daryl McDaniel ; Carsey, Jaben >> >> Subject: Re: [edk2-devel] Error building Python >> Importance: High >> >> +AppPkg maintainers >> >> On Sun, Apr 28, 2019 at 09:25:28PM -0700, phlamorim@riseup.net wrote: >> > I want to use python to prototype some UEFI applications, but the bui= ld >> > is not working on my environment, im trying to build in a linux(debia= n) >> > which have "gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516" installed, t= he >> > EDK2 is properly installed, i build other packages like OVMF and Mde*= , >> > at the first time i tried to build Python just uncommenting >> > "AppPkg/Applications/Python/PythonCore.inf" the build stopped because >> > some compiler warnings which are stopping the building bcause the fla= g >> > -Werror, so i changed the file tools_def.txt to remove the -Werror fl= ag, >> > the warnings dont stopped the build, i probably should fix the warnin= gs >> > one by one, but when i tried to build again the build system stopped = at >> > target >> > >> '/root/projeto_final/src/edk2/Build/AppPkg/DEBUG_GCC5/X64/AppPkg/Ap >> plications/Python/PythonCore/DEBUG/Python.dll', >> > i will leave the entire error message following this message, let me >> > know if i need to provide another/more information. >> > >> > -- >> > pymath.obj (symbol from plugin): In function `_Py_get_387controlword'= : >> > (.text+0x0): multiple definition of `copysign' >> > s_copysign.obj (symbol from plugin):(.text+0x0): first defined here >> > collect2: error: ld returned 1 exit status >> > GNUmakefile:583: recipe for target >> > >> '/root/projeto_final/src/edk2/Build/AppPkg/DEBUG_GCC5/X64/AppPkg/Ap >> plications/Python/PythonCore/DEBUG/Python.dll' >> > failed >> > make: *** >> > >> [/root/projeto_final/src/edk2/Build/AppPkg/DEBUG_GCC5/X64/AppPkg/Ap >> plications/Python/PythonCore/DEBUG/Python.dll] >> > Error 1 >> > >> > build.py... >> > =C2=A0: error 7000: Failed to execute command >> > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0make tbuild >> > >> [/root/projeto_final/src/edk2/Build/AppPkg/DEBUG_GCC5/X64/AppPkg/Ap >> plications/Python/PythonCore] >> > >> > build.py... >> > =C2=A0: error F002: Failed to build module >> > >> > /root/projeto_final/src/edk2/AppPkg/Applications/Python/PythonCore.in= f >> > [X64, GCC5, DEBUG] >> > >> > - Failed - >> > Build end time: 06:56:21, Apr.28 2019 >> > Build total time: 00:05:32 >> > -- >> > >> > Thanks, >> > Paulo Amorim >> > >> > >> > >=20 >=20