the current stable version, avr-libc-1.8.0 is not compatible with the current stable gcc-5.4.0 (see https://bugs.gentoo.org/show_bug.cgi?id=617432). avr-libc-2.0.0 works for me, please stabilize.
Dear arches please stabilize requested version, current stable is b0rk3d.
It's a surprise for me we have avr-libc keyworded for non-avr platforms. AFAIU those keywords are never used when you use crossdev. Are they?
(In reply to Sergei Trofimovich from comment #2) > It's a surprise for me we have avr-libc keyworded for non-avr platforms. > AFAIU those keywords are never used when you use crossdev. Are they? I am not part of dev-embedded but as I know the package architectures are not relevant for the avr target platform, as it used to generate the binaries on the source system. For example fedora supports even more arches. https://rpmfind.net/linux/rpm2html/search.php?query=avr-libc
(In reply to Johannes Huber from comment #3) > (In reply to Sergei Trofimovich from comment #2) > > It's a surprise for me we have avr-libc keyworded for non-avr platforms. > > AFAIU those keywords are never used when you use crossdev. Are they? > > I am not part of dev-embedded but as I know the package architectures are > not relevant for the avr target platform, as it used to generate the > binaries on the source system. For example fedora supports even more arches. > > https://rpmfind.net/linux/rpm2html/search.php?query=avr-libc But in the of the day is up to the arch team to destabilize a package (and reverse deps) to reduce workload, especially on minor arches.
Ah, crossdev uses any stable or any unstable to pick proper avr keyword: 'cross-avr/avr-libc * ~* -ia64 -~ia64' I'll leave only amd64 in KEYWORDS and add a comment that real keyword does not matter here.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=30ced618e7be3784f62fc45e83105f922b325406 commit 30ced618e7be3784f62fc45e83105f922b325406 Author: Sergei Trofimovich <slyfox@gentoo.org> AuthorDate: 2017-10-30 22:23:25 +0000 Commit: Sergei Trofimovich <slyfox@gentoo.org> CommitDate: 2017-10-30 22:30:56 +0000 dev-embedded/avr-libc: drop all keywords except amd64, bug #620316 dev-embedded/avr-libc is not installable as-is on any ARCH gentoo currently supports. It should have been a KEYWORDS=avr but there is no ARCH=avr profiles (at least yet). To explain meaning of KEYWORDS let's look at a concrete example: When cross-toolchain is installed with crossdev as 'crossdev -t avr' on ia64 (as an example ARCH without existing KEYWORDS) crossdev injects the following 'package.keywords': cross-avr/avr-libc * ~* -ia64 -~ia64 (as 'man 5 portage' says:) * package is visible if it is stable on any architecture ~* package is visible if it is in testing on any architecture Basically we need something (anything) in KEYWORDS to act as a bearer of stable/unstable sign. Let it be amd64. Bug: https://bugs.gentoo.org/620316 Package-Manager: Portage-2.3.13, Repoman-2.3.4 dev-embedded/avr-libc/avr-libc-1.6.2.ebuild | 7 +++++-- dev-embedded/avr-libc/avr-libc-1.6.4.ebuild | 7 +++++-- dev-embedded/avr-libc/avr-libc-1.6.8.ebuild | 7 +++++-- dev-embedded/avr-libc/avr-libc-1.7.0.ebuild | 7 +++++-- dev-embedded/avr-libc/avr-libc-1.7.1.ebuild | 7 +++++-- dev-embedded/avr-libc/avr-libc-1.8.0.ebuild | 7 +++++-- dev-embedded/avr-libc/avr-libc-1.8.1.ebuild | 7 +++++-- dev-embedded/avr-libc/avr-libc-2.0.0.ebuild | 7 +++++-- 8 files changed, 40 insertions(+), 16 deletions(-)}
I've left only KEYWORDS=amd64. The package should really be tested on avr.
amd64 stable (thanks to Richard Kenney)
