Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building on Debian: cross compile packages #22

Open
greytery opened this issue Jul 15, 2014 · 5 comments
Open

Building on Debian: cross compile packages #22

greytery opened this issue Jul 15, 2014 · 5 comments

Comments

@greytery
Copy link

Building the sdk on a "standard Debian Desktop installation" (Wheezy).
The cross compile packages gcc-arm-linux-gnueabihf and g++-arm-linux-gnueabihf do not appear as part of the basic Debian repositories. Instructions on how to include them for Synaptec or apt-get would be appreciated.

Perhaps the Fedora and Ubuntu instructions should also be tested and updated. The packages appear to be available in the Ubuntu 14.04 repositories - but perhaps Debian are a bit more careful?

@bcxcube
Copy link
Contributor

bcxcube commented Jul 15, 2014

greytery,

Please have a look at the link below. It should point you in the right direction for installing the ARM cross toolchain for Debian platforms.

https://wiki.debian.org/BuildingCrossCompilers

@greytery
Copy link
Author

Thanks, but I've been along that route and hit all sorts of broken dependencies etc.
As it says: "MOST PEOPLE SHOULDN'T BE BUILDING THEIR OWN CROSS-TOOLCHAIN - THEY SHOULD JUST INSTALL A PRE-BUILT ONE LIKE ANY OTHER PACKAGE." (NB: That's their shout not mine).
No - not quite the point. The Instructions found on -
(a) https://github.com/adapteva/epiphany-sdk/wiki/Building-the-SDK
(b) https://github.com/adapteva/epiphany-sdk/wiki/Building%20on%20Linux
are no longer correct.

Building the sdk following the instructions on the wiki WAS working until the last month or so. The sdk files where downloaded along with the epiphany-libs - and previously seemed to build fine. That has been changed, but the wiki instructions no longer reflect that (or work).

@greytery greytery reopened this Jul 15, 2014
@bcxcube
Copy link
Contributor

bcxcube commented Jul 15, 2014

Can you please send me the build log file and any output that describes the problems you are running into?

Do you have an arm cross toolchain installed on your build host?

@greytery
Copy link
Author

No longer have logfiles after I cleaned up the 'mess' I made on Debian. I actually pointed at some Ubuntu repositories - not the Debian/Emdebian ones - so unsurprising I got errors = My Error.

No longer have any cross toolchain built. I amused myself by building the sdk on as many platforms as I could while waiting for parallela delivery. That is: on Cygwin, Ubuntu (in Virtualbox), Mint Linux - all disposable environments. All appeared to build without error - using the previous Wiki instructions - but without parallela to run on, I could not test properly. After delivery, decided to start from scratch on clean systems. Found the Wiki instructions have changed. Can no longer build.

Will attempt to investigate Emdebian pages - but am already concerned by the number of dire 'There be Dragons' warnings. Been burned before .... :-)

@bcxcube
Copy link
Contributor

bcxcube commented Jul 17, 2014

Once you have the toolchain installed you'll need to check the toolchain prefix. If it isn't "arm-linux-gnueabihf-" then you will need to edit the install-sdk.sh script in the SDK source root and replace "arm-linux-gnueabihf-" to the appropriate prefix for your toolchain.

FYI, this will be changing in future releases; the build scripts will allow you to override the default toolchain prefix. Also, there is a script named build-epiphany-sdk.sh which will do all of the steps described on the "Building the SDK" Wiki. To use it:

cd [your working directory]
git clone https://github.com/adapteva/epiphany-sdk.git sdk
sdk/build-epiphany-sdk.sh

This will be documented on the Wiki when it is updated for the next release of the SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants