Ebuild for devkitarm as it was not yet in Portage. Website: http://www.devkitpro.org/ Category: dev-util Ebuild name: devkitarm (official name) ##### Begin description: DevkitARM is a devkitpro toolchain for ARM processors. That provide gcc for ARM processors and help to make homebrews for DS, GBA and GP32. ##### End description.
Created attachment 119780 [details] Ebuild for devkitarm-bin-20 Ebuild for last bin version of devkitARM.
Created attachment 119781 [details] Env.d file for devkitarm
This is now in the sunrise overlay. You can find it at: http://overlays.gentoo.org/svn/proj/sunrise/sunrise/dev-util/devkitarm-bin/ NB : ebuild name is not devkitarm but devkitarm-bin. My mistake in the initial description.
Created attachment 119789 [details] Ebuild for devkitarm-bin-20 Add insopts to make installed files executable.
Has been reviewed on Gentoo Sunrise Overlay : http://overlays.gentoo.org/svn/proj/sunrise/reviewed/dev-util/devkitarm-bin
Created attachment 139430 [details] Ebuild for devkitarm-bin-21 Update can also be found in the sunrise overlay.
Please, if it will be included in portage's overlay, include also r20 version, as PAlib for NDS needed it and doesn't support yet the r21 version (1) (1): http://palib.info/forum/modules/newbb/viewtopic.php?topic_id=3854
-r22 is out and why not source version? there are buildscripts available at sf.net
i apologize, latest released buildscripts are for -r21, though next ones will be out in the near future
Created attachment 150920 [details] Ebuild for devkitarm-bin-22 Update can also be found in the sunrise overlay. I'm looking at buildscripts but it looks to install automaticaly install libnds, libgba, libfat and others. It's going to be difficult to make it compatible with these ebuilds (libnds and others).
Created attachment 158555 [details] Updated ebuild : 23b New ebuild for devkitarm-bin : 23b version. buildscripts are still not working so we must keep a bin version :(
> buildscripts are still not working so we must keep a bin version :( have you tried fresh and corrected 20080624 buildscripts?
(In reply to comment #12) > > buildscripts are still not working so we must keep a bin version :( > have you tried fresh and corrected 20080624 buildscripts? > I didn't know there was a new release of buildscripts (last tested was from early june). Unfortunately, there is the same error. I posted it into devkitpro forums (actually, it is an already-known issue). For you information, here is the error : checking dynamic linker characteristics... no checking how to hardcode library paths into programs... immediate checking for shl_load... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. gmake[1]: *** [configure-target-libstdc++-v3] Error 1 gmake[1]: Leaving directory `/home/volkmar/Bordel/buildscripts/arm-eabi/gcc' gmake: *** [all] Error 2 Error building g++
latest devkitarm-bin-23b.ebuild needs to be rebuild against python 2.6.5, because revdep-rebuild tries to reemerge devkitarm-bin every time: broken /opt/devkitpro/devkitARM/bin/arm-eabi-gdb (requires libpython2.5.so.1.0) broken /opt/devkitpro/devkitARM/bin/arm-eabi-gdbtui (requires libpython2.5.so.1.0)
Created attachment 250789 [details] dev-util/devkitarm-bin-32.ebuild Updated for r32. Ebuild now supports amd64, man pages are now installed under /usr/share, and GCC versions (for QA_EXECSTRACK, though I have no idea what that does) are no longer hardcoded.
Created attachment 250791 [details] dev-util/devkitarm-bin-32.ebuild Attaching corrected ebuild. I made a few tweaks just before uploading the original copy, and discovered that those tweaks broke some permissions. Oops. New ebuild should work fine.
Hello, everyone. It seems that at least one ebuild related to this bug exists in the Sunrise overlay at the moment. However, I have to regretfully announce that after a long inactivity period the Sunrise project has been discontinued and the related overlay will be eventually removed. For this reason, I'd like to ask you to reevaluate the ebuilds and consider moving them. If you'd like to maintain a package from Sunrise in Gentoo, please take a look at our Proxy Maintainers [1] project. Please make sure to take ebuilds from the unreviewed developer Sunrise repository [2] rather than the -reviewed one, since the latter has not been updated for over a year. While at it, please note that: 1. Adding a package to Gentoo requires declaring yourself as an active maintainer for it. All bugs regarding the package will be assigned to you, and you will be expected to maintain it. 2. Some packages may not be suitable for addition anymore. While there's no strong rules that would prevent you from adding a package, it may be a bad idea to add old-unmaintained packages that will shortly result in a large number of bugs reported with no solution. If that is the case, please close the bug as RESOLVED/OBSOLETE to make it easier to find packages worth adding. 3. Some of the bugs were already closed as WONTFIX/OBSOLETE/... while the relevant ebuild was kept in Sunrise. If you disagree with the original decision, you still can add the ebuild via proxy-maint. 4. Pleaes note that many of the Sunrise ebuilds are old and may be buggy. If you decide to move them, please make sure to update/clean them up. The proxy-maint team will also review your ebuilds, therefore making sure they land in Gentoo in good quality. Once again, thank you for your contribution. We hope that you will still want to contribute to Gentoo, through proxy-maint or otherwise. [1]:https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers [2]:https://gitweb.gentoo.org/proj/sunrise.git/
