ofs-2023.2-1 build fails after ofs-2023.3-1 release ???
Closed this issue · 4 comments
umairsiddiqui-digitek commented
ofs-2023.2-1 build fails after ofs-2023.3-1
i was not expecting a long term support cycle...but few hours after release!!!
>>> OFS Board Path = n6001
>>> OFS Board Core = n6001
Setting up build variables
source /home/cicd_srv/tmp/ofs-agx7-pcie-attach/syn/scripts/build_var_setup.sh
BUILD_ROOT_REL is
**********************************
********* ENV SETUP **************
FIM Project:
OFS_PROJECT = n6001
OFS_FIM =
OFS_BOARD = n6001
Q_PROJECT = ofs_top
Q_REVISION = ofs_top
Fitter SEED = 3
FME id
BITSTREAM_ID = 05010202489c6418
BITSTREAM_MD = 0000000002312143
Flow:
ENA_CREATE_WORK_DIR = 1
ENA_OPAE_SDK_SETUP_FOR_FIM = 1
ENA_PRE_COMPILE_SCRIPT = 0
ENA_SETUP_IP_LIB_SCRIPT = 1
ENA_FIM_COMPILE = 1
ENA_PR_SETUP = 1
ENA_FLASH = 1
ENA_PR_BUILD_TEMPLATE_GEN = 1
OPAE_SDK:
OPAE_SDK_REPO =
OPAE_SDK_REPO_BRANCH = 2.8.0-1
File pointers:
WORK_SYN_TOP_PATH = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top
CREATE_WORK_DIR_SH_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/ofs-common/scripts/common/syn/create_work_dir.sh
FME_ID_MIF_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/ofs-common/src/common/fme_id_rom/fme_id.mif
PMCI_NIOS_HEX_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/ipss/pmci/pmci_ss_nios_fw.hex
WORK_FME_ID_MIF_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/fme_id.mif
WORK_PMCI_NIOS_HEX_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/pmci_ss_nios_fw.hex
REPORT_TIMING_TCL_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/ofs-common/scripts/common/syn/report_timing.tcl
WORK_BUILD_FLASH_SH_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/build_flash/build_flash.sh
WORK_PRE_COMPILE_SCRIPT_SH_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/ofs-common/scripts/common/syn/pre_compile_script.sh
SETUP_OPAE_SDK_SH_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/ofs-common/scripts/common/syn/setup_opae_sdk.sh
REPO_PATH = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/external
PIM configuration:
PIM_PLATFORM_NAME = ofs_agilex_adp
PIM_INI_FILE = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/src/top/ofs_agilex_adp.ini
PIM_ROOT_DIR = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/afu_with_pim
*** Specified WORK directory: /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001
Creating /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001
Symlinking files...
This may take a couple of minutes...
Done setting up work directory (/home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001)
BUILD_ROOT_REL = ../../../..
WORK_DIR = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001
SETUP_OPAE_SDK_SH_FILE is /home/cicd_srv/tmp/ofs-agx7-pcie-attach/ofs-common/scripts/common/syn/setup_opae_sdk.sh
Setting up OPAE SDK
Found OPAE SDK programs on PATH. Not building OPAE SDK.
Using cloned OFS_PLATFORM_AFU_BBB=/home/cicd_srv/tmp/ofs-agx7-pcie-attach/external/ofs-platform-afu-bbb
+ git clone -b master https://github.com/OFS/ofs-platform-afu-bbb /home/cicd_srv/tmp/ofs-agx7-pcie-attach/external/ofs-platform-afu-bbb
Cloning into '/home/cicd_srv/tmp/ofs-agx7-pcie-attach/external/ofs-platform-afu-bbb'...
/usr/bin/env: ‘python’: No such file or directory
+ /home/cicd_srv/tmp/ofs-agx7-pcie-attach/external/ofs-platform-afu-bbb/plat_if_develop/ofs_plat_if/scripts/gen_ofs_plat_if -c /home/cicd_srv/tmp/ofs-agx7-pcie-attach/src/top/ofs_agilex_adp.ini -v -t /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/afu_with_pim/pim_template/hw/lib/build/platform/ofs_plat_if
/usr/bin/env: ‘python’: No such file or directory
+ set +x
d is import=../../ofs-common/src/fpga_family/agilex/port_gasket/afu_main_pim/extend_pim/
TGT = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/afu_with_pim/pim_template
IMPORT_SRC_PATH = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/src/top/../../ofs-common/src/fpga_family/agilex/port_gasket/afu_main_pim/extend_pim/
PIM_ROOT_DIR = /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/afu_with_pim
+ cd /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/afu_with_pim
+ env OPAE_PLATFORM_ROOT=/home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/afu_with_pim/pim_template afu_synth_setup --platform= -s /home/cicd_srv/tmp/ofs-agx7-pcie-attach/ofs-common/scripts/common/syn/pim/dummy_afu/dummy_afu_files.txt afu
Error: AFU is type 'ofs_plat_afu' but the release is either not defined or does not provide
an ofs_plat_if.
*** Either OPAE_PLATFORM_ROOT is not set correctly or the release at
*** $OPAE_PLATFORM_ROOT is missing the directory hw/lib/build/platform/ofs_plat_if.
Error: "afu_platform_config --qsf --tgt platform --src=/home/cicd_srv/tmp/ofs-agx7-pcie-attach/ofs-common/scripts/common/syn/pim/dummy_afu/dummy_afu.json ofs_agilex_adp" failed
Copying build from /home/cicd_srv/tmp/ofs-agx7-pcie-attach/work_n6001/syn/board/n6001/syn_top/afu_with_pim/pim_template/hw/lib/build...
Configuring Quartus build directory: afu/build
cohensus commented
Hi umairsiddiqui-digitek.
Thanks for reaching out. Let me understand more about your environment so I can help. Are you using all the same tags from the 2023.2-1 release( the ofs-2023.2-1 branch of the ofs-agx7-pcie-attach repo along with the 2.8.0-1 version of opae-sdk repo and the 2023.2-6.1.1 tag for linux-dfl) and you are getting a build failure? If you can help me understand all the tags you are using we can replicate. Additionally, can you let me know the build command you are using? Thanks so much!
Regards,
Susan
umairsiddiqui-digitek commented
$ rpm -qa | grep -i opae
opae-debugsource-2.8.0-1.el8.x86_64
opae-extra-tools-debuginfo-2.8.0-1.el8.x86_64
opae-devel-2.8.0-1.el8.x86_64
opae-extra-tools-2.8.0-1.el8.x86_64
opae-debuginfo-2.8.0-1.el8.x86_64
opae-2.8.0-1.el8.x86_64
opae-devel-debuginfo-2.8.0-1.el8.x86_64
$ git describe
ofs-2023.2-6.1-1
chipb-intel commented
@umairsiddiqui-digitek Did you intend to close this issue because it was resolved? Would you mind sharing what the problem was so the next person might be able to apply the same resolution?
umairsiddiqui-digitek commented
i have opened
#9
and python issues was resolved by "python-is-python3"