Getting Started with avr-gcc on Linux

[PeterHouseJr]

I have compiled avr-gcc 14.1.0 in ~/avr-gcc-build. I can go into the folder ~/avr-gcc-build/build/avr-gcc-14.1.0-x64-linux/bin and run ./avr-gcc and it runs with the expected error for no input files.

My question is "Now what to I do?"

I would like to be able to run avr-gcc from my project folder using my makefile. Should I leave avr-gcc where it is and reference the exact location and I do not know how the compiler will find the libraries unless it uses it's own location and relative references?

Where should I put the files and how should I set up/modify the execution search path?

Thank you ! ! !

[ZakKemble]

Heya, IIRC it should be able to find all of the libraries and things if you keep it where it is.

Have a look at this project to get an idea of how to set things up https://github.com/ZakKemble/SmartPowerBankKeepAlive

cd into the firmware folder and run:

make COMPILER=~/avr-gcc-build/build/avr-gcc-14.1.0-x64-linux/bin/ (can't remember if the last slash is needed or not)

or edit the makefile and set the COMPILER variable on line 16 https://github.com/ZakKemble/SmartPowerBankKeepAlive/blob/main/firmware/Makefile#L16

It's also possible to add the location of your gcc build to your PATH environment variable, then you don't need to do any special make stuff (best to google this one, there's lots of ways to do it)

[PeterHouseJr]

Thank you so much for your quick and helpful response.

I started in the days when we wrote the assembler code on paper forms, hand assembled the code, and then toggle the code into the computer with switches!

In the last 20 years or so I have been spoiled by IDE's and now they are getting bloated and unreliable, especially when new versions are released, and subtle things change like the compiled object code!

I added the compiler build folder to the PATH and slightly modified your suggested Makefile for my project and all seems to be working well now. Very nice Makefile, BTW.

export PATH=~/avr-gcc-build/build/avr-gcc-14.1.0-x64-linux/bin:$PATH

[PeterHouseJr]

Zak, Here is what I came up with for a Raspberry Pi Basic install of your avr-gcc for all users: - avr-gcc 14.1.0 Basic Installation for All Users - Full Build Installation - Preferred - install linux gcc, tools, and man pages - ```sudo apt update``` - ```sudo apt install build-essential``` - ```sudo apt install manpages-dev``` - github.com/ZakKemble/avr-gcc-build - Get avr-gcc - Place in /etc/avr_gcc-build - ```sudo git clone https://github.com/ZakKemble/avr-gcc-build /etc/avr-gcc-build``` - Modify Build Script - ONLY compile for Linux - ```sudo nano /etc/avr-gcc-build/avr-gcc-build.sh``` - ```FOR_LINUX=${FOR_LINUX:-1}``` - Set All Others to :-0 - ```FOR_WINX64=${FOR_WINX64:-0}``` - Make Build Script Executable - ```sudo chmod +xxx /etc/avr-gcc-build/avr-gcc-build.sh``` - Run the Build Script - Takes a long time - 3505 Seconds (0h59m) on RPi5 w/M.2 SSD - 9708 Seconds (2h42m) on Pi 4 w/USB SSD - Change to Build Script Folder - ```cd /etc/avr-gcc-build``` - ```sudo ./avr-gcc-build.sh``` - Modify the PATH environment variable - Add this command to .bashrc or .bash_profile - ```export PATH=/etc/avr-gcc-build/build/avr-gcc-14.1.0-x64-linux/bin:$PATH``` - Either Reload your Terminal - OR - Use this for the current session - ```source .bashrc``` - Test - In your Home folder ~ - ```avr-gcc``` - Should respond with: - ```avr-gcc: fatal error: no input files``` - ```compilation terminated.``` - If reonse is: - ```-bash: avx-gcc: command not found``` - Check - the location of the executable - the PATH environment variable is correct - try: - /etc/avr-gcc-build/build/avr-gcc-14.1.0-x64-linux/bin/avr-gcc I hope this helps! Thank you for your help and assistance, Peter House

[rubenswe]

@PeterHouseJr Great write up. I got this error "avr-gcc cannot execute binary file: Exec format error". Running Pi OS Lite.
How did you make this run on the Pi? Looks like its only for x64 architecture, not ARM? Thanks.

[PeterHouseJr]

Did you compile on your Pi OS Lite machine? This should always produce a correct executable file for the compiling machine.

Use ls -la to make sure the avr-gcc file is executable.

Use where avr-gcc to make sure the file is in a correct execution search path.

[rubenswe]

I started compiling on the Pi but it took over an hour and it was running the CPU at 100% and 75degC so I got a bit worried. I booted a VM instead but that was x64 so I guess thats where the fault is. I see now that you also took a long time to build using the Pi, so I should've been more patient!

[PeterHouseJr]

Patience is somtimes a virtue and other times a burden. The problem is discerning the outcome in advance.

[PeterHouseJr]

A good fan might help to keep the processor from throttling during compile, and speed things up a bit.

[rubenswe]

Appreciate it Peter, I will make a setup and try again!