From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#23984: Bug avr-toolchain Date: Thu, 14 Jul 2016 21:36:09 +0200 Message-ID: <87d1mg57x2.fsf@elephly.net> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38288) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bNmRW-0003K1-JZ for bug-guix@gnu.org; Thu, 14 Jul 2016 15:37:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bNmRS-0000YS-EG for bug-guix@gnu.org; Thu, 14 Jul 2016 15:37:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:39443) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bNmRS-0000YH-AS for bug-guix@gnu.org; Thu, 14 Jul 2016 15:37:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bNmRS-0004Zo-0S for bug-guix@gnu.org; Thu, 14 Jul 2016 15:37:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Daniel Pimentel Cc: 23984@debbugs.gnu.org Daniel Pimentel writes: > I'd like report a bug in our avr-toolchain. I try compile to Arduino > plataform using Microscheme (installed with: guix package -i > microscheme) on GuixSD, but there are errors. > > I did: > sudo microscheme -m UNO -d /dev/ttyACM0 -au lightom.ms > > Output: > ... > 32 lines compiled OK > Assembling... > ... > avr-ld: cannot find crtatmega328p.o: No such file or directory This looks like a search path issue. If you copy this file from the depths of the output directory to the current directory it should work fine (works for me). > ... > avrdude: Device signature = 0x1e950f > avrdude: reading input file "lightom.hex" > avrdude: can't open input file lightom.hex: No such file or directory > avrdude: read from file 'lightom.hex' failed These errors will disappear once the above error is fixed. Thanks for taking care of this! ~~ Ricardo