baseband-devel January 2012

baseband-devel@lists.osmocom.org

38 participants
55 discussions

by Luca Bongiorni

Hi Dario, i suggest you to download the last Sylvain's burst_ind, because is improved of some features and patch it manually with Nohl's patch. Then you will be able to dump the bursts using ccch_scan, instead of layer23. Cheers, Luca > Can someone drive me to the right direction? P.S: http://comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/1754

13 years, 6 months

Re: Compling pb with Ubuntu 11.04 64 bits

by Holger Hans Peter Freyther

On 01/01/2012 03:34 PM, Eric Tyberghien wrote: > Hi all > Hi Gustav, it is your third mail (one private, two to the list) but it is sadly not much of a dialogue. There is nothing wrong with Ubuntu 11.10 (11.04...) but apparently you changed more than jut 11.10 -> 11.04. From the little information you provide one can see you at least changed the place where you keep the sourcecode. So please keep your environment stable because otherwise you wasted the time of the ones that were kind enough to respond. So the path to success: 1.) Think, try to understand what happens 2.) Provide context when you are writing an email, what do you do, why do you do this? what you think should happen 3.) include complete output.... In this specific case: Find where the sourcecode of msgb_free is (the answer will be msgb.c), find the msgb.o (compiled object file) that was compiled for ARM. Look if there is a msgb_free in it (objdump,nm..) or if there is something wrong with this file (ls, file, readelf). My guess is that you did something funny during compile and ended up with a zero byte msgb.o. cheers holger

13 years, 6 months

Compling pb with Ubuntu 11.04 64 bits

by Eric Tyberghien

Hi all I'll upgrade a Ubuntu 11.04 64 bits to 11.10 and it seems something was wrong. Now I have reinstall an "old" Ubuntu 11.04 64 bits from scratch and the compile process is fairly better but I obtain this failure : apps/hello_world/main.o: In function `console_rx_cb': apps/hello_world/main.c:59: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_alloc_msgb': ../../shared/libosmocore/include/osmocom/core/msgb.h:330: undefined reference to `msgb_alloc' comm/libcomm.a(sercomm.o): In function `sercomm_drv_rx_char': comm/sercomm.c:246: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `dispatch_rx_msg': comm/sercomm.c:227: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_drv_pull': comm/sercomm.c:161: undefined reference to `msgb_dequeue' comm/sercomm.c:188: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_sendmsg': comm/sercomm.c:125: undefined reference to `msgb_enqueue' comm/libcomm.a(sercomm_cons.o): In function `msgb_alloc_headroom': ../../shared/libosmocore/include/osmocom/core/msgb.h:330: undefined reference to `msgb_alloc' make[1]: *** [board/compal_e88/hello_world.compalram.elf] error 1 make[1]: Leaving directory `/srv/osmocom-bb/src/target/firmware' make: *** [firmware] error 2 Any idea Regards

13 years, 6 months

Re: Compiling failure with Ubuntu 11.10 64 bits

by Holger Hans Peter Freyther

On 01/01/2012 12:45 AM, Eric Tyberghien wrote: > Hi all > The config.log file is like that I think the relevant part is not in the log file. Put it somewhere and post a link, or preferable go through it yourself once more. Are you sure that autoconf/automake deal well with the encoding of your accents in the directories? thanks

13 years, 6 months

Re: Compiling failure with Ubuntu 11.10 64 bits

by Peter Stuge

Eric Tyberghien wrote: > I'm using Ubuntu 11.10 64 bits and I try to compile osmocom-bb but > it fails due to the enable-linker-buid-id option not supported by > the ld linker How do you come to that conclusion? > make[1]: quittant le répertoire « > /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target » Please keep in mind to always export LANG=C LC_ALL=C when posting output, so that there are no translations from english which both make everything more difficult to understand and usually also are very very bad translations. Never send localized output unless asking on a local-only mailing list. > cd shared/libosmocore/build-host && ../configure Who runs this command? You or make? > checking whether the C compiler works... no > configure: error: in > `/home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-host': > configure: error: C compiler cannot create executables > See `config.log' for more details > make: *** [sharedroland(a)redhat.com> > /libosmocore/build-host/Makefile] Erreur 77 .. > $ ./configure configure -v --with-pkgversion=Ubuntu/Linaro 4.6.1-9ubuntu3 > --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs > --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr > --program-suffix=-4.6 --enable-shared --disable-linker-build-id > --with-system-zlib --libexecdir=/usr/lib --without-included-gettext > --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 > --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin > --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic > --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu > --target=x86_64-linux-gnu Who is running the above and why? > configure:2839: checking for x86_64-linux-gnu-gcc > configure:2855: found /usr/bin/x86_64-linux-gnu-gcc So this is the compiler that would be used. > Thread model: posix > gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) > configure:3155: $? = 0 > configure:3144: x86_64-linux-gnu-gcc -V >&5 > x86_64-linux-gnu-gcc: error: unrecognized option '-V' > x86_64-linux-gnu-gcc: fatal error: no input files > compilation terminated. > configure:3155: $? = 4 > configure:3144: x86_64-linux-gnu-gcc -qversion >&5 > x86_64-linux-gnu-gcc: error: unrecognized option '-qversion' > x86_64-linux-gnu-gcc: fatal error: no input files > compilation terminated. > configure:3155: $? = 4 > configure:3175: checking whether the C compiler works > configure:3197: x86_64-linux-gnu-gcc conftest.c >&5 > /usr/local/bin/ld: unrecognized option '--build-id' > /usr/local/bin/ld: use the --help option for usage information > collect2: ld returned 1 exit status Find why /usr/bin/x86_64-linux-gnu-gcc invokes /usr/local/bin/ld. > Any idea ? I think you have simply created a broken build environment on your system. I have no idea how you did that, but you seem to just have a mess of toolchains. You need to clean that up and set up the neccessary system and target toolchains. Nothing more, nothing less. //Peter

13 years, 6 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel January 2012