Package Details: proxmark3-iceman-git 4.20469.r164.g0e95c62-1

Git Clone URL: https://aur.archlinux.org/proxmark3-iceman-git.git (read-only, click to copy)
Package Base: proxmark3-iceman-git
Description: RRG / Iceman repo - Proxmark3 RDV4.0 and other Proxmark3 platforms.
Upstream URL: https://github.com/RfidResearchGroup/proxmark3
Keywords: iceman proxmark3 rdv4.0
Licenses: GPL-3.0-or-later
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: 2
Popularity: 0.034262
First Submitted: 2019-08-28 06:29 (UTC)
Last Updated: 2025-08-03 04:11 (UTC)

Latest Comments

1 2 Next › Last »

taotieren commented on 2025-07-31 13:33 (UTC)

@giovanni Thanks!

giovanni commented on 2025-07-31 10:07 (UTC) (edited on 2025-07-31 10:08 (UTC) by giovanni)

You should correct the license field with license=(“GPL-3.0-or-later”). In addition, you should add !strip to the options, because otherwise it breaks the generated ELFs.

archi42 commented on 2024-10-07 09:31 (UTC)

This warning is easy to miss:

common_arm/Makefile.hal:116: PLATFORM=PM3OTHER is deprecated, please use PLATFORM=PM3GENERIC

Thanks @drwho for the hint with the SKIPQT and the invalid installation targets! :)

drwho commented on 2024-09-15 01:36 (UTC)

@Cryen, it's not a gcc-arm-none-eabi package issue, it's a bug in QT. ref, https://github.com/RfidResearchGroup/proxmark3/issues/2382

I cloned the source to proxmark3 and ran make SKIPQT=1 and it compiled the way it was supposed to. I then did a make clean, an export SKIPQT=1, and make, and it compiled the way it was supposed to. So, by cloning the Git repo for this PKGBUILD and adding export SKIPQT=1 to the build() function around line 60 makepkg was able to compile it successfully, but ran into another bug with some invalid installation targets. Deleting the substrings mfkey and 'nonce2key' from line 139 fixed that.

One of the later comments on that bug ticket says that patching the project file was also a working fix, which might be the right way to fix this bug. I did a little poking around in the source code but didn't see where that was.

Cryen commented on 2024-07-23 17:09 (UTC) (edited on 2024-07-23 17:10 (UTC) by Cryen)

Installing gcc-arm-none-eabi-bin or downgrading the gcc-arm-none-eabi doesn't fix the issue.

In file included from /usr/include/qt/QtCore/qfuture.h:45,
                 from /usr/include/qt/QtCore/QtCore:97,
                 from /usr/include/qt/QtGui/QtGuiDepends:3,
                 from /usr/include/qt/QtGui/QtGui:3,
                 from src/proxguiqt.h:30,
                 from src/proxgui.cpp:22:
/usr/include/qt/QtCore/qfutureinterface.h:284:37: error: template-id not allowed for constructor in C++20 [-Werror=template-id-cdtor]
  284 |     explicit QFutureInterface<void>(State initialState = NoState)
      |                                     ^~~~~
/usr/include/qt/QtCore/qfutureinterface.h:284:37: note: remove the ‘< >’
cc1plus: all warnings being treated as errors
make[1]: *** [Makefile:1004: obj/proxgui.o] Error 1
make: *** [Makefile:177: client/install] Error 2
==> ERROR: A failure occurred in build().

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.

1 2 Next › Last »