| #
b4edc27a |
| 19-Jul-2022 |
Andrew Geissler <geissonator@yahoo.com> |
utilize "/usr/bin/env perl" in perl scripts
When utilizing /usr/bin/perl, this expands to the full path of your
filesystem build. i.e. something like this:
/home/andrewg/Code/openbmc/build/withersp
utilize "/usr/bin/env perl" in perl scripts
When utilizing /usr/bin/perl, this expands to the full path of your
filesystem build. i.e. something like this:
/home/andrewg/Code/openbmc/build/witherspoon/tmp/work/x86_64-linux/mrw-perl-tools-native/1.0+gitAUTOINC+65ca8e19c4-r1/recipe-sysroot-native/usr/bin/perl
This now exceeds the allowed size by yocto:
"maximum shebang size exceeded, the maximum size is 128."
There are ways to disable this check in yocto, and we probably have a
case to argue this upstream, but our use in OpenBMC of perl is pretty
limited so the easiest solution is to just move the perl scripts over to
using /usr/bin/env. Half the perl scripts in this repo already do this.
Tested:
- Verified new yocto now builds this repo
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I1c6dfc49a9a1d5ace0d0b9fdd4fa7a0abdee033e
show more ...
|
| #
65ca8e19 |
| 16-Jul-2022 |
Andrew Geissler <geissonator@yahoo.com> |
ensure no space in script type string
New bitbake checks to ensure the #! line does not exceed 180 characters
and it requires no space between it and the script type info.
Signed-off-by: Andrew Gei
ensure no space in script type string
New bitbake checks to ensure the #! line does not exceed 180 characters
and it requires no space between it and the script type info.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If52da98c06aced381a6b82cfc0756c1a322f7aec
show more ...
|
| #
51041fc8 |
| 08-Oct-2019 |
Santosh Puranik <santosh.puranik@in.ibm.com> |
IPMI Parser Script Updates
This commit adds a new option to the IPMI MRW
parsing scripts (--skip-broken-mrw).
When specified, the option will cause the scripts
to ignore bro
IPMI Parser Script Updates
This commit adds a new option to the IPMI MRW
parsing scripts (--skip-broken-mrw).
When specified, the option will cause the scripts
to ignore broken MRW targets such as IPMI sensor
targets without a valid SENSOR_ID attribute
or a FRU without a valid FRU_ID.
This allows us to pull in an in-progress MRW without
it breaking our builds.
Tested:
I tested the scripts against an incomplete MRW and made
sure that the scripts ignored broken targets and generated
output config files for whatever targets were valid.
Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: Ibf2ca3769e6030d62e73fb362d73a775433273bc
show more ...
|
| #
9f3e1c1e |
| 19-Feb-2017 |
Deepak Kodihalli <dkodihal@in.ibm.com> |
gen_fru_properties.pl : fetch FRU properties
FRU management code can, via this script and by providing an input
config file, extract static FRU properties from the system MRW and have
gen_fru_properties.pl : fetch FRU properties
FRU management code can, via this script and by providing an input
config file, extract static FRU properties from the system MRW and have
the same output in YAML format.
Change-Id: I9ce76272d517f9309a87fe400ae6b65b9fcc2118
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
show more ...
|