Hi, I was following the procedure "Compiling osmo-bts for sysmoBTS" and using poky/1.5.4/sysroots/armv5te-poky-linux-gnueabi
During execution of libosmocore project it failed with: ... GEN gsm0503_conv.c Traceback (most recent call last): File "../../utils/conv_gen.py", line 26, in <module> import sys, os, math, argparse ImportError: CC oap.lo No module named argparse Makefile:735: recipe for target 'gsm0503_conv.c' failed make[2]: *** [gsm0503_conv.c] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory '/home/ivaylo/net/osmo/libosmocore/src/gsm' Makefile:460: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/ivaylo/net/osmo/libosmocore' Makefile:327: recipe for target 'all' failed make: *** [all] Error 2 ...
I am using:
Python 2.7.12+ (default, Sep 17 2016, 12:08:02) [GCC 6.2.0 20160914] on linux2 Type "help", "copyright", "credits" or "license" for more information.
I think that something is broken.
regards, Ivaylo
This seems to be caused by recent 2c717948d91540016067f87bb3e0913067d42647 although it shouldn't have: argparse is part of python2.7 (not sure about minor version though) and our poky toolchain 1.5.4 uses Python 2.7.3
Could it be that python is somehow misconfigured in the toolchain? Shall we add argparse to sysroots/i686-pokysdk-linux/usr/lib/python2.7 manually or try to update toolchain to newer version?
Max.
I can reproduce this.
Just pulled the newest libosmocore and SDK https://downloads.sysmocom.de/generic/sysmobts/201310-nightly/sdk/poky-eglib... and got the same error.
Ivaylo, for now you could locally revert this revision to be able to continue: cd libosmocore git revert 2c717948d91540016067f87bb3e0913067d42647
For general solutions: the SDK apparently provides optarg, so we could use that instead of argparse.
We could also try to find out why there is no argparse, but it seems to be more effort; the potential reason being packaging choices further upstream that might cause continuous efforts to work around??
~N
On Thu, Feb 09, 2017 at 06:25:51PM +0100, Ivaylo Kostov wrote:
Hi, I was following the procedure "Compiling osmo-bts for sysmoBTS" and using poky/1.5.4/sysroots/armv5te-poky-linux-gnueabi
During execution of libosmocore project it failed with: ... GEN gsm0503_conv.c Traceback (most recent call last): File "../../utils/conv_gen.py", line 26, in <module> import sys, os, math, argparse ImportError: CC oap.lo No module named argparse Makefile:735: recipe for target 'gsm0503_conv.c' failed make[2]: *** [gsm0503_conv.c] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory '/home/ivaylo/net/osmo/libosmocore/src/gsm' Makefile:460: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/ivaylo/net/osmo/libosmocore' Makefile:327: recipe for target 'all' failed make: *** [all] Error 2 ...
I am using:
Python 2.7.12+ (default, Sep 17 2016, 12:08:02) [GCC 6.2.0 20160914] on linux2 Type "help", "copyright", "credits" or "license" for more information.
I think that something is broken.
regards, Ivaylo
--
- Ivaylo Kostov ikostov@sysmocom.de mailto:ikostov@sysmocom.de
http://www.sysmocom.de/
- sysmocom - systems for mobile communications GmbH
- Alt-Moabit 93
- 10559 Berlin, Germany
- Sitz / Registered office: Berlin, HRB 134158 B
- Geschaeftsfuehrer / Managing Director: Harald Welte
Ironically the previous version of this patch was using getopt but it was changed to argparse based on review comments.
On 10.02.2017 13:24, Neels Hofmeyr wrote:
On Fri, Feb 10, 2017 at 01:19:15PM +0100, Neels Hofmeyr wrote:
For general solutions: the SDK apparently provides optarg, so we could use that instead of argparse.
make that: getopt
~N
Hi Neels and Ivaylo,
On Fri, Feb 10, 2017 at 01:19:15PM +0100, Neels Hofmeyr wrote:
Just pulled the newest libosmocore and SDK https://downloads.sysmocom.de/generic/sysmobts/201310-nightly/sdk/poky-eglib... and got the same error.
For general solutions: the SDK apparently provides optarg, so we could use that instead of argparse.
No, let's not go back there. We've been through that discussion.
We could also try to find out why there is no argparse, but it seems to be more effort; the potential reason being packaging choices further upstream that might cause continuous efforts to work around??
I'd say it just needs the right package name added to packagegroup-sdk-osmo.inc in https://github.com/sysmocom/meta-telephony/blob/master/recipes-osmocom/packa...
Also, as this discussion relates to the sysmocom SDK for a specific type of sysmocom products, I don't think we should bother the Osmocom mailing list with this.
On Fri, Feb 10, 2017 at 01:38:22PM +0100, Harald Welte wrote:
For general solutions: the SDK apparently provides optarg, so we could use that instead of argparse.
No, let's not go back there. We've been through that discussion.
ignore my recent mail/patch then.
~N
On Fri, Feb 10, 2017 at 01:19:15PM +0100, Neels Hofmeyr wrote:
For general solutions: the SDK apparently provides optarg, so we could use that instead of argparse.
Changed to getopt in https://gerrit.osmocom.org/1792 which works with the current nightly SDK.
~N
-
Harald Welte -
Ivaylo Kostov -
Max -
Neels Hofmeyr