3 Feb
2011
3 Feb
'11
2:22 p.m.
Make sure of the following:
1. Edit ~/.bashrc and put
export PATH=$PATH:<YOURPATH>/install/bin , where "yourpath" is your full
path to where
arm-elf-gcc is located
2. restart your computer (sometimes it helps)
3. run the "make" under the same user that has the above path (no sudo make
!!!)
5:38 p.m.
New subject: in deep trouble
On Thu, Feb 3, 2011 at 3:22 PM, Bogdan Alecu <b.alecu(a)yahoo.com> wrote:
Make sure of the following:
1. Edit ~/.bashrc and put
export PATH=$PATH:<YOURPATH>/install/bin , where "yourpath" is your full
path to where
arm-elf-gcc is located
2. restart your computer (sometimes it helps)
3. run the "make" under the same user that has the above path (no sudo make
!!!)
Bogdan,
evidently there is a good reason why Wolfram's answer is as it is.
Evidently there is a http://bb.osmocom.org/trac/wiki/GettingStarted,
where evidently is written :
If your GCC binary that produces ARM code is not called arm-elf-gcc
you will need to invoke the following statement and provide the
basename of the toolchain with the ending -.
$ cd src
$ make -e CROSS_TOOL_PREFIX=arm-OTHER_NAME-
Evidently the person who posts questions like this did not read
Getting Started page (which is the most sane thing to do in the
beginning), nor understood this (or any other, if you want) mailing
list netiquette (which is by the way underlined here :
http://bb.osmocom.org/trac/wiki/PreliminaryRequirements).
I do not get how someone can miss this sentences from the OsmocomBB home page :
To get started, checkout the PreliminaryRequirements and then GettingStarted
unless he/she really do not care.
I strongly opt for Wolfram's kind of response on a questions like this
(at least it forces people read what they should have red in the first
place). Otherwise September will never end.
BR,
Drasko
5315
days inactive
5315
days old
baseband-devel@lists.osmocom.org
3 comments
4 participants
participants (4)
-
Bogdan Alecu -
Drasko DRASKOVIC -
Peter Stuge -
Wolfram Sang