Hi,
i have a problem with bs11_config. When i start it, i get this:
---------------------------------------------------------
# ./bs11_config -p /dev/ttyS0 /path/to/BTSBMC76.SWI
bs11_config (C) 2009 by Harald Welte and Dieter Spaar
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY
Invalid length in hdr: 0
Speicherzugriffsfehler
---------------------------------------------------------
Thanks
Marcus
--
Marcus Specht
open|MVNO
c/o Cyber-Dynamix Gesellschaft für Systemintegration GmbH
Heiner-Stuhlfauth-Str. 28
90480 Nürnberg
Tel.: 0911 / 1809105
Fax.: 0911 / 1809109
Geschäftsführer: Heiko Thierbach, Gerhard Feder
Sitz der Gesellschaft ist Nürnberg
Amtsgericht Nürnberg, HRB 16704
Ust-Id.-Nr. DE204640808
------------------------------------------------------------------------------
Diese Nachricht ist eine nicht öffentliche Mitteilung.
Sollten Sie diese Nachricht versehentlich erhalten haben
und nicht der gewünschte Empfänger sein,
so bitten wir Sie, diese Nachricht zu löschen, keine
Kopien anzufertigen und nicht weiterzuleiten. Bitte
informieren Sie uns per eMail über den Zustellungsfehler
und entschuldigen Sie die Unannehmlichkeit.
Bitte beachten Sie: Unabhängig vom Inhalt stellt diese
Nachricht keinerlei vertragliche Verpflichtung,
Zusicherung, Bestellung, Angebot oder ähnliches dar,
solange keine schriftliche Bestätigung von uns vorliegt.
On Saturday 06 March 2010 00:58:50 Harald Welte wrote:
>
> I think OpenBSC has been quite useful and stable for quite some time, it
> would be great to make something like an 1.0 release at some point soon.
> Maybe zecke and myself can do this in the next couple of weeks.
Shall we pick 1.0.0 for both OpenBSC and libosmocore?
Hi,
I have downloaded and compiled both libosmocore and OpenBSC. However, when
I try to execute an OpenBSC program (for example ipaccess-find) I see the
following error
~/openbsc/openbsc/src# ./ipaccess-find eth0
./ipaccess-find: error while loading shared libraries: libosmocore.so.0:
cannot open shared object file: No such file or directory
could you help me. Thanks.
Ahmet
On Saturday 06 March 2010 00:58:50 Harald Welte wrote:
>
> I think OpenBSC has been quite useful and stable for quite some time, it
> would be great to make something like an 1.0 release at some point soon.
> Maybe zecke and myself can do this in the next couple of weeks.
Shall we pick 1.0.0 for both OpenBSC and libosmocore?
Hi All
Just to clarify this (since we've had another question on the ML)
On Wed, Mar 03, 2010 at 10:15:44AM +0100, Holger Freyther wrote:
> You are using the latest version of libosmocore but not the one of OpenBSC.
You always need to use latest OpenBSC with latest libosmocore. We really
cannot afford to spend more time in supporting any kind of forward/backward
compatibility on a commit level.
However, what we should do, is to make official releases of both the library
and the OpenBSC program. OpenBSC will then require a particular version of
libosmocore, and the configure script will notice if it is not available.
I think OpenBSC has been quite useful and stable for quite some time, it would
be great to make something like an 1.0 release at some point soon. Maybe
zecke and myself can do this in the next couple of weeks.
> libosmocore is a rather new library and we move stuff from OpenBSC into this
> library, which means if you have a new version of libosmocore and a bit older
> one of OpenBSC your compiler will see stuff twice.
This will probably still be the case for the weeks to come, while even more
stuff (e.g. 04.08 call control IE parsing / generation) moves into libosmocore.
So please, always do a full cycle of
* "git pull" on libosmocore
* "git pull" on openbsc
* "./configure && make install" on libosmocore
* "./configure && make" on openbsc
This way you'll get a consistent build.
Thanks for your understanding,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi,
i want to operate two BS-11 via one E1-card. And i did it almost like
here:
http://lists.gnumonks.org/pipermail/openbsc/2009-August/000733.html
But i dont know how to configure the bport1 object for multidrop and how
to use the hfcmulti module to get two interfaces (for lcr i compiled
misdn_l1loop but i think this isnt the right here ;)). So atm i am not
able to communicate with the second BS11 :/. Any idea?
Thx & Greets Till
i thought it is the same (sorry, but i could not yet compile it myself).
try changing gsm.h line 79 into:
extern char gsm_conf_error[128];
or
extern char gsm_conf_error[];
anyway: i hate global return values and i will change it.
________________________________
Von: Ihab el Bakri [mailto:ihab.elbakri@hotmail.com]
Gesendet: Dienstag, 16. März 2010 12:33
An: Andreas.Eversberg
Cc: openbsc
Betreff: RE: AW: AW: AW: WG: again compilation of lcr
still getting errors:
gsm_conf.c:15: error: conflicting declaration âchar gsm_conf_error [128]â
gsm.h:79: error: âgsm_conf_errorâ has a previous declaration as âchar* gsm_conf_errorâ
make[1]: *** [gsm_conf.o] Error 1
make[1]: Leaving directory `/usr/src/test2/new/lcr'
make: *** [all] Error 2
________________________________
Hotmail: Trusted email with powerful SPAM protection. Sign up now. <https://signup.live.com/signup.aspx?id=60969>
oops, try this:
---
diff --git a/gsm_conf.c b/gsm_conf.c
index 560d9b3..6daf9b3 100644
--- a/gsm_conf.c
+++ b/gsm_conf.c
@@ -12,7 +12,7 @@
#include "main.h"
-char *gsm_conf_error = (char *)"";
+char gsm_conf_error[128] = "";
/* read options
*
---
i never had an error in the config, so an error message never created.
> 000000 DEBUG (in getrulesetbyname() line 1871): ruleset main found.
> Segmentation fault
can you provide gnu debug?
start gdb inside lcr source directory:
root@isdn-tester:~# gdb
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i586-pc-linux-gnu".
(gdb)
load and run
(gdb) file lcr
Reading symbols from lcr...done.
(gdb) run start
after crash type
(gdb) where
you will get a traceback. it should also say the line in code where the
crash happened. (before libc was called)
