Arch Linux User Repository

I've tried building locally and I'm facing some issues building the package.

Thanks for considering my work.

python-build might be needed within makedepends

What do we need it for?

I wasn't able to build the pletora of different packages that you've added

Me neither. I mean, some firmware are not so straightforward. At some point, I gave up and thought that either someone could help or that firmware is of little interest (for the Arch users, at least).

I hope it's clear why I added all those packages. To recap:

1. those are the output of the project
2. I'd be happy as an Arch user and micropython developer to find the firmware of my developing board and start immediately coding.
3. If the makepkg will ever be part of some official archive, we can uncomment all firmwares.

If we can possibly move the repo to Github?

I own a Gitbub account, too. See aur-micropython.

I'd be happy to support more boards from this package.

Thanks a lot. Let's go on in Github, then.

Hey @lorcap, I've tried building locally and I'm facing some issues building the package.

Some issues I faced,

• python-build might be needed within makedepends,
• I wasn't able to build the pletora of different packages that you've added

It would be good if I could open issues on the repo that you've shared, I'm not sure why bitbucket doesn't allow me to do that :-( If we can possibly move the repo to Github? I'd be happy to support more boards from this package.

A friendly ping from my request below.

Hi there, I saw this package was orphaned and I started working on it. I came up with an enhanced version which provides: micropython, mpremote, mpy-cross and (many, not all) board firmware images. Are you willing to accept my changes? You can have a look at https://bitbucket.org/lorcap/aur-micropython/. Thanks.

@jimmo - Thanks for the pointers they seem genuinely helpful and I'll try to incorporate these. Seperating mlib and micropython, that I would need to test the changes once before I push these changes out.

@kseistrup - This seems intentional, however I'm not sure why this was put in place as this is something that was put in 5 years ago by Kyle.

For the time being I'm keeping the PKGBUILD as is and updating to 1.22.0, sometime in the next few weeks I'll push out another release with a newer PKGBUILD, I don't seem to have enough time to test everything due to high load at work.

This package (micropython-lib 1.21.0-1), when built, seems to contain only the LICENSE and nothing else. Is that intentional?

I do see some error during build, but that doesn't seem to deter makepkg from comtinuing:

==> Starting package_micropython-lib()...
==> ERROR: Skipping ./.github (no setup)
==> ERROR: Skipping ./micropython (no setup)
==> ERROR: Skipping ./python-ecosys (no setup)
==> ERROR: Skipping ./python-stdlib (no setup)
==> ERROR: Skipping ./tools (no setup)
==> ERROR: Skipping ./unix-ffi (no setup)

We're in the process of releasing MicroPython v1.21.0 today, the new tarball should be available shortly. Some suggestions for updating the PKGBUILD:

1. The -Wno-dangling-pointer is no longer required.
2. Rather than modifying Makefile to remove /local, it would make more sense to pass PREFIX=/usr on the make commandline.
3. I'm not sure what the second sed was for (with the git clean), as it doesn't match anything in the Makefile.
4. MICROPY_PY_USSL was renamed to MICROPY_PY_SSL in v1.21.0. I'm not sure why the PKGBUILD is disabling ssl but enabling mbedtls though. Also mbedtls is now the default, so I think all three lines can be removed.
5. I'm not sure what the issue with FFI is -- this works for me on Arch. But if you do want to disable it, this should be done by adding MICROPY_PY_FFI=0 to the make commandline instead. You also shouldn't need make deplibs because it's not using MICROPY_STANDALONE.
6. The tests should not be non-deterministic. We run them as part of CI against a bunch of variants of the unix port. They should be safe to run here.
7. As I mentioned in an earlier comment, I don't think micropython-lib should be part of this package. We added mip to the unix port by default, so the user can do micropython mip install <name> to install the packages they need. TBH I'm not even sure what's here would work at all.

Here's an updated PKGBUILD with the above changes: https://gist.github.com/jimmo/426d88ce30361aed3a540d9af08ecdb6

See https://github.com/micropython/micropython/issues/11464#issuecomment-1543042388 for the dangling pointer workaround, use make CFLAGS_EXTRA="-Wno-dangling-pointer".

CC ../py/stackctrl.c ../py/stackctrl.c: In function ‘mp_stack_ctrl_init’: ../py/stackctrl.c:32:32: error: storing the address of local variable ‘stack_dummy’ in ‘mp_state_ctx.thread.stack_top’ [-Werror=dangling-pointer=] 32 | MP_STATE_THREAD(stack_top) = (char *)&stack_dummy; ../py/stackctrl.c:31:18: note: ‘stack_dummy’ declared here 31 | volatile int stack_dummy; | ^~~~~~~~~~~ In file included from ../py/runtime.h:29, from ../py/stackctrl.c:27: ../py/mpstate.h:294:23: note: ‘mp_state_ctx’ declared here 294 | extern mp_state_ctx_t mp_state_ctx; | ^~~~~~~~~~~~ cc1: all warnings being treated as errors make: *** [../py/mkrules.mk:77: build/py/stackctrl.o] Error 1 ==> ERROR: A failure occurred in build(). Aborting... -> error making: micropython-exit status 4 -> Failed to install the following packages. Manual intervention is required: micropython - exit status 4 Does Not Build?

Doesn't build:

../py/stackctrl.c: In function ‘mp_stack_ctrl_init’:
../py/stackctrl.c:32:32: error: storing the address of local variable ‘stack_dummy’ in ‘mp_state_ctx.thread.stack_top’ [-Werror=dangling-pointer=]
   32 |     MP_STATE_THREAD(stack_top) = (char *)&stack_dummy;
../py/stackctrl.c:31:18: note: ‘stack_dummy’ declared here
   31 |     volatile int stack_dummy;
      |                  ^~~~~~~~~~~
In file included from ../py/runtime.h:29,
                 from ../py/stackctrl.c:27:
../py/mpstate.h:294:23: note: ‘mp_state_ctx’ declared here
  294 | extern mp_state_ctx_t mp_state_ctx;
      |                       ^~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [../py/mkrules.mk:77: build/py/stackctrl.o] Error 1
==> ERROR: A failure occurred in build().
    Aborting...