WARNING: osmo-pcu-0.4+gitAUTOINC+0cd8e4eade-r5.18 do_configure: QA Issue: osmo-pcu: configure was passed unrecognised options: --enable-sysmocom-bts [unknown-configure-option]
Looking at ./configure --help in osmo-pcu, that option doesn't seem to
be available. The recipe is already using --enable-sysmocom-dsp too,
which is correct.
Commit d32cbbb13087eae2617920d4ea980f0e8869a89e changed --enable-sysmocom-bts to --enable-osmo-bts.
Later on, commit 08e5d604d3fce75b955549244b36fde62f20894b removed --enable-osmo-bts option.
Current u-boot version cannot handle correctly ext4 formated with 64bit
option, which is enabled by default with recent versions of mkfs.ext4.
If option 64bit is enabled, u-boot reads the filesystem erroneously,
listing wrong directories or displaying some directories such as /boot
as empty, which forbids itself from loading the kernel and failing to
boot.
See #3733 and https://github.com/armbian/build/issues/279 for more
details.
* use systemd class to auto-enable installed services
* make sure lc15-sysdev-remap is started before lc15bts-mgr
* keep BTS-specific name to enable adjustment via service file template
in future versions
Rename:
sysmobts -> osmo-bts-sysmo (available in master since 114293a414bd5b7c86622ec8c293c4034c80d243)
sysmopcu -> osmo-pcu (available in master since 241f5bcb00f9c6fee4200a3aea9aa497bf0d3eee)
Old names are still available via alias.
The function is declared and defined as inline and gcc6 will not
emit an external visible symbol for it. Master doesn't have this
problem anymore so let's just patch it here.
Fixes:
| /usr/src/debug/osmo-bts/0.4.3+gitAUTOINC+57ee780789-r1a2ff06d20-r18.18/git/tests/sysmobts/sysmobts_test.c:207: undefined reference to `l1if_ms_pwr_ctrl'
UBL is setting up the flash timings (A1CR) and so far U-Boot
was overwriting it with a timing for the EVB development board
of TI. Let UBL define ECC/ChipSelect and the A1CR timings.
This might now cause different kind of flash issues because the
per chip timings might be "wrong". This is why this commit should
needs to stay in testing a bit longer. We should use this commit
on RevC, D, E and F hardware ourselves a bit.
I didn't know that u-boot was creating a package and installing
the bin into /boot. The detection of the file seems to have
changed and a new QA error comes up.
ERROR: u-boot-v2011.12+gitAUTOINC+f6453a3911-r0 do_package: QA Issue: split_and_strip_files: 'file /home/oebuilds/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/sysmobts_v2-poky-linux-gnueabi/u-boot/v2011.12+gitAUTOINC+f6453a3911-r0/package/boot/u-boot-sysmobts-v2-v2011.12+gitAUTOINC+f6453a3911-r0' failed [split-strip]
This seems to have been introduced by changing the LC_ALL to
en_US.UTF-8. I have started a dialogue with upstream development
but as we do not need a u-boot package, let's just remove the
files.
The builds of the stable upgrade and the Yocto-Master failed
because of the commit gone missing (no remote is referencing
it). I created a dummy branch to hold this commit.
I think the last device we sold was in 2011 and I am not aware
if anyone has used it for the last couple of years. Remove it
to lower the complexity of the builds.
In yocto versions before dizzy/master the build was done
in the source directory and when configure was executed
twice in the same directory we would have a build failure
due the symlink already existing. Simply assume that if
the ln fails the link is already there.
Out of disk space situations are handled more early by
OE and missing files will be found by configure.
In dizzy/master OE will clean the build directory before
calling configure so the issue does not apply there.
Fixes: SYS#1170