On Mon, 8 Apr 2013, Juergen Harms wrote:
On 04/06/2013 06:35 AM, andre999 wrote:
did a little research to hopefully help a bit, on packages still in the
list.
( used http://rpmfind.net/linux/ )
cross-avr-gcc
See bugzilla: https://bugs.mageia.org/show_bug.cgi?id=7825
Looks like an incompatibilty between the object gcc (which is now 4.7.2) and
the target gcc (the specfile still pulls in 4.6.2).
To make cross-avr-gcc build
- cross-avr-binutils (which is used as a dependency) must be rebuilt
to use binutils-2.23 (the present cross-avr-binutils uses 2.20),
2.23.2 I guess?
- cross-avr-gcc must be re-built to use gcc-4.7.2 (and some tweeks - see
bugzilla 7825)
We don't really have a choice here (:
I have locally made such a build and successfully use it in production
for building the software for my AVR cpus (attached my specfile = attachment
3044).
The reasons why I did not submit my local build are that there are some
serious rpmlint warnings (serious at least for cross-avr-binutils: complaints
about the use of hardlinks) which I did not manage to get rid of - but also
that I did not want to interfere with the work of the maintainer.
The current package has the same rpmlint warnings so you don't need to fix
this right now INHO. The hardlinks are only a problem when /usr/bin is on
a different filesystem than /usr. I don't actually maintain these
packages so you will likely end up being the maintainer.
avr-libc doesn't need to be updated?
Christiaan
