Package Details: proxmark3-iceman-git 4.17768.r201.gab0c46a-1

Git Clone URL: (read-only, click to copy)
Package Base: proxmark3-iceman-git
Description: RRG / Iceman repo - Proxmark3 RDV4.0 and other Proxmark3 platforms.
Upstream URL:
Keywords: iceman proxmark3 rdv4.0
Licenses: GPL-2.0-only
Conflicts: proxmark3, proxmark3-iceman
Provides: proxmark3, proxmark3-iceman
Replaces: proxmark3-iceman-git-generic, proxmark3-iceman-git-rdv4
Submitter: edward-p
Maintainer: taotieren
Last Packager: taotieren
Votes: 1
Popularity: 0.000000
First Submitted: 2019-08-28 06:29 (UTC)
Last Updated: 2024-01-23 18:08 (UTC)

Latest Comments

edward-p commented on 2020-06-13 00:24 (UTC)

Since arm-none-eabi-gcc updated to 10.x, there was a compile error with the firmware. I switched to gcc-arm-none-eabi-bin just for lower version of arm-none-eabi-gcc. It compiles now with arm-none-eabi-gcc and arm-none-eabi-newlib and I will switch back to arm-none-eabi-gcc and arm-none-eabi-newlib. Thanks for reminding!

HeroCC commented on 2020-06-12 21:18 (UTC)

Why use gcc-arm-none-eabi-bin instead of arm-none-eabi-gcc + arm-none-eabi-newlib? The official docs recommend the latter.

edward-p commented on 2020-03-13 05:41 (UTC)

@stiefel40k Okay,I'll fix.

stiefel40k commented on 2020-03-13 05:38 (UTC)

I'm pretty sure that was the problem. I got the following message:

==> Starting build()...
mkdir: cannot create directory ‘’: No such file or directory

However I have to say, with makepkg it worked for me as well. First I was trying to install it with yay, as it didn't work I changed stuff, and I built it with makepkg... Maybe I should contact the devs of yay.

edward-p commented on 2020-03-13 03:14 (UTC)

@stiefel40k I just built with makepkg, it builds. Are you sure it's about the exported variables? Since the upstream source is a git repository (in development), it may have problems when compiling. If you feel annoyed building this, why not consider using the binary provided by "archlinuxcn"? See .

Status can be found here:

The upstream also have a CI for building and testing. See

stiefel40k commented on 2020-03-12 18:55 (UTC)

The package doesn't build, as the exported variables in prepare doesn't exist in other parts (like build) of the pkgbuild. After copying those variables into the build and package functions the package builds