[U-Boot] Swig now required to build U-Boot?
Simon,
Is it expected that the latest u-boot-dm.git master branch now requires swig? All the non-sandbox builds on my test systems are failing:
CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h GEN ./Makefile UPD include/generated/timestamp_autogenerated.h CHK include/config.h CFG u-boot.cfg SHIPPED scripts/dtc/pylibfdt/libfdt.i PYMOD scripts/dtc/pylibfdt/_libfdt.so unable to execute 'swig': No such file or directory error: command 'swig' failed with exit status 1 make[4]: *** [scripts/dtc/pylibfdt/_libfdt.so] Error 1 make[3]: *** [scripts/dtc/pylibfdt] Error 2 make[2]: *** [scripts/dtc] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs....
Hi Stephen,
On 8 December 2017 at 16:28, Stephen Warren swarren@wwwdotorg.org wrote:
Simon,
Is it expected that the latest u-boot-dm.git master branch now requires swig? All the non-sandbox builds on my test systems are failing:
CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h GEN ./Makefile UPD include/generated/timestamp_autogenerated.h CHK include/config.h CFG u-boot.cfg SHIPPED scripts/dtc/pylibfdt/libfdt.i PYMOD scripts/dtc/pylibfdt/_libfdt.so unable to execute 'swig': No such file or directory error: command 'swig' failed with exit status 1 make[4]: *** [scripts/dtc/pylibfdt/_libfdt.so] Error 1 make[3]: *** [scripts/dtc/pylibfdt] Error 2 make[2]: *** [scripts/dtc] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs....
Yes, unless we have a very recent libfdt on the system (and even then I'm not sure that it is picked up). We need swig to build pylibfdt which is needed for binman.
Regards, Simon
On 12/08/2017 04:53 PM, Simon Glass wrote:
Hi Stephen,
On 8 December 2017 at 16:28, Stephen Warren swarren@wwwdotorg.org wrote:
Simon,
Is it expected that the latest u-boot-dm.git master branch now requires swig? All the non-sandbox builds on my test systems are failing:
CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h GEN ./Makefile UPD include/generated/timestamp_autogenerated.h CHK include/config.h CFG u-boot.cfg SHIPPED scripts/dtc/pylibfdt/libfdt.i PYMOD scripts/dtc/pylibfdt/_libfdt.so unable to execute 'swig': No such file or directory error: command 'swig' failed with exit status 1 make[4]: *** [scripts/dtc/pylibfdt/_libfdt.so] Error 1 make[3]: *** [scripts/dtc/pylibfdt] Error 2 make[2]: *** [scripts/dtc] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs....
Yes, unless we have a very recent libfdt on the system (and even then I'm not sure that it is picked up). We need swig to build pylibfdt which is needed for binman.
Which version of swig is required? (Perhaps the makefile could check for the required minimum version and bail out early with a mesage, like it does for dtc and gcc?)
I have 2.0.11 available in the distro package repository, but I see that 3.0.x exists on swig.org. I hope I can get away with installing the standard OS package.
Hi Stephen,
On 8 December 2017 at 16:57, Stephen Warren swarren@wwwdotorg.org wrote:
On 12/08/2017 04:53 PM, Simon Glass wrote:
Hi Stephen,
On 8 December 2017 at 16:28, Stephen Warren swarren@wwwdotorg.org wrote:
Simon,
Is it expected that the latest u-boot-dm.git master branch now requires swig? All the non-sandbox builds on my test systems are failing:
CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h GEN ./Makefile UPD include/generated/timestamp_autogenerated.h CHK include/config.h CFG u-boot.cfg SHIPPED scripts/dtc/pylibfdt/libfdt.i PYMOD scripts/dtc/pylibfdt/_libfdt.so unable to execute 'swig': No such file or directory error: command 'swig' failed with exit status 1 make[4]: *** [scripts/dtc/pylibfdt/_libfdt.so] Error 1 make[3]: *** [scripts/dtc/pylibfdt] Error 2 make[2]: *** [scripts/dtc] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs....
Yes, unless we have a very recent libfdt on the system (and even then I'm not sure that it is picked up). We need swig to build pylibfdt which is needed for binman.
Which version of swig is required? (Perhaps the makefile could check for the required minimum version and bail out early with a mesage, like it does for dtc and gcc?)
I have 2.0.11 available in the distro package repository, but I see that 3.0.x exists on swig.org. I hope I can get away with installing the standard OS package.
Yes v2 should be fine. I have:
$ swig -version
SWIG Version 2.0.11
Compiled with g++ [x86_64-unknown-linux-gnu]
Configured options: +pcre
Please see http://www.swig.org for reporting bugs and further information
Regards, Simon
On 12/08/2017 05:04 PM, Simon Glass wrote:
Hi Stephen,
On 8 December 2017 at 16:57, Stephen Warren swarren@wwwdotorg.org wrote:
On 12/08/2017 04:53 PM, Simon Glass wrote:
Hi Stephen,
On 8 December 2017 at 16:28, Stephen Warren swarren@wwwdotorg.org wrote:
Simon,
Is it expected that the latest u-boot-dm.git master branch now requires swig? All the non-sandbox builds on my test systems are failing:
CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h GEN ./Makefile UPD include/generated/timestamp_autogenerated.h CHK include/config.h CFG u-boot.cfg SHIPPED scripts/dtc/pylibfdt/libfdt.i PYMOD scripts/dtc/pylibfdt/_libfdt.sounable to execute 'swig': No such file or directory error: command 'swig' failed with exit status 1 make[4]: *** [scripts/dtc/pylibfdt/_libfdt.so] Error 1 make[3]: *** [scripts/dtc/pylibfdt] Error 2 make[2]: *** [scripts/dtc] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs....
Yes, unless we have a very recent libfdt on the system (and even then I'm not sure that it is picked up). We need swig to build pylibfdt which is needed for binman.
Which version of swig is required? (Perhaps the makefile could check for the required minimum version and bail out early with a mesage, like it does for dtc and gcc?)
I have 2.0.11 available in the distro package repository, but I see that 3.0.x exists on swig.org. I hope I can get away with installing the standard OS package.
Yes v2 should be fine.
OK, installing the swig and python-dev packages made the builds work. I do see test failures on Beaver and Jetson TK1 (but not other boards), but I probably won't be able to look at those until Monday, and the tests haven't finished yet so I can't grab the logs.
On Fri, 8 Dec 2017, Simon Glass wrote:
Hi Stephen,
On 8 December 2017 at 16:28, Stephen Warren swarren@wwwdotorg.org wrote:
Simon,
Is it expected that the latest u-boot-dm.git master branch now requires swig? All the non-sandbox builds on my test systems are failing:
CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h GEN ./Makefile UPD include/generated/timestamp_autogenerated.h CHK include/config.h CFG u-boot.cfg SHIPPED scripts/dtc/pylibfdt/libfdt.i PYMOD scripts/dtc/pylibfdt/_libfdt.so unable to execute 'swig': No such file or directory error: command 'swig' failed with exit status 1 make[4]: *** [scripts/dtc/pylibfdt/_libfdt.so] Error 1 make[3]: *** [scripts/dtc/pylibfdt] Error 2 make[2]: *** [scripts/dtc] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs....
Yes, unless we have a very recent libfdt on the system (and even then I'm not sure that it is picked up). We need swig to build pylibfdt which is needed for binman.
Err, would it be long before we need Java/Eclipse/Maven/younameit to just build U-Boot?
--- ****************************************************************** * KSI@home KOI8 Net < > The impossible we do immediately. * * Las Vegas NV, USA < > Miracles require 24-hour notice. * ******************************************************************
On Fri, Dec 08, 2017 at 04:16:41PM -0800, Sergey Kubushyn wrote:
On Fri, 8 Dec 2017, Simon Glass wrote:
Hi Stephen,
On 8 December 2017 at 16:28, Stephen Warren swarren@wwwdotorg.org wrote:
Simon,
Is it expected that the latest u-boot-dm.git master branch now requires swig? All the non-sandbox builds on my test systems are failing:
CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h GEN ./Makefile UPD include/generated/timestamp_autogenerated.h CHK include/config.h CFG u-boot.cfg SHIPPED scripts/dtc/pylibfdt/libfdt.i PYMOD scripts/dtc/pylibfdt/_libfdt.so unable to execute 'swig': No such file or directory error: command 'swig' failed with exit status 1 make[4]: *** [scripts/dtc/pylibfdt/_libfdt.so] Error 1 make[3]: *** [scripts/dtc/pylibfdt] Error 2 make[2]: *** [scripts/dtc] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs....
Yes, unless we have a very recent libfdt on the system (and even then I'm not sure that it is picked up). We need swig to build pylibfdt which is needed for binman.
Err, would it be long before we need Java/Eclipse/Maven/younameit to just build U-Boot?
There is a fine line to be walked here. On the flip side, do we want to have to depend on N little external tools to put together a functional image? We can use binman to avoid some subset of that. That said, Simon, are we only building binman related stuff when we need binman in the end? Thanks!
Hi Tom,
On 11 December 2017 at 18:51, Tom Rini trini@konsulko.com wrote:
On Fri, Dec 08, 2017 at 04:16:41PM -0800, Sergey Kubushyn wrote:
On Fri, 8 Dec 2017, Simon Glass wrote:
Hi Stephen,
On 8 December 2017 at 16:28, Stephen Warren swarren@wwwdotorg.org wrote:
Simon,
Is it expected that the latest u-boot-dm.git master branch now requires swig? All the non-sandbox builds on my test systems are failing:
CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h GEN ./Makefile UPD include/generated/timestamp_autogenerated.h CHK include/config.h CFG u-boot.cfg SHIPPED scripts/dtc/pylibfdt/libfdt.i PYMOD scripts/dtc/pylibfdt/_libfdt.so unable to execute 'swig': No such file or directory error: command 'swig' failed with exit status 1 make[4]: *** [scripts/dtc/pylibfdt/_libfdt.so] Error 1 make[3]: *** [scripts/dtc/pylibfdt] Error 2 make[2]: *** [scripts/dtc] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs....
Yes, unless we have a very recent libfdt on the system (and even then I'm not sure that it is picked up). We need swig to build pylibfdt which is needed for binman.
Err, would it be long before we need Java/Eclipse/Maven/younameit to just build U-Boot?
There is a fine line to be walked here. On the flip side, do we want to have to depend on N little external tools to put together a functional image? We can use binman to avoid some subset of that. That said, Simon, are we only building binman related stuff when we need binman in the end? Thanks!
Sorry I missed this question but answered it on another thread. Yes we are only building pylibfdt when it is needed. It is controlled by CONFIG_PYLIBFDT which is enabled when binman or dtoc are needed.
Regards, Simon
participants (4)
-
Sergey Kubushyn -
Simon Glass -
Stephen Warren -
Tom Rini