openbsc build broken due to new GSM_PCHAN value

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/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Mon Jul 25 09:54:49 UTC 2016


On Sun, Jul 24, 2016 at 10:06:58PM +0800, Holger Freyther wrote:
> 
> > On 24 Jul 2016, at 20:48, Neels Hofmeyr <nhofmeyr at sysmocom.de> wrote:
> > 
> > Build fixed in 17a6bab150bd70954b00645c8d1f18ce3ccf8948
> > https://gerrit.osmocom.org/568
> > 
> > I pushed the commit through without peer review to fix the build, so maybe have
> > a look whether I need to improve something.
> 
> 
> is it feasible to move the value_string array to libosmocore too?

I'm pretty sure that it is... someone just needs to do it...
I'd like to first put a lid on the dyn TS feature before adding more cosmetics.

> The VTY test would then still fail but that is okay(tm).

...not failing anymore :)

~Neels

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160725/924ed52e/attachment.bin>


More information about the OpenBSC mailing list