Arch Linux User Repository

latest makes pamac-aur stuck forever, something is off, not sure what that is!

It updates fine with "aur" though: https://raw.githubusercontent.com/WebReflection/archibold.io/refs/heads/master/utils/aur

Currently this package breaks when using the mold linker:

LINK build/mpy-cross
mold: fatal: unknown command line option: --cref
collect2: error: ld returned 1 exit status
make: *** [../py/mkrules.mk:244: build/mpy-cross] 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

I modified the PKGBUILD with this, which forces ld.bfd and strips the -fuse-ld=mold flags.
It’s a bit hacky, but should fix builds for people who use mold globally:

export LD=/usr/bin/ld.bfd
export CFLAGS="${CFLAGS/-fuse-ld=mold/}"
export CXXFLAGS="${CXXFLAGS/-fuse-ld=mold/}"
export LDFLAGS="${LDFLAGS/-fuse-ld=mold/}"
export RUSTFLAGS="${RUSTFLAGS//-C link-arg=-fuse-ld=mold/}"

Currently fails to build because upstream uses -Werror by default and GCC 15 introduced a new warning.

Workaround:

CFLAGS="$CFLAGS -Wno-error=unterminated-string-initialization"

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)