This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.
Rusty Dekema rdekema at gmail.comI am not familiar with that error. I would recommend starting over (except for building the gcc toolchain; that part is probably alright) and making sure to follow the directions on the wiki carefully. Cheers, Rusty D On Mon, Apr 14, 2014 at 11:02 AM, Ahmad Jan <e10007a at gmail.com> wrote: > As m using bash, export PATH=$PATH:/home/arslan/dir/install/bin seems to > resolved this issue of arm-elf-gcc. M really grateful for your help. > > After that, when i went on making the source, a new sort of error has been > arrived. > It seems to be quite a big problem as compare to last one. It look like > this: > > make[1]: Entering directory `/home/arslan/osmocom-bb/src/target/firmware' > LD board/compal_e88/hello_world.highram.elf > apps/hello_world/main.o: In function `console_rx_cb': > /home/arslan/osmocom-bb/src/target/firmware/apps/hello_world/main.c:59: > undefined reference to `msgb_free' > comm/libcomm.a(sercomm.o): In function `sercomm_sendmsg': > /home/arslan/osmocom-bb/src/target/firmware/comm/sercomm.c:138: undefined > reference to `msgb_enqueue' > comm/libcomm.a(sercomm.o): In function `msgb_alloc_headroom': > /home/arslan/osmocom-bb/src/target/firmware/../../shared/libosmocore/include/osmocom/core/msgb.h:388: > undefined reference to `msgb_alloc' > comm/libcomm.a(sercomm.o): In function `sercomm_drv_pull': > /home/arslan/osmocom-bb/src/target/firmware/comm/sercomm.c:174: undefined > reference to `msgb_dequeue' > /home/arslan/osmocom-bb/src/target/firmware/comm/sercomm.c:201: undefined > reference to `msgb_free' > comm/libcomm.a(sercomm.o): In function `sercomm_drv_rx_char': > /home/arslan/osmocom-bb/src/target/firmware/comm/sercomm.c:259: undefined > reference to `msgb_free' > comm/libcomm.a(sercomm.o): In function `dispatch_rx_msg': > /home/arslan/osmocom-bb/src/target/firmware/comm/sercomm.c:240: undefined > reference to `msgb_free' > comm/libcomm.a(sercomm_cons.o): In function `msgb_alloc_headroom': > /home/arslan/osmocom-bb/src/target/firmware/../../shared/libosmocore/include/osmocom/core/msgb.h:388: > undefined reference to `msgb_alloc' > make[1]: *** [board/compal_e88/hello_world.highram.elf] Error 1 > make[1]: Leaving directory `/home/arslan/osmocom-bb/src/target/firmware' > make: *** [firmware] Error 2 > > > > Any idea, anyone? > > > On Mon, Apr 14, 2014 at 7:07 PM, Rusty Dekema <rdekema at gmail.com> wrote: >> >> To the best of my knowledge from when I first was trying to build >> osmocom-bb, the error you are receiving is a result of gcc for Intel >> x86/x86_64 trying to compile ARM code. There is no 'eor' instruction >> for x86, which is why you get that error. >> >> When you built the toolchain, you built a copy of gcc that compiles to >> the ARM architecture. On your system, this compiler should be located >> at /home/arslan/dir/install/bin/arm-elf-gcc. The message about >> assuming arm-elf-gcc is inside the current path means your PATH >> environment variable, not your current working directory. So, if you >> add /home/arslan/dir/install/bin to your path environment variable, >> the osmocom-bb build scripts will be able to find arm-elf-gcc there, >> and you should not receive that error. >> >> If you are using bash as your shell, you can accomplish this by >> issuing the command: >> >> export PATH=$PATH:/home/arslan/dir/install/bin >> >> Cheers, >> Rusty D >> >> >> >> On Mon, Apr 14, 2014 at 7:46 AM, Ahmad Jan <e10007a at gmail.com> wrote: >> > Hi... >> > I m trying to install osmocom-bb using following link: >> > >> > http://bb.osmocom.org/trac/wiki/Software/GettingStarted >> > >> > First of all i installed the Dependencies for the host. >> > >> > Then for target dependencies, i build my own toolchain using following: >> > >> > http://bb.osmocom.org/trac/wiki/GnuArmToolchain >> > >> > This toolchain building processes ended up saying: "Build complete! Add >> > /home/arslan/dir/install/bin to your PATH to make arm-elf-gcc and >> > friends >> > accessible directly." >> > (i don't know building my own toolchain is necessary or not). >> > >> > Then i went back for building osmocom-bb >> > >> > There i came across getting and updating the source. >> > >> > But in building the source section, what it says is: " Compiling both >> > the >> > target and the host code will happen with the following command. It >> > assumes >> > that the arm-elf-gcc is inside the current path." >> > >> > I didn't understand it as my current path is osmocom-bb and there is no >> > arm-elf-gcc >> > Can anyone tell me what does it mean? >> > >> > Anyways, i just ignored it and went on executing the following command >> > >> > cd src/ >> > make >> > >> > So i ended up with an error saying: >> > /home/arslan/osmocom-bb/src/target/firmware/include/asm/swab.h:32: >> > Error: no >> > such instruction: `eor %edx,%r15d,%r15d,ror' >> > make[4]: *** [gsmtap_util.lo] Error 1 >> > >> > I tried to figure it out from Internet. It really didn't work out. >> > M stuck at this point. >> > Can anyone help me resolving this problem? >> > >> > > >