matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
8aa5fbbe79
sonic-buildimage/platform/broadcom/sai.mk

10 lines
806 B
Makefile
Raw Normal View History

[broadcom]: Upgrading bcmsai from 4.3.0.10-5 to 4.3.0.13 (#6767) Merged bcmsai 4.3.0.13 code to top of master bcmsai 4.3.0.10-5. - How to verify it Ran nightly regression on T0 and T1 topology using bcmsai 4.3.0.13. Test results are better than previous runs. For T0 - New test passing - CRM, Decap, FDB, platform test, VxLAN New test failing – PFC unknown MAC For T1 – New test passing – Port Channel New test failing – platform test
2021-02-11 04:31:56 -06:00
BRCM_SAI = libsaibcm_4.3.0.13_amd64.deb
$(BRCM_SAI)_URL = "https://sonicstorage.blob.core.windows.net/packages/bcmsai/4.3/master/libsaibcm_4.3.0.13_amd64.deb?sv=2019-12-12&st=2021-02-11T06%3A07%3A09Z&se=2030-02-12T06%3A07%3A00Z&sr=b&sp=r&sig=IlCyw1BGN0Ei56tPPeXJSucFSFj8SSqUGLB2A%2BRZ1w0%3D"
BRCM_SAI_DEV = libsaibcm-dev_4.3.0.13_amd64.deb
build orchagent and syncd docker on broadcom platform (#118) * build orchagent and syncd docker on broadcom platform
2016-12-14 13:59:24 -06:00
$(eval $(call add_derived_package,$(BRCM_SAI),$(BRCM_SAI_DEV)))
[broadcom]: Upgrading bcmsai from 4.3.0.10-5 to 4.3.0.13 (#6767) Merged bcmsai 4.3.0.13 code to top of master bcmsai 4.3.0.10-5. - How to verify it Ran nightly regression on T0 and T1 topology using bcmsai 4.3.0.13. Test results are better than previous runs. For T0 - New test passing - CRM, Decap, FDB, platform test, VxLAN New test failing – PFC unknown MAC For T1 – New test passing – Port Channel New test failing – platform test
2021-02-11 04:31:56 -06:00
$(BRCM_SAI_DEV)_URL = "https://sonicstorage.blob.core.windows.net/packages/bcmsai/4.3/master/libsaibcm-dev_4.3.0.13_amd64.deb?sv=2019-12-12&st=2021-02-11T06%3A08%3A31Z&se=2030-02-12T06%3A08%3A00Z&sr=b&sp=r&sig=G5mYUa8gCnDNpuadvHEuH%2B4q2MuY0JYspPLt2gaC2NY%3D"
build orchagent and syncd docker on broadcom platform (#118) * build orchagent and syncd docker on broadcom platform
2016-12-14 13:59:24 -06:00
[build]: Eliminate build warning messages (#2172)
2018-10-20 16:39:04 -05:00
SONIC_ONLINE_DEBS += $(BRCM_SAI)
[broadcom]: Updated BRCM SAI Debian package revision number to 3.7.3.3-2. (#4182) This has patch to fix enable/disable attribute for lag member. It's on top of vanilla 3.7.3.3
2020-02-25 11:14:23 -06:00
$(BRCM_SAI_DEV)_DEPENDS += $(BRCM_SAI)
[build]: wait for conflicts package to be uninstalled (#5039) when parallel build is enabled, both docker-fpm-frr and docker-syncd-brcm is built at the same time, docker-fpm-frr requires swss which requires to install libsaivs-dev. docker-syncd-brcm requires syncd package which requires to install libsaibcm-dev. since libsaivs-dev and libsaibcm-dev install the sai header in the same location, these two packages cannot be installed at the same time. Therefore, we need to serialize the build between these two packages. Simply uninstall the conflict package is not enough to solve this issue. The correct solution is to have one package wait for another package to be uninstalled. For example, if syncd is built first, then it will install libsaibcm-dev. Meanwhile, if the swss build job starts and tries to install libsaivs-dev, it will first try to query if libsaibcm-dev is installed or not. if it is installed, then it will wait until libsaibcm-dev is uninstalled. After syncd job is finished, it will uninstall libsaibcm-dev and swss build job will be unblocked. To solve this issue, _UNINSTALLS is introduced to uninstall a package that is no longer needed and to allow blocked job to continue. Signed-off-by: Guohan Lu <lguohan@gmail.com>
2020-07-27 12:46:20 -05:00
$(eval $(call add_conflict_package,$(BRCM_SAI_DEV),$(LIBSAIVS_DEV)))
Reference in New Issue Copy Permalink