AVR Freaks

I'm trying to use your script to build only avr-gcc + avr-libc.

When I first got the error, I thought I needed libiberty.a installed, so I installed binutils-devel, and now have:
/usr/lib64/libiberty.a

I still get the above build error though.

Any ideas what I need to do to get it to work?
Here's the contents of the directory I call the build script from:

In case you need more details, I copied buildavr.log to http://162.248.164.251/files/

./config usually produces a log file that reveals any issues.

Thanks for the help.  With 4.9.2 out, I took another look.  My screw-up came from reading the comments in getfiles.sh:
 

#
# Get MPC - Needed for GCC >= 4.5.0
#

There was no such comment for GMP & mpfr, so I thought they weren't required.  Reading the gnu docs makes it clear that they are required.

https://gcc.gnu.org/install/prer...

I added back GMP & mpfr to the get-files and build scripts, re-ran the get-files, and am running the build script as I type this.

I think I found a bug in the build script.  In the buildavr.log I found the following:

cp: cannot stat `gmp-6.0.0a/*': No such file or directory

This is from the following line in the build script:

   cp -rfp ${gmpbase}/* ${gccbase}/gmp

The problem is the script assumes the basename of the gmp archive (gmp-6.0.0a) is the name of the directory created when the archive is extracted.  However the directory name in gmp-6.0.0a.tar.bz2 is gmp-6.0.0 (no 'a' suffix).

I manually copied the gmp source files and re-ran the build script.

For latest Atmel device support you are (currently) better off sticking to Atmel builds. So while 4.9 may look enticing I'd just take Atmel's 4.8.1 and use that for the time being. Atmel haven't released a toolchain for a while so I rather suspect they are waiting for the 4.9 dust to settle and we may see one shortly anyway.

They are working (see the check in history at the AVR-LibC repo and all the activity from Atmel employees) to push their private changes for added device support back upstream so the generic build will mirror their own local build at which point it won't be necessary to have an Atmel one at all - but that's still work in progress and until then the Atmel builds remain the best option - especially for "none mainstream" devices like the one you want to use.

Message

  The system has encountered an error. Details of which should follow...

ERROR

Target binary, dcp extraction not possible. Cannot find the target.

While attempting to download the Windows AVR 8 3.4.5 tool chain and headers

3.4.4 had the same problem, Linux x64 wasn't available at first.  Give it a few days...
 

I'm certain it has already been built.  Rather it's the website which isn't properly updated.

Last but not least, where do I put the header files? The file structure seems to be vastly different for each build of the AV tool chain, the Eclipse AVR add in can't find them.

Oh, Eclipse on Raspberry, that was a trip.

Last but not least, where do I put the header files?

I think the relative location of the the .h to the .bin is something controlled by the .config usually an avr8 build has this structure:

E:\avr8-gnu-toolchain-linux_x86_64>tree
Folder PATH listing for volume VBOX_windows
Volume serial number is 0000-FC03
E:.
├───libexec
│   └───gcc
│       └───avr
│           └───4.8.1
│               ├───install-tools
│               └───plugin
├───lib64
├───include
├───share
│   ├───man
│   │   ├───man7
│   │   └───man1
│   ├───info
│   └───doc
│       ├───cppinternals
│       ├───gccinstall
│       ├───cpp
│       ├───gcc
│       ├───gccint
│       └───mpfr
│           └───examples
├───lib
│   └───gcc
│       └───avr
│           └───4.8.1
│               ├───avrxmega2
│               ├───avr5
│               ├───avr3
│               ├───avrxmega6
│               ├───include
│               ├───avr7
│               ├───install-tools
│               │   └───include
│               ├───avr4
│               ├───avrxmega7
│               ├───plugin
│               │   └───include
│               │       ├───java
│               │       ├───ada
│               │       │   └───gcc-interface
│               │       ├───cp
│               │       ├───objc
│               │       ├───c-family
│               │       └───config
│               │           └───avr
│               ├───avrxmega5
│               ├───avr35
│               ├───tiny-stack
│               ├───avr25
│               │   └───tiny-stack
│               ├───avrtiny
│               ├───avr31
│               ├───avr51
│               ├───include-fixed
│               ├───avr6
│               └───avrxmega4
├───avr
│   ├───include
│   │   ├───avr
│   │   ├───compat
│   │   └───util
│   ├───lib
│   │   ├───ldscripts
│   │   ├───avrxmega2
│   │   ├───avr5
│   │   ├───avr3
│   │   ├───avrxmega6
│   │   ├───avr7
│   │   ├───avr4
│   │   ├───avrxmega7
│   │   ├───avrxmega5
│   │   ├───avr35
│   │   ├───tiny-stack
│   │   ├───avr25
│   │   │   └───tiny-stack
│   │   ├───avrtiny
│   │   ├───avr31
│   │   ├───avr51
│   │   ├───avr6
│   │   └───avrxmega4
│   └───bin
├───man
│   ├───man3
│   └───man1
├───info
├───doc
│   ├───binutils
│   │   ├───as.html
│   │   ├───ld.html
│   │   ├───bfd.html
│   │   ├───binutils.html
│   │   └───gprof.html
│   └───avr-libc
│       ├───avr-libc-user-manual
│       └───examples
│           ├───largedemo
│           ├───twitest
│           ├───asmdemo
│           ├───demo
│           └───stdiodemo
├───bin
└───x86_64-pc-linux-gnu
    └───avr
        ├───include
        └───lib

The avr-gcc etc are in ./bin and the base of the includes are at ../avr/include/ from there - that would be the directory with stdio.h and so on. Then all the AVr specific stuff is in an ./avr/ from there (that is ../avr/include/avr/ from the ./bin/) which is why io.h is referred to as <avr/io.h> in AVR programs.

To be honest I don't know why you don't just get the .tar.gz from atmel.com and unpack it (though I understand the current issue with no linux64 build).

Had to give up on AVR Linux, the tools are 4.81 and the Eclipse AVR add in does not pick up the arv/io.h file so it will not allow selection of a MCU. I did a git and found where he was parsing the directories but couldn't figure out why it was failing.

Atmel Studio 6.2 (AS) on Windows 10 was working until they installed the latest build, it killed all the USB drivers, didn't like them, they were not branded by Microsoft so they killed them. Several application from the 'Store' died too so Atmel is not alone.

I restored a snap-shot of my Windows 7 workstation system before I installed AS and installed AS again, after it installed the first time I ran it AF told me it had an update, 100mb or so later it was install and now AS on Windows 7 x64 is working. 

Here is the deal: gcc 4.80 ~ 4.82 are known to be faulty, the current compiler for AVR8/32 is gcc 4.81 for ARM 4.84 so is it safe to use 4.81 on an AVR8 device?

C:\Program Files (x86)\Atmel\Atmel Toolchain\ARM GCC\Native\4.8.1437\arm-gnu-toolchain\arm-none-eabi\bin>

gcc version 4.8.4 20140725 (release) [ARM/embedded-4_8-branch revision 213147] (Atmel build: 371)

I would go back 1970 and command line everything like the good old days of masm using ed but I'm getting lazy in my old age.

Parts are here, circuit boards are 14 days out, building a prototype out of P-dip transceivers parts and UNO's