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/OpenBSC@lists.osmocom.org/.
Ruben Undheim ruben.undheim at gmail.comI made a litle bit progress. The problem disappears if "-Wl,-Bsymbolic-functions" is removed from LDFLAGS. Any idea why? Ruben On Wed, Feb 10, 2016 at 07:22:50PM +0100, Ruben Undheim wrote: > Hi, > > Can someone here help me debug the failing build of libosmocore in Ubuntu? > > See: > https://launchpadlibrarian.net/235791225/buildlog_ubuntu-xenial-amd64.libosmocore_0.9.0-3_BUILDING.txt.gz > > The test case "gprs-bssgp" fails with following output: > > stderr: > MESSAGE to 0x7f0000ff, msg length 12 > 02 00 81 01 01 82 0b 56 04 82 0b 55 > All NS-VCs for NSEI 2901 are either dead or blocked! > All NS-VCs for NSEI 2901 are either dead or blocked! > BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error - unspecified > BSSGP BVCI=1234 Rx BVC STATUS, cause=Unknown BVCI > NSEI=2901/BVCI=2989 Cannot handle PDU type 34 for unknown BVCI, NS BVCI 2989 > Unable to resolve NSEI 4660 to NS-VC! > Assert failed rc >= 0 gb/gprs_bssgp_test.c:234 > > > I think it is related to the hardening option "-D_FORTIFY_SOURCE=2". What is > interesting is that it builds correctly in Debian, but not Ubuntu. > > The issue has apparently been observed before: > http://comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/4149 > > If this gets fixed quickly, it might go into the next Ubuntu LTS version which > has import freeze Feb 18th. > > > Cheers, > Ruben