> I was refering to "layer23" the quick & dirty test app if you want to
> play with the layer1.
oops. sorry, but anyway i need to improve the IMM.ASS. check against
timestamp.
i will test all the new features soon and also check the time stamps if
they match.
Hello,
I want to use the power measurements from the l1test in the phone. Therefore I modified the program so only the PM is done and additional some averaging and so on.
Finally the information should be sent to an microcontroller over UART. There is the problem: I don't know how to use this HDLC sercomm stuff because I don't have time to understand AND implement it for my thesis in the µc-part. I need a quick dirty hack to deactivate this HDLC. I don't find it in code and tried some hours.
I tried "uart_putchar_wait()" and hterm shows me that the bytes are sent with a lot other stuff.
What is the easiest way working for me?
Thanks a lot.
Marco
Hello,
I am just writing this email to thank everyone who helped me with all the
trouble I had while Osmocom. Though I didn't succeed in my objective but it
was just a part of my project that I started quite late and was always
fighting against time to complete it.
Thank you :),
Zaki.
Hi all,
can anybody point be to the SIM card driver sources ?
I looked at src/target/firmware/calypso but did not find it...
Is there some other sources that you know for SCI (Smart Card
Interface) that I can look at ?
Best regards,
Drasko
---------- Forwarded message ----------
From: Wolfgang Draxinger <wdraxinger.maillist(a)draxit.de>
Date: Wed, Jun 9, 2010 at 10:08 AM
Subject: Re: SIM card driver
To: hardware(a)lists.openmoko.org, Al Johnson <openmoko(a)mazikeen.demon.co.uk>
On Wed, 9 Jun 2010 00:04:07 +0200
Drasko DRASKOVIC <drasko.draskovic(a)gmail.com> wrote:
> Very uncool :(.
>
> I need to write a driver for ARM PrimeCell Smart Card Interface PL131
> in order to init/read/write SIM card for 4G mobile device. Does
> anybody knows where I can get hold of some implementation of (any) SIM
> interface driver ?
>
> Thanks and BR,
> Drasko
SIMs, like any other SmartCard communicate over an interface very
similar to I2C, with the notable difference, that the terminal always
is the "bus" master.
Building your very own SmartCard terminal is very easy. Or you just use
one of the ready to use ones (from Towitoko, Reiner SCT, etc.).
Also have a look in the Open Baseband project
http://bb.osmocom.org/trac/
Which b nature also must deal with SIM cards.
Wolfgang
_______________________________________________
hardware mailing list
hardware(a)lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/hardware
Hello,
Thank you for your reply. I have downloaded the toolchain that I should have
done at the first place. I am not getting those errors any more but I am
stuck at some new ones. I am pasting them below
.................
calypso/libcalypso.a(uart.o):(.ARM.exidx.text.uart_irq_handler_sercomm+0x0):
undefined reference to `__aeabi_unwind_cpp_pr1'
calypso/libcalypso.a(uart.o):(.ARM.exidx.text.uart_init+0x0): undefined
reference to `__aeabi_unwind_cpp_pr0'
lib/libmini.a(console.o):(.ARM.exidx.text.cons_rb_pull+0x0): undefined
reference to `__aeabi_unwind_cpp_pr0'
lib/libmini.a(console.o):(.ARM.exidx.text.__cons_rb_append+0x0): undefined
reference to `__aeabi_unwind_cpp_pr0'
lib/libmini.a(console.o):(.ARM.exidx.text.cons_rb_append+0x0): undefined
reference to `__aeabi_unwind_cpp_pr0'
lib/libmini.a(console.o):(.ARM.exidx.text.cons_puts+0x0): undefined
reference to `__aeabi_unwind_cpp_pr0'
lib/libmini.a(console.o):(.ARM.exidx.text.cons_rb_flush+0x0): more undefined
references to `__aeabi_unwind_cpp_pr0' follow
make[1]: *** [board/compal_e88/hello_world.ramload.elf] Error 1
make[1]: Leaving directory `/home/zaki/osmocom-bb/src/target/firmware'
make: *** [firmware] Error 2
Another thing that I had to ask was that basically my work is at the layer1
and all the c files present in that folder of firmware have got built, the
error that is coming above is in some other folder. Would I be able to load
the layer1 files through osmocon without completing the installation of the
rest of the firmware.
Awaiting your response,
Zaki.
Hi,
I would like to get started with osmocon for openmoko devices.
I have checked out the project and setup the gnuarm but it doesnt seem to
compile.
I am running ubuntu karmic.
Please do help me with the steps of getting it running on this device.
-------------Error--------------
configure error could not find install.sh, or sh-tool
make [shared/libosmocore/build-host/Makefile]
-------------Error--------------
Regards
Saravanan.L
Hello,
I never thought I would become such a popular figure on your mailing lists,
be it for the wrong reasons. I am sorry to have emailed you that question,
but honestly I am new to Ubuntu. I have done quite a lot of programming on
Windows, but this seems to be quite a different world, and that is why I
email you even my seemingly childish questions for you to you, as I am sure
you wont have any trouble solving them although it does takes some seconds
of yours.
Regards,
Zaki.
On Wed, Jun 9, 2010 at 9:47 AM, <baseband-devel-request(a)lists.osmocom.org>wrote:
> Send baseband-devel mailing list submissions to
> baseband-devel(a)lists.osmocom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osmocom.org/mailman/listinfo/baseband-devel
> or, via email, send a message with subject or body 'help' to
> baseband-devel-request(a)lists.osmocom.org
>
> You can reach the person managing the list at
> baseband-devel-owner(a)lists.osmocom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of baseband-devel digest..."
>
> Today's Topics:
>
> 1. Re: Trouble building Osmocom (Sylvain Munaut)
> 2. Re: Trouble building Osmocom (Zaki Ud Din)
> 3. Re: Trouble building Osmocom (Huseyin Turan)
> 4. Re: Trouble building Osmocom (Nordin)
> 5. Re: Trouble building Osmocom (Huseyin Turan)
> 6. Re: Trouble building Osmocom (Nordin)
> 7. Re: Trouble building Osmocom (Nordin)
> 8. Re: Trouble building Osmocom (Sylvain Munaut)
> 9. Re: Trouble building Osmocom (Holger Hans Peter Freyther)
>
>
> ---------- Forwarded message ----------
> From: Sylvain Munaut <246tnt(a)gmail.com>
> To:
> Date: Tue, 8 Jun 2010 15:57:22 +0200
> Subject: Re: Trouble building Osmocom
> Looking at gnuarm.com, it looks like you have a x86_64 toolchain and
> try to run it on i686.
> Honestly I don't want to be mean but if you can't see what's wrong
> with that, osmocom-bb might not be for you quite just yet.
>
>
>
>
> ---------- Forwarded message ----------
> From: Zaki Ud Din <fyproject14(a)gmail.com>
> To: baseband-devel(a)lists.osmocom.org
> Date: Tue, 8 Jun 2010 19:00:20 +0500
> Subject: Re: Trouble building Osmocom
> Hello,
>
> Thank you for your reply. I am really sorry I did not get your point in the
> mail where you asked me to perform the different checks. Though I have
> written those commands and have pasted their output below.
>
>
> zaki@zaki-desktop:~/gnuarm-4.0.2/bin$ file ./arm-elf-gcc
> ./arm-elf-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked (uses shared libs), for GNU/Linux 2.4.1, stripped
> zaki@zaki-desktop:~/gnuarm-4.0.2/bin$ uname -a
> Linux zaki-desktop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC
> 2009 i686 GNU/Linux
>
> Awaiting your response,
>
> Zaki.
>
>
> ---------- Forwarded message ----------
> From: Huseyin Turan <huseyinturan(a)gmail.com>
> To: baseband-devel(a)lists.osmocom.org
> Date: Tue, 8 Jun 2010 16:51:06 +0300
> Subject: Re: Trouble building Osmocom
> Sorry;
>
> file ./arm-elf-gcc
> ./arm-elf-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked (uses shared libs), for GNU/Linux 2.4.1, stripped
>
>
>
> ---------- Forwarded message ----------
> From: Nordin <bouchtaoui(a)gmail.com>
> To: baseband-devel(a)lists.osmocom.org
> Date: Tue, 08 Jun 2010 16:26:08 +0200
> Subject: Re: Trouble building Osmocom
> On 8-6-2010 15:57, Sylvain Munaut wrote:
>
>> Honestly I don't want to be mean but if you can't see what's wrong
>> with that, osmocom-bb might not be for you quite just yet.
>>
>>
>
> Maybe he's good in programming embedded stuff, this has purely to do with
> Linux specific builds and nothing to do with coding/decoding gsm stuff.
> By the way, he can always learn...
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Huseyin Turan <huseyinturan(a)gmail.com>
> To: baseband-devel(a)lists.osmocom.org
> Date: Tue, 8 Jun 2010 18:16:50 +0300
> Subject: Re: Trouble building Osmocom
> Thank you very much.
>
> I have succeded to compile. I will try to deploy on C118.
>
>
> ---------- Forwarded message ----------
> From: Nordin <bouchtaoui(a)gmail.com>
> To: Sylvain Munaut <246tnt(a)gmail.com>
> Date: Tue, 08 Jun 2010 17:24:35 +0200
> Subject: Re: Trouble building Osmocom
> Silvain,
>
> Yes I agree with you, but I just want to note that we have to encourage
> beginners to keep trying and learning.
> Especially when one comes from the Windows world like me, where everything
> builds magically in Visual Studio (debugging is a joy in there ;-)
> Never programmed in Linux, never used git, gdb, vim, etc... and now, I
> begin to rock a little bit, thnx to OpenBSC and you guys ;-)
>
>
>
> On 8-6-2010 17:07, Sylvain Munaut wrote:
>
>> Maybe he's good in programming embedded stuff, this has purely to do with
>>> Linux specific builds and nothing to do with coding/decoding gsm stuff.
>>>
>>>
>> I never meant otherwise in my previous message. But basic knowledge /
>> problem solving of the build system is a requirement IMHO, especially
>> in this project (that includes both host and target code with even
>> some shared code between the two).
>>
>> I also looked up his history on the various mailing lists before
>> posting this and this is not the first build problem with GSM related
>> projects so I would expect him to learn from previous experience.
>>
>>
>> Also, when I see a message with :
>>
>> ----
>> zaki@zaki-desktop:~/gnuarm-4.0.2/bin$ file ./arm-elf-gcc
>> ./arm-elf-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
>> dynamically linked (uses shared libs), for GNU/Linux 2.4.1, stripped
>> zaki@zaki-desktop:~/gnuarm-4.0.2/bin$ uname -a
>> Linux zaki-desktop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17
>> 01:57:59 UTC 2009 i686 GNU/Linux
>> ----
>>
>> And he still asks what's wrong ? An embedded programmer that doesn't
>> know he can't just run binaries from one architecture onto another
>> architecture ...
>>
>>
>>
>>
>>
>>> By the way, he can always learn...
>>>
>>>
>> I know, that's why there is a "quite just yet" at the end. That's
>> exactly what I implied: that he learns that first and then come back.
>>
>>
>> Cheers,
>>
>> Sylvain
>>
>>
>>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Nordin <bouchtaoui(a)gmail.com>
> To: baseband-devel(a)lists.osmocom.org
> Date: Tue, 08 Jun 2010 17:27:53 +0200
> Subject: Re: Trouble building Osmocom
> Congratulations! :)
>
>
>
> On 8-6-2010 17:16, Huseyin Turan wrote:
>
>> Thank you very much.
>>
>> I have succeded to compile. I will try to deploy on C118.
>>
>>
>>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Sylvain Munaut <246tnt(a)gmail.com>
> To: Nordin <bouchtaoui(a)gmail.com>
> Date: Tue, 8 Jun 2010 17:07:42 +0200
> Subject: Re: Trouble building Osmocom
> > Maybe he's good in programming embedded stuff, this has purely to do with
> > Linux specific builds and nothing to do with coding/decoding gsm stuff.
>
> I never meant otherwise in my previous message. But basic knowledge /
> problem solving of the build system is a requirement IMHO, especially
> in this project (that includes both host and target code with even
> some shared code between the two).
>
> I also looked up his history on the various mailing lists before
> posting this and this is not the first build problem with GSM related
> projects so I would expect him to learn from previous experience.
>
>
> Also, when I see a message with :
>
> ----
> zaki@zaki-desktop:~/gnuarm-4.0.2/bin$ file ./arm-elf-gcc
> ./arm-elf-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked (uses shared libs), for GNU/Linux 2.4.1, stripped
> zaki@zaki-desktop:~/gnuarm-4.0.2/bin$ uname -a
> Linux zaki-desktop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17
> 01:57:59 UTC 2009 i686 GNU/Linux
> ----
>
> And he still asks what's wrong ? An embedded programmer that doesn't
> know he can't just run binaries from one architecture onto another
> architecture ...
>
>
>
> > By the way, he can always learn...
>
> I know, that's why there is a "quite just yet" at the end. That's
> exactly what I implied: that he learns that first and then come back.
>
>
> Cheers,
>
> Sylvain
>
>
>
>
> ---------- Forwarded message ----------
> From: Holger Hans Peter Freyther <holger(a)freyther.de>
> To: baseband-devel(a)lists.osmocom.org
> Date: Wed, 09 Jun 2010 12:31:46 +0800
> Subject: Re: Trouble building Osmocom
> On 06/08/2010 11:24 PM, Nordin wrote:
> > Silvain,
> >
> > Yes I agree with you, but I just want to note that we have to encourage
> > beginners to keep trying and learning.
> > Especially when one comes from the Windows world like me, where
> > everything builds magically in Visual Studio (debugging is a joy in
> > there ;-)
> > Never programmed in Linux, never used git, gdb, vim, etc... and now, I
> > begin to rock a little bit, thnx to OpenBSC and you guys ;-)
>
> Hi Nordin,
>
> I wouldn't have the skills I have now if it wouldn't be due to others
> help. And of course I know file and uname and it is new to others. The
> biggest problem I have is judging is someone is just lazy, or if there
> is someone who is slow to start but eager to learn.
>
> how would you figure that out?
>
> z.
>
> PS: Would you be willing to help me to go through the documentation and
> provide some more getting started information? At least two have
> downloaded a wrong toolchain, I am pretty sure this will happen again.
>
>
>
> _______________________________________________
> baseband-devel mailing list
> baseband-devel(a)lists.osmocom.org
> https://lists.osmocom.org/mailman/listinfo/baseband-devel
>
>
Hello,
Thank you for your reply. I am really sorry I did not get your point in the
mail where you asked me to perform the different checks. Though I have
written those commands and have pasted their output below.
zaki@zaki-desktop:~/gnuarm-4.0.2/bin$ file ./arm-elf-gcc
./arm-elf-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.4.1, stripped
zaki@zaki-desktop:~/gnuarm-4.0.2/bin$ uname -a
Linux zaki-desktop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC
2009 i686 GNU/Linux
Awaiting your response,
Zaki.
Hello,
Thank you very much for your reply. When i give the path to arm-elf-gcc
"export PATH=$PATH:/home/zaki/gnuarm-4.0.2/bin/" , and run "make firmware",
I get errors. I have pasted some of the errors that i get in config.log
below and have also attached that file.
configure:2559: checking for arm-elf-linux-gcc
configure:2586: result: arm-elf-gcc
configure:2858: checking for C compiler version
configure:2866: arm-elf-gcc --version >&5
../configure: line 2868: /home/zaki/gnuarm-4.0.2/bin/arm-elf-gcc: cannot
execute binary file
configure:2870: $? = 126
configure:2877: arm-elf-gcc -v >&5
../configure: line 2879: /home/zaki/gnuarm-4.0.2/bin/arm-elf-gcc: cannot
execute binary file
configure:2881: $? = 126
configure:2888: arm-elf-gcc -V >&5
../configure: line 2890: /home/zaki/gnuarm-4.0.2/bin/arm-elf-gcc: cannot
execute binary file
configure:2892: $? = 126
configure:2915: checking for C compiler default output file name
configure:2937: arm-elf-gcc -Os -ffunction-sections
-I../../../../target/firmware/include conftest.c >&5
../configure: line 2939: /home/zaki/gnuarm-4.0.2/bin/arm-elf-gcc: cannot
execute binary file
configure:2941: $? = 126
configure:2979: result:
configure: failed program was:
Awaiting your response,
Zaki.
On Tue, Jun 8, 2010 at 6:12 PM, <baseband-devel-request(a)lists.osmocom.org>wrote:
> Send baseband-devel mailing list submissions to
> baseband-devel(a)lists.osmocom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osmocom.org/mailman/listinfo/baseband-devel
> or, via email, send a message with subject or body 'help' to
> baseband-devel-request(a)lists.osmocom.org
>
> You can reach the person managing the list at
> baseband-devel-owner(a)lists.osmocom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of baseband-devel digest..."
>
> Today's Topics:
>
> 1. Re: Trouble building Osmocom (Adrian-Ken Rueegsegger)
> 2. Re: Trouble building Osmocom (Sylvain Munaut)
> 3. AW: Trouble building Osmocom (Riemer, Bjoern)
> 4. Re: Trouble building Osmocom (Holger Freyther)
> 5. Trouble building Osmocom (Zaki Ud Din)
> 6. Re: Trouble building Osmocom (Holger Freyther)
>
>
> ---------- Forwarded message ----------
> From: Adrian-Ken Rueegsegger <ken(a)codelabs.ch>
> To: Zaki Ud Din <fyproject14(a)gmail.com>
> Date: Tue, 08 Jun 2010 12:44:56 +0200
> Subject: Re: Trouble building Osmocom
> Hi,
>
> Zaki Ud Din schrieb:
> > Hello,
> >
> > Thank you very much for your reply. No my config.log file seems to be
> > different. I am pasting a portion of config.log file below and am also
> > attaching the complete file with this email.
>
> [snip]
>
> > configure:2866: arm-elf-gcc --version >&5
> > ../configure: line 2868: arm-elf-gcc: command not found
> > configure:2870: $? = 127
> > configure:2877: arm-elf-gcc -v >&5
> > ../configure: line 2879: arm-elf-gcc: command not found
> > configure:2881: $? = 127
> > configure:2888: arm-elf-gcc -V >&5
> > ../configure: line 2890: arm-elf-gcc: command not found
> > configure:2892: $? = 127
> > configure:2915: checking for C compiler default output file name
> > configure:2937: arm-elf-gcc -Os -ffunction-sections
> > -I../../../../target/firmware/include conftest.c >&5
> > ../configure: line 2939: arm-elf-gcc: command not found
>
> It does not find the toolchain/cross-compiler. Where did you
> install/unpack the toolchain? Please check that it is really in
> "/gnuarm-4.0.2/arm-elf/bin". Otherwise you have to export the proper path.
>
> -Adrian
>
>
>
>
> ---------- Forwarded message ----------
> From: Sylvain Munaut <246tnt(a)gmail.com>
> To: baseband-devel(a)lists.osmocom.org
> Date: Tue, 8 Jun 2010 12:43:19 +0200
> Subject: Re: Trouble building Osmocom
> This seems pretty clear :
>
> > ../configure: line 2939: arm-elf-gcc: command not found
>
> Make sure you have a good ARM toolchain installed ... (look it up on
> google, plenty of doc on how to install one).
>
> Sylvain
>
>
>
>
> ---------- Forwarded message ----------
> From: "Riemer, Bjoern" <bjoern.riemer(a)fokus.fraunhofer.de>
> To: "Zaki Ud Din" <fyproject14(a)gmail.com>, <
> baseband-devel(a)lists.osmocom.org>
> Date: Tue, 8 Jun 2010 13:07:30 +0200
> Subject: AW: Trouble building Osmocom
>
> Hi
>
>
>
> You say that you unpacked the gcc compiler to your home directory and then
> set you path to PATH=/gnuarm-4.0.2/arm-elf/bin:$PATH ..
>
> Unless your home directory is set to / the path to the gcc compiler is
> wrong.
>
>
>
> bjoern
>
>
>
> *Von:* baseband-devel-bounces(a)lists.osmocom.org [mailto:
> baseband-devel-bounces(a)lists.osmocom.org] *Im Auftrag von *Zaki Ud Din
> *Gesendet:* Sonntag, 6. Juni 2010 22:21
> *An:* baseband-devel(a)lists.osmocom.org
> *Betreff:* Trouble building Osmocom
>
>
>
> Hello,
>
> I have been trying to build osmocom but have been getting errors in doing
> so.
>
> Firstly, I downloaded the following file,"* binutils-2.16.1,
> gcc-4.0.2-c-c++, newlib-1.14.0, insight-6.4, TAR BZ2 [65.5MB]*" under
> GCC-4.0 toolchain from www.gnuarm.com and extracted this to my home
> folder.
>
> Secondly, I gave the following path "export PATH=/gnuarm-4.0.2/arm-elf/
>
> bin:$PATH" in terminal window. Afterwards when I entered "make" under
> "/osmosom-bb/src", I got the following errors
>
>
> zaki@zaki-desktop:~/osmocom-bb/src$ make
>
> cd shared/libosmocore/build-host && make
> make[1]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host'
> make all-recursive
> make[2]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host'
> Making all in include
> make[3]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include'
> Making all in osmocore
> make[4]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
> Making all in protocol
> make[5]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol'
> make[5]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
> make[5]: Nothing to be done for `all-am'.
> make[5]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
> make[4]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
> make[4]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include'
> make[3]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include'
> Making all in src
> make[3]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/src'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/src'
> Making all in tests
> make[3]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests'
> Making all in timer
> make[4]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests/timer'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests/timer'
> Making all in sms
> make[4]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests/sms'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests/sms'
> make[4]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests'
> make[3]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests'
> make[3]: Entering directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host'
> make[3]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host'
> make[2]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host'
> make[1]: Leaving directory
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host'
> cd shared/libosmocore/build-target && ../configure \
> --host=arm-elf-linux --disable-shared --disable-talloc
> --disable-tests \
> CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections
> -I../../../../target/firmware/include"
> configure: WARNING: If you wanted to set the --build type, don't use
> --host.
> If a cross compiler is detected then cross compile mode will be used.
>
>
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
>
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for arm-elf-linux-strip... no
> checking for strip... strip
> checking whether make sets $(MAKE)... (cached) yes
>
>
> checking for arm-elf-linux-gcc... arm-elf-gcc
> checking for C compiler default output file name...
> configure: error: in
> `/home/zaki/osmocom-bb/src/shared/libosmocore/build-target':
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
> make: *** [shared/libosmocore/build-target/Makefile] Error 77
>
> I shall be grateful to you if you could help me on this.
>
> Awaiting your Response,
>
> Zaki.
>
>
> ---------- Forwarded message ----------
> From: Holger Freyther <zecke(a)selfish.org>
> To:
> Date: Tue, 08 Jun 2010 20:05:45 +0800
> Subject: Re: Trouble building Osmocom
> On 06/08/2010 07:59 PM, Zaki Ud Din wrote:
> > Hello,
>
> > I did export the path using the following line "export
> > PATH=$PATH:/home/zaki/gnuarm-
> > 4.0.2/arm-elf/bin/ " and afterwards I typed "make firmware" and then got
> > the errors I told you.
> >
> > Awaiting your response,
>
> Well,
> it claims to not find arm-elf-gcc. Have you considered checking that
> this application exists? e.g. does which arm-elf-gcc lead to anything?
>
>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Zaki Ud Din <fyproject14(a)gmail.com>
> To: baseband-devel(a)lists.osmocom.org, Holger Freyther <zecke(a)selfish.org>
> Date: Tue, 8 Jun 2010 16:59:23 +0500
> Subject: Trouble building Osmocom
> Hello,
>
> Thank you very much for your reply.
>
> I am using ,"* binutils-2.16.1, gcc-4.0.2-c-c++, newlib-1.14.0,
> insight-6.4, TAR BZ2 [65.5MB]*" under GCC-4.0 toolchain from
> www.gnuarm.com. I then extracted to the folder named "Zaki".
>
> I did export the path using the following line "export
> PATH=$PATH:/home/zaki/gnuarm-
> 4.0.2/arm-elf/bin/ " and afterwards I typed "make firmware" and then got
> the errors I told you.
>
> Awaiting your response,
>
> Zaki.
>
> ---------- Forwarded message ----------
> From: Holger Freyther <zecke(a)selfish.org>
> To: baseband-devel(a)lists.osmocom.org
> Date: Tue, 08 Jun 2010 21:12:05 +0800
> Subject: Re: Trouble building Osmocom
> On 06/08/2010 09:01 PM, Huseyin Turan wrote:
>
> > checking for gcc... gcc
> > checking for C compiler default output file name...
> > configure: error: in
> > `/home/name1/osmocom/osmocom-bb/src/shared/libosmocore/build-host':
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details.
>
> Looking at the log file is always a good idea. It might have an eye
> opening effect....
>
>
> >
> > That is; in gnuarm-4.0.2/arm-elf/bin there are executables like
> > gcc,g++,etc. which can be executed.
> > in gnuarm-4.0.2/bin there are executables like
> > arm-elf-gcc,arm-elf-g++,etc. which can not be executed.
> >
> > Which path is true?
>
> You want to use your normal gcc and such, so putting
> gnuarm-4.0.2/arm-elf/bin in your path is not that clever. What is the
> issue with arm-elf-gcc? What happens when you try to execute it?
>
>
>
>
> _______________________________________________
> baseband-devel mailing list
> baseband-devel(a)lists.osmocom.org
> https://lists.osmocom.org/mailman/listinfo/baseband-devel
>
>
