On Tue, Jun 8, 2010 at 6:12 PM, <baseband-devel-request@lists.osmocom.org> wrote:

Send baseband-devel mailing list submissions to
baseband-devel@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@lists.osmocom.org

You can reach the person managing the list at
baseband-devel-owner@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@codelabs.ch>
To: Zaki Ud Din <fyproject14@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@gmail.com>
To: baseband-devel@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@fokus.fraunhofer.de>
To: "Zaki Ud Din" <fyproject14@gmail.com>, <baseband-devel@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@lists.osmocom.org [mailto:baseband-devel-bounces@lists.osmocom.org] Im Auftrag von Zaki Ud Din
Gesendet: Sonntag, 6. Juni 2010 22:21
An: baseband-devel@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@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@gmail.com>
To: baseband-devel@lists.osmocom.org, Holger Freyther <zecke@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@selfish.org>
To: baseband-devel@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@lists.osmocom.org
https://lists.osmocom.org/mailman/listinfo/baseband-devel