public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: phlamorim@riseup.net
To: devel@edk2.groups.io, jaben.carsey@intel.com
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
	Daryl McDaniel <edk2-lists@mc2research.org>,
	Brian Richardson <brian.richardson@intel.com>
Subject: Re: [edk2-devel] Error building Python
Date: Tue, 30 Apr 2019 13:47:25 -0700	[thread overview]
Message-ID: <7a4832ab4467b3f67fdb786d45bc37af@riseup.net> (raw)
In-Reply-To: <CB6E33457884FA40993F35157061515CBCC0D629@FMSMSX103.amr.corp.intel.com>

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 

On 2019-04-30 13:36, Carsey, Jaben wrote:
> Paulo,
> 
> I would urge you to use the minpython instead of the AppPkg python. 
> 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.
> 
> That being said, I have not seed that error message before. Maybe
> Daryl has a better starting point.
> 
> -Jaben
> 
>> -----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 <edk2-lists@mc2research.org>; Carsey, Jaben
>> <jaben.carsey@intel.com>
>> 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 build
>> > is not working on my environment, im trying to build in a linux(debian)
>> > which have "gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516" installed, the
>> > 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 flag
>> > -Werror, so i changed the file tools_def.txt to remove the -Werror flag,
>> > the warnings dont stopped the build, i probably should fix the warnings
>> > 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...
>> >  : error 7000: Failed to execute command
>> >         make tbuild
>> >
>> [/root/projeto_final/src/edk2/Build/AppPkg/DEBUG_GCC5/X64/AppPkg/Ap
>> plications/Python/PythonCore]
>> >
>> > build.py...
>> >  : error F002: Failed to build module
>> >
>> > /root/projeto_final/src/edk2/AppPkg/Applications/Python/PythonCore.inf
>> > [X64, GCC5, DEBUG]
>> >
>> > - Failed -
>> > Build end time: 06:56:21, Apr.28 2019
>> > Build total time: 00:05:32
>> > --
>> >
>> > Thanks,
>> > Paulo Amorim
>> >
>> >
>> >
> 
> 

  reply	other threads:[~2019-04-30 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29  4:25 Error building Python phlamorim
2019-04-29 16:54 ` [edk2-devel] " Leif Lindholm
2019-04-30 16:36   ` Carsey, Jaben
2019-04-30 20:47     ` phlamorim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-28 14:08 phlamorim
2019-04-29 21:13 ` [edk2-devel] " Brian Richardson

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-list 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=7a4832ab4467b3f67fdb786d45bc37af@riseup.net \
    --to=devel@edk2.groups.io \
    /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