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/.
Peter Stuge peter at stuge.seEric 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 at 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