Skip to content
This repository

installation directory #9

Open
micromouseonline opened this Issue July 25, 2011 · 7 comments

2 participants

micromouseonline James Snyder
micromouseonline

Any particular reason why you build this to the users home folder by default? It appears to me that, if I built to a folder like /usr/loca/arm-tools or some such, I could copy the result to my other machines without a lengthy build.

James Snyder
Owner

I believe you should be able to move the built binaries to other locations if you want, though I haven't tried putting them elsewhere. You can also change the prefix during build time, although as it is currently set up it might be simplest to give yourself user permissions in the destination directory.

I'll work on making it easier to do something like make PREFIX=/usr/local/arm-tools in the future, I think since this was requested either on this toolchain or on the avr32 toolchain I maintain.

micromouseonline
James Snyder
Owner

I had believed that the prefix needed to be the same as the installation location but I am not sure now

I don't believe so, however I could be wrong. I do have binaries that are on the site that others have downloaded and I suspect have had success with that were definitely built for my home directory. I've presumed that since I've not had complaints about these that they've worked in other home directories which have different paths.

Today, I have tried a lot but failed to make the installation work on OS X Lion.

Do you mean that a build failed from scratch or something else? I have to confess that although I've got Lion running, I haven't tried a build yet. If you were using XCode 4 before you will definitely need 4.1 since it moves 4.0.x out of the way. I'll give a build a try today and see how things go.

micromouseonline
James Snyder
Owner

Looks like this might be a common issue with llvm-gcc that has potentially been fixed in a later version than what is shipping. I've created a separate issue.

micromouseonline
James Snyder
Owner

I believe I've got a workaround for now that should work that involves using clang to build everything except for GCC. I haven't tried it from a completely clean start, but what I now have on the readme file, should get everything built. The only complication was GDB which has something that clang (rightfully) blew up on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.