search

sonic-net / sonic-buildimage

Scripts which perform an installable binary image build for SONiC
Other
717 stars 1.38k forks source link

[build] [debug] [201911] compile failed when enable SONIC_DEBUGGING_ON or SONIC_PROFILING_ON #5982

Open tim-rj opened 3 years ago

tim-rj commented 3 years ago

Description

compile failed locally when enable SONIC_DEBUGGING_ON or SONIC_PROFILING_ON

Steps to reproduce the issue:

  1. set SONIC_DEBUGGING_ON = y (or SONIC_PROFILING_ON = y )
  2. make target/sonic-broadcom.bin
  3. compile failed

Describe the results you received:

/sonic/src/monit
mv: cannot stat 'monit-dbgsym_5.20.0-6_amd64.deb': No such file or directory
Makefile:9: recipe for target '/sonic/target/debs/stretch/monit_5.20.0-6_amd64.d                                                                                                          eb' failed
make[1]: *** [/sonic/target/debs/stretch/monit_5.20.0-6_amd64.deb] Error 1
make[1]: Leaving directory '/sonic/src/monit'
[  FAIL LOG END  ] [ target/debs/stretch/monit_5.20.0-6_amd64.deb ]
slave.mk:335: recipe for target 'target/debs/stretch/monit_5.20.0-6_amd64.deb' f                                                                                                          ailed
make: *** [target/debs/stretch/monit_5.20.0-6_amd64.deb] Error 1
make[1]: *** [Makefile.work:211: target/sonic-broadcom.bin] Error 2
make[1]: Leaving directory '/home/sdk/ssp/sonic-sym'
make: *** [Makefile:7: target/sonic-broadcom.bin] Error 2

Describe the results you expected:

ONE MACRO to enable symbol for all components and compile successful

Additional information you deem important (e.g. issue happens only occasionally):

If I run 'make target/debs/stretch/monit-dbgsym_5.20.0-6_amd64.deb ' after compile failed, it will success, but 'make target/sonic-broadcom.bin' will fall again for other component noting the linkly error 'cant stat xxx-dbgsym_xxx.deb'.

All the codes are open source ,we change nothing. what can we do to fix such problem?
tim-rj commented 3 years ago

I found that in issue log, no dbgsym deb is built:

1023    dh_md5sums
1024    dh_builddeb
1025 dpkg-deb: building package 'monit' in '../monit_5.20.0-6_amd64.deb'.
1026 make[2]: Leaving directory '/sonic/src/monit/monit'
1027  dpkg-genbuildinfo --build=binary
1028  dpkg-genchanges --build=binary >../monit_5.20.0-

compare the normal log:

   dh_gencontrol
   dh_md5sums
   dh_builddeb
dpkg-deb: building package 'monit-dbgsym' in '../monit-dbgsym_5.20.0-6_amd64.deb'.
dpkg-deb: building package 'monit' in '../monit_5.20.0-6_amd64.deb'.
make[2]: Leaving directory '/sonic/src/monit/monit'
 dpkg-genbuildinfo --build=binary
 dpkg-genchanges --build=binary >../monit_5.20.0-6_amd64.changes
tim-rj commented 3 years ago

This is actually an issue, i will plan to fix it soon.

zhangyanzhao commented 2 years ago

How to make this workaround work completely to fix the issue of #6413 ?

zhangyanzhao commented 2 years ago

Nvidia and MSFT members will have a discussion on this issue.