The issu-version file for Mellanox is generated from the Mellanox SDK libraries. The SDK is installed into a Buster docker container, but the issu-version file goes onto the base OS, which is Bullseye. To work around this, the issu-version build rules explicitly copies the issu-version file to target/files/bullseye/ during the Buster build. Because of our build infra, if caching is enabled and a cache is being used, then for issu-version, since it is technically built as part of Buster, then only target/files/buster/issu-version is saved into the cache, and target/files/bullseye/issu-version isn't cached. If this cache gets used, then target/files/bullseye/issu-version is missing, and the final image build fails. This is to work around the current build issue where Mellanox builds are failing. This is so that issu-version is always "built", so that copy is made into the bullseye directory. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> |
||
---|---|---|
.. | ||
docker-saiserver-mlnx | ||
docker-syncd-mlnx | ||
docker-syncd-mlnx-rpc | ||
hw-management | ||
issu-version | ||
mft | ||
mlnx-platform-api | ||
mlnx-sai | ||
sdk-src | ||
.gitignore | ||
asic_table.j2 | ||
docker-saiserver-mlnx.dep | ||
docker-saiserver-mlnx.mk | ||
docker-syncd-mlnx-rpc.dep | ||
docker-syncd-mlnx-rpc.mk | ||
docker-syncd-mlnx.dep | ||
docker-syncd-mlnx.mk | ||
fw.dep | ||
fw.mk | ||
hw-management.dep | ||
hw-management.mk | ||
issu-version.dep | ||
issu-version.mk | ||
libsaithrift-dev.dep | ||
libsaithrift-dev.mk | ||
mft.dep | ||
mft.mk | ||
mlnx-ffb.dep | ||
mlnx-ffb.mk | ||
mlnx-ffb.sh | ||
mlnx-fw-upgrade.j2 | ||
mlnx-onie-fw-update.dep | ||
mlnx-onie-fw-update.mk | ||
mlnx-onie-fw-update.sh | ||
mlnx-platform-api.dep | ||
mlnx-platform-api.mk | ||
mlnx-sai.dep | ||
mlnx-sai.mk | ||
mlnx-ssd-fw-update.dep | ||
mlnx-ssd-fw-update.mk | ||
mlnx-ssd-fw-update.sh | ||
one-image.dep | ||
one-image.mk | ||
peripheral_table.j2 | ||
platform.conf | ||
rules.dep | ||
rules.mk | ||
sdk.dep | ||
sdk.mk |