Build for Due/gShield

[perfectphase]

Hi, in advance apologies if this is the wrong place to ask this.

I'm trying to build (for the first time) g2 for Due+gShield. I've tried this on Windows10+Bash and Ubuntu 16.4.1 and have failed on both.

Basic steps: sudo apt-get install git-core make git clone https://github.com/synthetos/g2.git --recursive cd g2/g2core make CONFIG=TestV9

On the Ubuntu machine failed at:

make[1]: Leaving directory '/home/stephen/g2/Motate/Tools' Compiling c ../Motate/MotateProject/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.c -> build/TestV9-g2v9k/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.o bash: ../Motate/MotateProject/motate/../../Tools/linux/gcc-arm-none-eabi/bin/arm-none-eabi-gcc: No such file or directory ../Motate/MotateProject/motate/Motate.mk:473: recipe for target 'build/TestV9-g2v9k/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.o' failed make: *** [build/TestV9-g2v9k/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.o] Error 127

The Windows10+Bash build fails at: "Found that we're in Linux" Compiling c ../Motate/MotateProject/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.c -> build/TestV9-g2v9k/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.o bash: ../Motate/MotateProject/motate/../../Tools/linux/gcc-arm-none-eabi/bin/arm-none-eabi-gcc: cannot execute binary file: Exec format error make: *** [build/TestV9-g2v9k/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.o] Error 126

Could any point me in the correct direction?

Also is it correct that to build for the Due+gShield I need to do: make BOARD=gShield

Thanks

Stephen.

[giseburt]

The arm toolchain we are currently using is built for 32-bit on linux, so you'll need the 32-bit compatibility libraries installed on your version of linux for them to work. They are installed differently for the various version of linux, but should be easy to install.

Note: the next version of the tools (which we will switch to once tested) are build for 64-bit on linux. This means they no longer support 32-bit machines on linux. There's not a lot we can do about that, unfortunately.

@perfectphase please let us know if that solves your problem.

-Rob

[perfectphase]

Thanks, I've spun up a 32bit version of Ubuntu and it seems to be compiling OK now.

Was just hoping you could clarify the final part of my original post while I have your attention, what's the correct options for make to build for the Due/gShield? I've spent ages looking through the wiki and I think I know but I'm not 100% sure, and long the same lines, do any of the release work with the due/gShield?

Thanks,

Stephen.

[giseburt]

Ok good. There are also 32-bit compatibility libraries for 64-bit Linux, so it'll work in a 64-bit Linux.

The compile options would be something like:

make BOARD=gShield SETTINGS_FILE="..."

The BOARD=gShield part is case sensitive. The settings file would be specific to your machine or one of the defaults found in settings/. For example: SETTINGS_FILE="settings_othermill.h"

Does that help? -Rob

[perfectphase]

Thanks, that's a help. Just for context, I have a couple of TinyGv8 boards and have my own app that feeds gcode to it, and am looking to have a play with g2 to see if the changes to the comms and alarms help with the issues I'm having.

Cheers,

Stephen.

[ril3y]

perfectPhase,

Have you posted your code? We are always interested in new stuff for TinyG and G2.

Thanks!

[wedges]

@perfectphase , You just have to add some i386 lib to your x64 linux; On ubuntu: sudo apt-get install -y libc6-i386 lib32stdc++6 lib32gcc1 lib32ncurses5 lib32z1

But no way to make it work with Windows 10+Bash...

[adleal]

@perfectphase

I've run into the same problem but since I'm compiling on Raspbian a 32-bit system I'm not sure why I'm getting the same error you were:

make: *** [build/TestV9-g2v9k/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.o] Error 126

[giseburt]

@adleal You've run into another issue altogether. It appears we check for Linux but not architecture, so it's downloading the Intel tools and you're on an ARM processor.

Since the tools we use have been moved to ARM's web site, this has changed. They don't have an ARM build (interestingly) and the Linux build is 64-bit only now. https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads

So some refactor is needed it appears.

[adleal]

@giseburt

Thanks for the clarification Rob... I wasn't even considering the difference in architecture. So I guess my best bet for now would be to move to a 32-bit Intel based Linux system and recompile there.

[justinclift]

Hey all, this issue looks pretty old and it seems like it's solved.

Is it ok to close this one, or are there bits that still need stuff done? :smile:

[adleal]

I wound up using a work around by loading linux on an older computer and compiling on there. Is there another way to do it now?

[justinclift]

Hmmm, it should work on 64-bit Linux "fairly easily" these days. I say "fairly easily" because when I tried it a few weeks back on CentOS 7 64-bit it "just worked".

Hadn't actually realised until reading this issue that there had been 32-bit vs 64-bit problems in the past, nor architecture issues to work through (eg compiling on ARM vs Intel host).

But, that's just one fairly-new-to-the-project persons viewpoint so far. If you want to try compiling stuff again on a recent 64-bit Linux system that'd help verify things. :smile:

[adleal]

Ok will see if I can try it next week.

[justinclift]

Awesome, please do. :smile:

[giseburt]

Some more info: The versions of the gcc toolchain we use (built by ARM) in edge and master are only available in 32-bit for Linux. So for most Linux machines running in Intel (or compatible) hardware you’ll need the 32-bit compatibility installed. For many people they may have already installed those, for others they’ll see this issue pop up.

Now for the near future branches like Dev-168 that we are wrapping up and will pull soon, they use a newer version of the ARM toolchain (to get C++17 support, along with other bug fixes) which is now the opposite: they’re only available for 64-bit on Intel Linux. For most people that will not be an issue. For those on 32-bit intel Linux there’s not really a solution. :-/

This isn’t really something we have control over, unfortunately. We are using the gcc and related build tools provided by ARM, and they stopped building them for 32-but Linux.

-Rob On Thu, Apr 12, 2018 at 5:59 PM Justin Clift notifications@github.com wrote:

Awesome, please do. 😄

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/synthetos/g2/issues/205#issuecomment-380969570, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXj0dBYGH710Eu43JgNMAZ3wBIMxrddks5tn9xKgaJpZM4LUyhZ .

[justinclift]

k. That sounds like we'll be requiring 64-bit Linux (at least on Intel) in the near-ish future.

When that happens, we should update our docs to mention it, just to keep things clear for people. :smile:

[justinclift]

@adleal Reminder ping. :smile:

[adleal]

Okay, I was able to get a 64-bit Linux system running but when I went to compile I got this error:

make[1]: Leaving directory '/home/alex/g2/Motate/Tools'
Compiling c ../Motate/MotateProject/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.c
    -> build/TestV9-g2v9k/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.o 
bash: ../Motate/MotateProject/motate/../../Tools/linux/gcc-arm-none-eabi/bin/arm-none-eabi-gcc: No such file or directory
../Motate/MotateProject/motate/Motate.mk:475: recipe for target 'build/TestV9-g2v9k/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.o' failed
make: *** [build/TestV9-g2v9k/motate/cmsis/TARGET_Atmel/sam3x/source/templates/exceptions.o] Error 127

[justinclift]

Damn. That looks like it's not downloading the right bits for you for some reason. With the 64-bit Linux you got running, which distro and which architecture? :smile:

[adleal]

Okay after rereading the thread carefully I installed the 32-bit Linux compatibility using:

sudo apt-get install lib32ncurses5 lib32z1

and was then able to compile successfully:

Exporting symbols bin/TestV9-g2v9k/g2core.elf.txt Making binary bin/TestV9-g2v9k/g2core.bin --- SIZE INFO --- text data bss dec hex filename 162896 0 35024 197920 30520 bin/TestV9-g2v9k/g2core.elf Build 100.26 100.26-10-g1ff7

[justinclift]

Cool! :smile: