Closed Zames-Chang closed 1 year ago
@juimonen @ranj063 any ideas - looks like a topology compiler crash. @Zames-Chang which topology file - the build output is in parallel so difficult to see which topology file is crashing the compiler ?
@perexg FYI, something in latest alsa-lib head is segfaulting all our topology1 builds....
I see the segfault as:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7ee20d7 in snd_interval_empty (i=
and this lead me to commit 78b20e3caa7bba930095e05f, which does seems little fishy, at least what reads in the commit message.
But even after using the get_access method I still get segfault. So something perhaps in the ALSA_PCM_OLD_HW_PARAMS_API things, but not sure...
Oops. I just reverted the debug code in src/topology/ctl.c . Thanks for the FYI.
@perexg thanks! builds now.
@Zames-Chang update alsa-lib to latest head.
@Zames-Chang can we close ?
Hi
Sorry for late reply. I can build topology now with latest head. Thanks for the help.
Describe the bug If you use newest alsa-lib to build topology will causing build failure. It can be workaround by checkout alsa-lib to commit 152983f01b0bc1178ea0d461ebf66e2d2a8e2e02
To Reproduce git checkout mt8186/v0.2 ./scripts/build-tools.sh -T
Reproduction Rate 100%
Expected behavior Can build
Impact What impact does this issue have on your progress (e.g., annoyance, showstopper)
Environment 1) Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
Screenshots or console output