arduino-0018 was released on 2010.01.29 release notes: http://arduino.cc/en/Main/ReleaseNotes since then 0017 is unsupported
There seems to be a problem with their .tgz file. I simply renamed the arduino ebuild to 0018, and I got an error while unpacking. Just using plain old tar on the .tgz gave the error: gzip: stdin: not in gzip format tar: Child returned status 1 tar: Exiting with failure status due to previous errors On their Google Code page, they have a 64-bit package which does extract. http://code.google.com/p/arduino/downloads/list
Hmm... It looks like the .tgz file does actually extract now. I downloaded it twice, and I got errors both time, but the third time it worked.
(In reply to comment #1) > There seems to be a problem with their .tgz file. The download URL has changed. All our patches have to be reworked as well. The new SRC_URI will need to be http://arduino.googlecode.com/files/${P}.tgz
Is there any progress on this? What needs to be done?
See comment #3.
Still no progress, here?
Created attachment 231229 [details] dev-embedded/arduino-0018.ebuild Fixes the URL change and removes Makefile patching (no longer needed). mv files/arduino-script-0017.patch files/arduino-script-0018.patch (and works at least for me)
> (and works at least for me) Working here on ~amd64, although I don't think the arduino executable is in $PATH any more.
I don't have many details yet.. What I just tried was: Removing the Makefile patch. Remove pkg_postinst(). Use the 0017 script patch. Fix SRC_URI to the new location. Works so far.. Also a einfo about ldscripts would be good like (example) "Don't forget to 'ln -s /usr/lib64/binutils/avr/2.20.1/ldscripts /usr/avr/lib/ldscripts'"
If I try this arduino-0018.ebuild I get first the warning: >>> Install arduino-0018 into /var/tmp/portage/dev-embedded/arduino-0018/image/ category dev-embedded chmod: cannot access `/var/tmp/portage/dev-embedded/arduino-0018/image//usr/share/arduino-0018/hardware/libraries': No such file or directory and if I then try to verify the example sketch Digital->Blink, I still get as with arduino-0017: Error Compiling: unknown MCU 'atmega328p' specified Known MCU names: avr2 at90s2313 ... /usr/share/arduino-0018/hardware/arduino/cores/arduino/wiring_shift.c:1: Fehler: MCU »atmega328p« nur für Assemblierung unterstützt
After installing the toolchain with: USE="-openmp" crossdev -t avr -s4 -S --g 4.3.3 --without-headers the issue with "unknown MCU 'atmega328p' specified" disappeared. (I forget the --g 4.3.3 option during my last install).
The arduino-0018.tgz archive comes without an Makefile in arduino-0018/hardware/arduino/cores/arduino directory. The Makefiles for arduino-0018 which I found in the WEB : http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1265576847 http://leepike.wordpress.com/makefile/ are not well designed for Gentoo. The Makefile tries to write the object files into or below the install directory, which is not good, if you call 'make' as ordinary user and if arduino is installed by gentoo under /usr/share/arduino-00XX. Whereas a ordinary user has no problems to use the arduino-ide. Has anybody a Makefile for arduino to compile and upload sketches as an ordinary user under gentoo.
Created attachment 241411 [details] Makefile for compiling and uploading of sketches for ordinary Gentoo users I hope it is useful for someone
(In reply to comment #13) > Created an attachment (id=241411) [details] > Makefile for compiling and uploading of sketches for ordinary Gentoo users > > I hope it is useful for someone > Yes, that saved me doing it myself. If that makefile is made into a patch, then I don't think there's any reason to use the obsolete version in portage anymore.
Oh this is assigned to me vs me being on the CC: Sorry guys but I thought another maintainer took this package over. Any developer is free to take over this package (hint idl0r). It's recommended to not have to depend on java-ide just to be able to upload a sketch (ala Makefile).
Created attachment 241509 [details] arduino-0018.ebuild with cores_Makefile-0018.patch
Created attachment 241511 [details] cores_Makefile-0018.patch
Created attachment 241625 [details] cleaned arduino-0018.ebuild
Created attachment 241627 [details] enhanced cores_Makefile-0018.patch for extern setting of PORT etc and to avoid the __cxa_pure_virtual error
Comment on attachment 241511 [details] cores_Makefile-0018.patch obsolet
Tried 0018-r1 to have a go at the Makefile. The location of the Makefile is actually in /usr/share/arduino-0018/hardware/arduino/cores/arduino/Makefile, slightly different to what's printed. Trying the Makefile: Warnings from gcc 4.3.3 cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++ cc1plus: warning: command line option "-std=gnu99" is valid for C/ObjC but not for C++ CXX invocation uses CINCS not CXXINCS, but it's not used anyway? LIBRARIES path is now $INSTALL_DIR/libraries. Not that it matters, I can't work out how to use libraries via any Makefile I've seen for the arduino. If the Makefile says depend on avrdude 5.8, can this be in the ebuild? Same for "dev-perl/Device-SerialPort"? Out of interest does this Makefile allow multi-file compilation or am I using it wrong?
0019 almost there: http://code.google.com/p/arduino/downloads/list Perhaps we should target the RC.
(In reply to comment #22) > 0019 almost there: > http://code.google.com/p/arduino/downloads/list > > Perhaps we should target the RC. > And 0019 is actually there. We're very outdated with 0017.
Created attachment 248579 [details] new ebuild (and necessary files) for 0019
(In reply to comment #24) > Created an attachment (id=248579) [details] > new ebuild (and necessary files) for 0019 > Built this and been using it for a while. Seems to be fine. Please merge.
(In reply to comment #24) > Created an attachment (id=248579) [details] > new ebuild (and necessary files) for 0019 > Builds and works fine for me.
They are up to 0021 now, but I noticed that the tarballs seem to be double-gzipped. You can gunzip it once, rename it back to tar.gz, and then tar zxvf normally. Needing to symlink the ldscripts should maybe be a bug for crossdev. I updated this page with more up-to-date notes on how to manually install, until the version bump gets done: http://www.arduino.cc/playground/Linux/Gentoo
(In reply to comment #27) > Needing to symlink the ldscripts should maybe be a bug for crossdev. http://bugs.gentoo.org/show_bug.cgi?id=340114
0021 already available See: https://bugs.gentoo.org/show_bug.cgi?id=339788
Since there are a bunch of outstanding bugs for Arduino-related ebuilds that haven't yet made it into the main portage tree, I've created an overlay that brings them all together for more convenient testing and updating: git://gitorious.org/gentoo-arduino/arduino.git I'll try to keep up with new Arduino-related ebuilds and add them as I can, but anyone who files a bug here with an ebuild related to Arduino development is welcome to add me to the CC list, or email the ebuild to me directly.
*** Bug 367407 has been marked as a duplicate of this bug. ***
*** Bug 339788 has been marked as a duplicate of this bug. ***
*** Bug 347349 has been marked as a duplicate of this bug. ***
Created attachment 274123 [details] arduino-0022.ebuild
Created attachment 274125 [details, diff] arduino-script-0022.patch
Created attachment 274127 [details] rxtx-2.2_pre2.ebuild required for arduino-0022
Created attachment 274129 [details] ChangeLog for rxtx-2.2_pre2
Created attachment 274131 [details] rxtx/files/lockfiled.xinetd for rxtx-2.2_pre2
Created attachment 274133 [details, diff] rxtx/files/rxtx-2.2pre2-lfd.diff for rxtx-2.2_pre2
Created attachment 274135 [details, diff] rxtx/files/rxtx-2.2pre2-nouts.diff
I attached some files, which were necessary for me to emerge arduino-0022.
can this be in portage main tree any soon ?
(In reply to comment #42) > can this be in portage main tree any soon ? You can get all the needed ebuilds and patches from the overlay at git://gitorious.org/~luksan/gentoo-arduino/luksans-arduino.git while you're waiting for this to hit gentoo-x86
To comment 43, how can I add this overlay to my overlays? It seems me that it is not possible with layman.
(In reply to comment #44) > To comment 43, how can I add this overlay to my overlays? It seems me that it > is not possible with layman. run "git clone git://gitorious.org/~luksan/gentoo-arduino/luksans-arduino.git", this will create a new directory called luksans-arduino. Then add the full path to that directory to your PORTDIR_OVERLAY variable in /etc/make.conf. To update the overlay, cd into the directory and run "git pull".
I have trouble with arduino-0022 eeprom library, here. No matter using arduino or eclipse. I use cross-dev libc and gcc ../src/fan_control.cpp:605: undefined reference to `EEPROM' ../src/fan_control.cpp:605: undefined reference to `EEPROM' ../src/fan_control.cpp:605: undefined reference to `EEPROMClass::read(int)' ../src/fan_control.cpp:605: undefined reference to `EEPROMClass::read(int)' ../src/fan_control.cpp:605: undefined reference to `EEPROM' ../src/fan_control.cpp:605: undefined reference to `EEPROM' ../src/fan_control.cpp:605: undefined reference to `EEPROMClass::write(int, unsigned char)' ../src/fan_control.cpp:605: undefined reference to `EEPROMClass::write(int, unsigned char)' When adding eeprom lib stuff to project it becomes: ./libs/EEPROM/EEPROM.o: In function `EEPROMClass::write(int, unsigned char)': ../libs/EEPROM/EEPROM.cpp:47: undefined reference to `__eerd_byte_m328p' ../libs/EEPROM/EEPROM.cpp:47: undefined reference to `__eewr_byte_m328p'
ARDUINO 0023 - 2011.11.09 * Added .inf files for R3 boards. * Updated to optiboot 4.4. * Included combined firmwares for ATmega16U2.
I pushed out an updated ebuild for arduino-0023. Check it out at https://gitorious.org/~luksan/gentoo-arduino/luksans-arduino
arduino-1.0 released.
*** Bug 393469 has been marked as a duplicate of this bug. ***
it should be possible to add a "teensy" use flag in case anyone wants to add support to the teensy board (using the official teensy addon) automatically. documentation : http://www.pjrc.com/store/teensypp.html http://www.pjrc.com/teensy/teensyduino.html
Here is an updated arduino-1.0 ebuild. Crossdev is currently broken for building avr toolchains. I updated the instructions on getting it working here: http://en.gentoo-wiki.com/wiki/Crossdev#AVR_Architecture Funtoo users see here for additional necessary steps: http://forums.funtoo.org/viewtopic.php?pid=5342 I would love to add a teensy use flag but as far as I know currently the only way to install teensyduino is a graphical installer. I emailed the author to see about getting it in some other form.
Created attachment 297829 [details] arduino-1.0.ebuild
Created attachment 297831 [details, diff] arduino-script-1.0.patch
fails for me: >>> Install arduino-1.0 into /var/tmp/portage/dev-embedded/arduino-1.0/image/ category dev-embedded !!! dodoc: readme.txt does not exist dodoc failed * ERROR: dev-embedded/arduino-1.0 failed (install phase): * dodoc failed what does this comment mean? "# jednak to selhava v ebuildu, vsecko je jinde, druhak se mi nezda ze by ide neco kompilovalo napoprve"
Created attachment 297861 [details] arduino-1.0.ebuild
Woops, guess I didn't double check it before posting as that stuff slipped in from an ebuild for an older arduino version I was copying from. I have cleaned up the ebuild and removed the problem. I have no idea what that says. Should all be good to go now.
I have created an local arduino overlay /usr/local/portage/dev-embedded/arduino with the arduino-1.0.ebuild. How can I avoid that 'emerge arduino' tries to install arduino-0017 from /usr/portage/dev-embedded/arduino ?
echo ">=dev-embedded/arduino-0015-r1" >> /etc/portage/package.mask
Portage obviously doesn't know that 1.0 is newer than 0017. Is there a proper way to deal with the change in version number scheme or are the older ebuilds just going to have to be removed or masked?
everything compiles for the uno but when i switch to the teensy (I installed teensyduino) i have this coming out: collect2: ld terminated with signal 11 [Segmentation fault] if i switch back to the uno everything compiles..... help
Teensyduino isn't currently supported since it requires running a graphical installer. That said it is working fine for me. Only problem I had was that the teensy loader is dynamically linked against an older version of libpng. That error looks more like a problem a problem with your avr toolchain. Feel free to email me directly with the full output and what if any patches you have installed to get the toolchain working. Its not really relevant here.
Hi Jess - I have been working on an ebuild for arduino-1.0 without realising you have done it! Anyway, I did come across an issue with version 1 in hardware/arduino/cores/arduino/Print.cpp which I patched along the way. For completeness, I will upload my version of the ebuild, and the patches. I would be interested in your comments!
Created attachment 299675 [details] Alternative arduino-1.0.ebuild
Created attachment 299677 [details, diff] Patch to fix deprecated prog_char in Hardware/arduino/cores/arduino/Print.cpp
Created attachment 299679 [details, diff] build.xml patch to use system libraries and avoid library mismatch error
Created attachment 299681 [details, diff] Arduino patch - for use with paulj's ebuild
Sorry - I should have been clearer - my ebuild compiles the source rather than installing the binary. I felt it was more gentoo :)
(In reply to comment #56) > Created attachment 297861 [details] > arduino-1.0.ebuild Looks very good, I modified it a little to comply with QA and pushed it into the tree. Thanks! (In reply to comment #68) > Sorry - I should have been clearer - my ebuild compiles the source rather than > installing the binary. I felt it was more gentoo :) Thanks for your effort but I don't think it is worth it. Feel free to convince me otherwise :) I'm using your "prog_char" patch though.
(In reply to comment #69) > (In reply to comment #56) > > Created attachment 297861 [details] > > arduino-1.0.ebuild > > Looks very good, I modified it a little to comply with QA and pushed it into > the tree. Thanks! > > (In reply to comment #68) > > Sorry - I should have been clearer - my ebuild compiles the source rather than > > installing the binary. I felt it was more gentoo :) > > Thanks for your effort but I don't think it is worth it. Feel free to convince > me otherwise :) I'm using your "prog_char" patch though. Glad to have contributed something! Good to see it in the main portage tree (although I haven't yet changed over from mine :))