5 Jan
2011
5 Jan
'11
5:19 p.m.
Hi,
I use Ubuntu 9.10, when i try to Compile Osmocom, i get this:
root@r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src
root@r00t-laptop:~/install/osmocom-bb/src# make
cd shared/libosmocore/build-target && ../configure \
--host=arm-elf-linux --disable-vty --enable-panic-infloop \
--disable-shared --disable-talloc --disable-tests \
CC="/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc" CFLAGS="-Os
-ffunction-sections -I/home/r00t/install/osmocom-bb/src/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 arm-elf-linux-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for arm-elf-linux-gcc... /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc accepts -g... yes
checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option to accept ISO C89...
none needed
checking for style of include used by make... GNU
checking dependency style of /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc... gcc3
checking build system type... i686-pc-linux-gnulibc1
checking host system type... arm-elf-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc...
/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld
checking if the linker (/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... no
checking for arm-elf-linux-dumpbin... no
checking for arm-elf-linux-link... no
checking for dumpbin... no
checking for link... link -dump -symbols
configure: WARNING: using cross tools not prefixed with host triplet
checking the name lister (link -dump -symbols) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 805306365
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld option to reload object
files... -r
checking for arm-elf-linux-objdump... no
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for arm-elf-linux-ar... no
checking for ar... ar
checking for arm-elf-linux-strip... strip
checking for arm-elf-linux-ranlib... no
checking for ranlib... ranlib
checking command to parse link -dump -symbols output from
/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc object... failed
checking how to run the C preprocessor... /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc
-E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... no
checking for inttypes.h... no
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... no
checking for objdir... .libs
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -fno-rtti
-fno-exceptions... no
checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option to produce PIC...
-fPIC -DPIC
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc PIC flag -fPIC -DPIC works...
yes
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc static flag -static works...
yes
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -c -o file.o... yes
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -c -o file.o...
(cached) yes
checking whether the /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc linker
(/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking execinfo.h usability... no
checking execinfo.h presence... no
checking for execinfo.h... no
checking sys/select.h usability... no
checking sys/select.h presence... no
checking for sys/select.h... no
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports
-fvisibility=hidden... no
configure: creating ./config.status
config.status: creating libosmocore.pc
config.status: creating libosmocodec.pc
config.status: creating libosmovty.pc
config.status: creating include/osmocom/Makefile
config.status: creating include/osmocom/vty/Makefile
config.status: creating include/osmocom/codec/Makefile
config.status: creating include/osmocom/crypt/Makefile
config.status: creating include/osmocore/Makefile
config.status: creating include/osmocore/protocol/Makefile
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating src/vty/Makefile
config.status: creating src/codec/Makefile
config.status: creating tests/Makefile
config.status: creating tests/timer/Makefile
config.status: creating tests/sms/Makefile
config.status: creating tests/msgfile/Makefile
config.status: creating tests/ussd/Makefile
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
cd shared/libosmocore/build-target && make
make[1]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target'
make all-recursive
make[2]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target'
Making all in include
make[3]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in osmocom
make[4]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
Making all in codec
make[5]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
make[5]: Für das Ziel »all« ist nichts zu tun.
make[5]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
Making all in crypt
make[5]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
make[5]: Für das Ziel »all« ist nichts zu tun.
make[5]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
make[5]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
make[5]: Für das Ziel »all-am« ist nichts zu tun.
make[5]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
make[4]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
Making all in osmocore
make[4]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
Making all in protocol
make[5]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
make[5]: Für das Ziel »all« ist nichts zu tun.
make[5]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
make[5]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[5]: Für das Ziel »all-am« ist nichts zu tun.
make[5]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[4]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[4]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include'
make[4]: Für das Ziel »all-am« ist nichts zu tun.
make[4]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include'
make[3]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in src
make[3]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src'
Making all in .
make[4]: Betrete Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src'
CC rate_ctr.lo
../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory
make[4]: *** [rate_ctr.lo] Fehler 1
make[4]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src'
make[3]: *** [all-recursive] Fehler 1
make[3]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src'
make[2]: *** [all-recursive] Fehler 1
make[2]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis
'/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target'
make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Fehler 2
root@r00t-laptop:~/install/osmocom-bb/src#
5 Jan
5 Jan
6:01 p.m.
../../src/rate_ctr.c:24:22: inttypes.h: No such file
or directory
Just comment the line that includes the inttypes.h, and you are good
to go.
Cheers,
sergio
On Jan 5, 2011, at 5:19 PM, Sebastian --- wrote:
> Hi,
>
> I use Ubuntu 9.10, when i try to Compile Osmocom, i get this:
>
> root@r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src
> root@r00t-laptop:~/install/osmocom-bb/src# make
> cd shared/libosmocore/build-target && ../configure \
> --host=arm-elf-linux --disable-vty --enable-panic-
> infloop \
> --disable-shared --disable-talloc --disable-tests \
> CC="/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc"
> CFLAGS="-Os -ffunction-sections -I/home/r00t/install/osmocom-bb/src/
> 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 arm-elf-linux-strip... no
> checking for strip... strip
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make sets $(MAKE)... (cached) yes
> checking for arm-elf-linux-gcc... /home/r00t/install/gnuarm-3.4.3/
> bin/arm-elf-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... yes
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc
> accepts -g... yes
> checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option
> to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of /home/r00t/install/gnuarm-3.4.3/bin/arm-
> elf-gcc... gcc3
> checking build system type... i686-pc-linux-gnulibc1
> checking host system type... arm-elf-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-
> gcc... /home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld
> checking if the linker (/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/
> ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... no
> checking for arm-elf-linux-dumpbin... no
> checking for arm-elf-linux-link... no
> checking for dumpbin... no
> checking for link... link -dump -symbols
> configure: WARNING: using cross tools not prefixed with host triplet
> checking the name lister (link -dump -symbols) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 805306365
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld option
> to reload object files... -r
> checking for arm-elf-linux-objdump... no
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for arm-elf-linux-ar... no
> checking for ar... ar
> checking for arm-elf-linux-strip... strip
> checking for arm-elf-linux-ranlib... no
> checking for ranlib... ranlib
> checking command to parse link -dump -symbols output from /home/r00t/
> install/gnuarm-3.4.3/bin/arm-elf-gcc object... failed
> checking how to run the C preprocessor... /home/r00t/install/
> gnuarm-3.4.3/bin/arm-elf-gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... no
> checking for inttypes.h... no
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... no
> checking for objdir... .libs
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports
> -fno-rtti -fno-exceptions... no
> checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option
> to produce PIC... -fPIC -DPIC
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc PIC flag
> -fPIC -DPIC works... yes
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc static
> flag -static works... yes
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports
> -c -o file.o... yes
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports
> -c -o file.o... (cached) yes
> checking whether the /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc
> linker (/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld) supports
> shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
> checking for ANSI C header files... (cached) yes
> checking execinfo.h usability... no
> checking execinfo.h presence... no
> checking for execinfo.h... no
> checking sys/select.h usability... no
> checking sys/select.h presence... no
> checking for sys/select.h... no
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports
> -fvisibility=hidden... no
> configure: creating ./config.status
> config.status: creating libosmocore.pc
> config.status: creating libosmocodec.pc
> config.status: creating libosmovty.pc
> config.status: creating include/osmocom/Makefile
> config.status: creating include/osmocom/vty/Makefile
> config.status: creating include/osmocom/codec/Makefile
> config.status: creating include/osmocom/crypt/Makefile
> config.status: creating include/osmocore/Makefile
> config.status: creating include/osmocore/protocol/Makefile
> config.status: creating include/Makefile
> config.status: creating src/Makefile
> config.status: creating src/vty/Makefile
> config.status: creating src/codec/Makefile
> config.status: creating tests/Makefile
> config.status: creating tests/timer/Makefile
> config.status: creating tests/sms/Makefile
> config.status: creating tests/msgfile/Makefile
> config.status: creating tests/ussd/Makefile
> config.status: creating Makefile
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing depfiles commands
> config.status: executing libtool commands
> cd shared/libosmocore/build-target && make
> make[1]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target'
> make all-recursive
> make[2]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target'
> Making all in include
> make[3]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include'
> Making all in osmocom
> make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocom'
> Making all in codec
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocom/codec'
> make[5]: Für das Ziel »all« ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocom/codec'
> Making all in crypt
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocom/crypt'
> make[5]: Für das Ziel »all« ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocom/crypt'
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocom'
> make[5]: Für das Ziel »all-am« ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocom'
> make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocom'
> Making all in osmocore
> make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocore'
> Making all in protocol
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocore/protocol'
> make[5]: Für das Ziel »all« ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocore/protocol'
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocore'
> make[5]: Für das Ziel »all-am« ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocore'
> make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include/osmocore'
> make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include'
> make[4]: Für das Ziel »all-am« ist nichts zu tun.
> make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include'
> make[3]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/include'
> Making all in src
> make[3]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/src'
> Making all in .
> make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/src'
> CC rate_ctr.lo
../../src/rate_ctr.c:24:22: inttypes.h: No such file
or directory
> make[4]: *** [rate_ctr.lo] Fehler 1
> make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/src'
> make[3]: *** [all-recursive] Fehler 1
> make[3]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target/src'
> make[2]: *** [all-recursive] Fehler 1
> make[2]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target'
> make[1]: *** [all] Fehler 2
> make[1]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/
> shared/libosmocore/build-target'
> make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a]
> Fehler 2
> root@r00t-laptop:~/install/osmocom-bb/src#
>
6:04 p.m.
Hi Sebastian,
On Wed, Jan 5, 2011 at 18:19, Sebastian --- <seppel18(a)hotmail.com> wrote:
Hi,
I use Ubuntu 9.10, when i try to Compile Osmocom, i get this:
snip<
../../src/rate_ctr.c:24:22: inttypes.h: No such file
or directory
What works for me, is to comment out the include of inttypes.h
from src/shared/libosmocore/src/rate_ctr.c
and the include_next of stdint.h in src/target/firmware/include/stdint.h.
Regards,
Hessel
6:05 p.m.
../../src/rate_ctr.c:24:22: inttypes.h: No such file
or directory
Just comment/delete that include as is already fixed on upstream
libosmocom
http://ur1.ca/2r4l9
6:15 p.m.
Sebastian --- wrote:
I use Ubuntu 9.10, when i try to Compile Osmocom, i
get this:
root@r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src
root@r00t-laptop:~/install/osmocom-bb/src# make
cd shared/libosmocore/build-target && ../configure \
--host=arm-elf-linux --disable-vty --enable-panic-infloop \
--disable-shared --disable-talloc --disable-tests \
CC="/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc" CFLAGS="-Os
-ffunction-sections -I/home/r00t/install/osmocom-bb/src/target/firmware/include"
Please don't do this. First, work as a regular user. You could use
r00t. Then, your --host is wrong. Also, please just set your path to
include /home/r00t/install/gnuarm-3.4.3/bin in the path. And I'm not
sure that you need the target/firmware/include, I'd expect that to be
added where needed automatically.
./configure --host=arm-elf --disable-vty --enable-panic-infloop \
--disable-shared --disable-talloc --disable-tests
should be enough. Run as r00t, not root, with PATH set correctly.
Look for cross-compile tutorials for microcontroller projects on the
interwebs to learn more about how to work with projects like these.
//Peter
8:07 p.m.
Peter,
On 05/01/11 18:15, Peter Stuge wrote:
Sebastian --- wrote:
That configure-line is already make-output ;)
The other points are very valid, of course.
All the best,
Wolfram
I use Ubuntu 9.10, when i try to Compile Osmocom,
i get this:
root@r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src
root@r00t-laptop:~/install/osmocom-bb/src# make
cd shared/libosmocore/build-target && ../configure \
--host=arm-elf-linux --disable-vty --enable-panic-infloop \
--disable-shared --disable-talloc --disable-tests \
CC="/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc" CFLAGS="-Os
-ffunction-sections -I/home/r00t/install/osmocom-bb/src/target/firmware/include"
Please don't do this. First, work as a regular user. You could use
r00t. Then, your --host is wrong. Also, please just set your path to
include /home/r00t/install/gnuarm-3.4.3/bin in the path. And I'm not
sure that you need the target/firmware/include, I'd expect that to be
added where needed automatically. 
3 Oct
3 Oct
7:35 a.m.
New subject: Make Errors
I'm installing osmocombb on Ubuntu13.04,
I've already set the path for arm-elf-gcc...
but I try this command..
$ sudo make
I get these errors...
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:
Assembler messages:
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:32:
Error: no such instruction: `eor %edx,%ecx,%ecx,ror'
make[4]: *** [gsmtap_util.lo] Error 1
make[4]: Leaving directory
`/home/shahzad/arm/osmocom-bb/src/shared/libosmocore/build-target/src'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/home/shahzad/arm/osmocom-bb/src/shared/libosmocore/build-target/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/shahzad/arm/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/shahzad/arm/osmocom-bb/src/shared/libosmocore/build-target'
make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Error 2
Can you guys help me to solve this problem...??
Thanks...
8:21 a.m.
New subject: Make Errors
On Thu, Oct 3, 2013 at 1:35 AM, Shahzad Ahmed <engr.shahzad786(a)gmail.com> wrote:
I'm installing osmocombb on Ubuntu13.04,
I've already set the path for arm-elf-gcc...
but I try this command..
$ sudo make
Bike shedding: you usually don't want to build as root. Use `sudo`
on
install if needed.
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:
Assembler messages:
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:32:
Error: no such instruction: `eor %edx,%ecx,%ecx,ror'
Looks like a path problem.
Ensure the assembler (AS) for the target is
on-path; and not the host's assembler.
How are you setting your cross compile environment?
Jeff
11:02 a.m.
New subject: Make Errors
Jeffrey Walton wrote:
Read the error message and think about that one more time.
The problem is not the assembler but the header file.
The original poster isn't building against a cross-compiled libosmocore.
//Peter
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:
Assembler messages:
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:32:
Error: no such instruction: `eor %edx,%ecx,%ecx,ror'
Looks like a path
problem. Ensure the assembler (AS) for the target is
on-path; and not the host's assembler.
10:38 p.m.
New subject: Make Errors
On Thu, Oct 3, 2013 at 5:02 AM, Peter Stuge <peter(a)stuge.se> wrote:
Jeffrey Walton wrote:
Read the error message and think about that one more time.
The problem is not the assembler but the header file.
That's an assembler error
message. It does not matter where the ASM came from.
You'd can get a similar error for inline ASM on a native (non-cross
compile) build. For example, using AVX's pclmulqdq instruction on an
older intel assembler that did not understand pclmulqdq would produce
a similar result. See, for example,
https://groups.google.com/forum/#!topic/cryptopp-users/6tCoUzsvXcM:
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:
Assembler messages:
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:32:
Error: no such instruction: `eor %edx,%ecx,%ecx,ror'
Looks like a path
problem. Ensure the assembler (AS) for the target is
on-path; and not the host's assembler. The original poster isn't building against a
cross-compiled libosmocore.
Oh, my bad. So OP is building for x86/x86_64, but the
header file only
makes available ARM routine? If so, I would think the ARM ASM would be
guarded in appropriate define.
Jeff
4 Oct
4 Oct
noon
New subject: Make Errors
Jeffrey Walton wrote:
Read the error message and think about that one more time.
The problem is not the assembler but the header file.
That's an assembler error message.
Yes, that's right.
No. As the error very clearly states the "eor" instruction is unknown.
eor is a 64-bit x86 instruction, so clearly the header file is for
x86_64, meaning that the assembler is for ARM.
The way that can happen is, as I wrote above, that the poster isn't
building against a cross-compiled libosmocore.
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:
Assembler messages:
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:32:
Error: no such instruction: `eor %edx,%ecx,%ecx,ror'
Looks like a path
problem. Ensure the assembler (AS) for the target is
on-path; and not the host's assembler. It does not matter where the ASM came from.
It really does.
You'd can get a similar error for inline ASM on a
native (non-cross
compile) build.
You get that error if you have a mismatch between the assembly and
the assembler.
The original
poster isn't building against a cross-compiled libosmocore.
Oh, my bad. So OP is building for x86/x86_64, but the header file only
makes available ARM routine? If so, I would think the ARM ASM would be guarded in
appropriate define.
I think it would be useful if you sent some patches to improve the
osmocom-bb build system. Thank you!
//Peter
1:06 p.m.
New subject: Make Errors
> >> >
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:
> >> > Assembler messages:
> >> >
/home/shahzad/arm/osmocom-bb/src/target/firmware/include/asm/swab.h:32:
> >> > Error: no such instruction: `eor %edx,%ecx,%ecx,ror'
Retry with a fresh checkout.
Attempting to build without the ARM toolchain, then installing it,
then retrying in the same directory doesn't work. There are some
leftovers from the failed attempt and you need to start everything
from scratch.
Cheers,
Sylvain
6 Jan
6 Jan
12:08 a.m.
Hi,
On 05.01.2011 18:15, Wolfram Sang wrote:
To prevent that another 20 people will run into this problem, I've taken
the liberty to test osmocom-bb with the latest version of libosmocore,
and merged it into master.
Regards,
Steve
../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory
See my mail from three days ago.
@maintainers: who can do the sync of libosmocore? 
7:21 a.m.
Hi Steve,
On Thu, Jan 06, 2011 at 12:08:11AM +0100, Steve Markgraf wrote:
thanks a lot.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
@maintainers: who can do the sync of libosmocore?
To prevent that another 20 people will run into this problem, I've
taken the liberty to test osmocom-bb with the latest version of
libosmocore, and merged it into master.
4873
days inactive
4874
days old
baseband-devel@lists.osmocom.org
14 comments
11 participants
participants (11)
-
Cristian Paul Peñaranda Rojas -
Harald Welte -
Hessel Schut -
Jeffrey Walton -
Peter Stuge -
Sebastian --- -
Sergio 'shadown' Alvarez -
Shahzad Ahmed -
Steve Markgraf -
Sylvain Munaut -
Wolfram Sang