Joel Sherrill commented on a discussion: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/29#note_111324 Now that I have written it, it feels a bit rambling. There may not be a real solution in here. It is just background which might help figure out a workable solution. @the.m3chanic GDB is built relatively early in the set of tools because it often fails to build because the python development package isn't installed (e.g. Python.h). At some point, Chris/I moved gdb up from last to near first so if this failure occurred, it wouldn't waste as much of the user's time. It is possible to move gdb back toward the end of the list. This may fix this problem if the cross gcc is visible while building. This may work but it doesn't address the small elephant left in the room which is why we moved the order of gdb back then... We wanted gdb to be early because the sb-check tool only checks for installed program executables. It does not check for needed libraries/headers. You can run sb-check and get an "ok" but fail because you are missing python-devel. Enhancing sb-check to check for libraries/headers would help users avoid starting a build they don't have all the dependencies to finish. -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/29#note_111324 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
