Bugzilla Bug 26146

There has been a lot of discussion about tool chains for other architectures. 
That is all well and good, but some archs are never going to fit into that
system.  The pure embedded comilers never will.  The AVR tool chain has its own
libc that is not a part of glibc and probably never will be.  Unix will probably
never be ported to them.  There is only a C compiler.  This C compiler is
normally referenced as avr-gcc, not just gcc.

With the cross-compile stuff I have seen the first two steps would work for AVR
(binutils and bootstrapped gcc) but the rest is useless.  Then libc has to be
added manually anyway.  This is not acceptable.  Therefore, I submit this ebuild
for avr-gcc.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Created an attachment (id=15701) [details]
avr-gcc 3.3 ebuild

See bug http://bugs.gentoo.org/show_bug.cgi?id=8799 for the avr-binutils
ebuild.  An avr-libc ebuild should follow soon.

Created an attachment (id=15704) [details]
avr-gcc 3.3 ebuild

This ebuild puts everything in the right place now.  ;)

*** This bug has been marked as a duplicate of 8799 ***

How is this a duplicate of 8799?  This is an ebuild for an entirely different program.  8799 is for an assembler/linker.  This is for a C compiler.  Should I attach my ebuild here to that bug?  If so, should we rename the bug tool-cnain for AVR MCU's instead of binutils for AVR?

a

What can I do to help speed up getting these ebuilds committed to CVS?

Scott  =)

Created an attachment (id=21667) [details]
AVR GCC ebuild

This now puts uses avr-binutils out of dev-embedded.

So what's the currently supported method for building an AVR development
environment (cross-compilation and emulation)?
Neither "emerge avr-gcc" nor "CCHOST=avr emerge gcc" work. :(

emerge avr-gcc should work.  Do you see avr-gcc, avr-binutils, and avr-libc if
you look in /usr/portage/dev-embedded?

try: 

emerge -search avr

Have you rsync'd lately?

Scott  =)

"emerge avr-gcc" does not work for me (see below). I sync my portage tree
nearly daily, sometimes even several times a day.

=== Begin screenshot ===
root@cube:~# emerge -v avr-gcc
Calculating dependencies ...done!
>>> emerge (1 of 1) dev-embedded/avr-gcc-3.3-r1 to /
>>> md5 src_uri ;-) gcc-3.3.tar.bz2
>>> Unpacking source...
>>> Unpacking gcc-3.3.tar.bz2 to /var/tmp/portage/avr-gcc-3.3-r1/work
>>> Source unpacked.

!!! ERROR: dev-embedded/avr-gcc-3.3-r1 failed.
!!! Function econf, Line 367, Exitcode 1
!!! no configure script found
=== End screenshot ===

Created an attachment (id=28512) [details]
r2 ebuild

This ebuild fixes a problem created when the ebuild was changed to put it into
portage.  I had to add:

S=${WORKDIR}/${MY_P}

Since the downloaded package is not called avr-gcc.  It would not correctly
find the source directory.

Scott  =)

Using your updated ebuild I can emerge avr-gcc fine, thanks! Any chance of
getting it into the official Portage tree?  

Alas, I don't have the power.  :(  We will have to wait for someone else to do
it.

This particular bug is found at http://bugs.gentoo.org/show_bug.cgi?id=46885
where there is an ebuild for gcc-3.3.2.

Scott  =)

its there not sure why this is still open.