> Should this not point to /gnu/store/...-python-3...? If not, it could > probably be left alone, since any package built with it will presumably > have its shebangs patched.
It's just that Python 3 is incompatible with Python 2 but the source code has no marker in the file - so patch-shebang would have to use a crystal ball, tea leaves or whatever to find out it is indeed Python 3. I expect that patch-shebang will then see python3 and correct it - and it does. > You can use 'install-file' from (guix build utils) here to remove much > of the repitition. Ah, nice! > > + ;(supported-systems '("avr")) > > You can remove this comment. I wouldn't. It's nice to see that it's for AVR even if we don't use the whole target machinery (I tried invoking "guix build --target=avr" before and it rebuilt half the universe - not sure why. There are not many non-native inputs and the native inputs are... native). > I don't have an arduino to test this package on. Can anyone else help > with this? You can still test the compilation and linkage. My Makefile to test this looks like this: ARCHITECTURE = avr BOARD_TAG = uno # shouldn't be necessary but is CPPFLAGS += -I${HOME}/.guix-profile/avr/include # shouldn't be necessary but is. The "-L" flag order matters. LDFLAGS += -L${HOME}/.guix-profile/avr/lib/avr5 -L${HOME}/.guix-profile/avr/lib -B${HOME}/.guix-profile/avr/lib include /gnu/store/k21m6b7c8bmzxk5x73zqm0qaz769lx2d-arduino-makefile-1.5.1/share/arduino/Arduino.mk Then create a file Blink.ino in the same directory which contains: void setup() { } void loop() { } Then run $ make