Reapply xtensa gdb fix to the right section #87
Conversation
This reverts commit 7f4fc80.
This time to the correct apt-get line.
root@5b2362eb60c2:/src/nuttx# ldd /tools/xtensa-esp32-elf-gcc/bin/xtensa-esp32-elf-gdb
linux-vdso.so.1 (0x00007ffeb59f3000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f2a7fc31000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f2a7fc0e000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f2a7fc09000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f2a7faba000)
libpython2.7.so.1.0 => /lib/x86_64-linux-gnu/libpython2.7.so.1.0 (0x00007f2a7f74e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2a7f55c000)
/lib64/ld-linux-x86-64.so.2 (0x00007f2a7fc3f000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f2a7f53e000)
root@5b2362eb60c2:/src/nuttx#
|
Makes sense. |
|
a mysterious "unknown blob" happened in the job for this PR. i have no idea what it is. |
|
Yeah I retried the push job a few times and it still failed. There are a few tickets around about this but no real resolution. I was going to look tonight. Worse case I push it locally. |
|
i restarted the job once more. |
|
Something is bad in the cache. I am going to force this locally to get it unblocked, and then update the actions to better handle the cache, docker released some improvements to this. |
i have a locally-built image on docker hub for my convenience. |
|
Just kicked off the build locally and am going to manually push and see if that gets this unstuck. Forgot to do this. |
|
Was able to get it to push, lets see if it fails again. I think something got messed up when we had two runs writing the image at the same time. |
Summary
#83 was applied to the wrong instance of apt-get.
this PR fixes it.
Impact
Testing
built and tested locally (with #86)