If you did build and "make install" sdcc (from trunk or source snapshots
tarball) between the beginning of March, and today, this issue most
likely affects you.
During my work on merging current upstream binutils into thr SDCC fork,
I introduced a bug (https://sourceforge.net/p/sdcc/bugs/3972/). The bug
resulted in "make install" installing some executables into
/usr/local/bin that did not have the sd prefix the binaries from the
SDCC binutils fork should have.
This resulted in some executables, in particular addr2line, readelf,
strip, size, strings being installed in /usr/local, i.e. in the user's
path that did not support the host binaries (sine they were compiled
with support for SDCC targest only).
When the user attempted to e.g. do a "strip" of a host binary,
/usr/local/bin/strip could be in the path and be used instead of the
correct executable. Then, instead of the intended strip action on the
host binary, the user would just get an error message "Unexpected
character `\177' in asxxxx .rel file"
If you are affected by the issue, you will notice executables addr2line,
readelf, strip, size, strings in /usr/local/bin with the same or similar
creation timestamp as /usr/local/bin/sdcc. In tha case, please:
* Delete addr2line, readelf, strip, size, strings in /usr/local/bin
* Use an SDCC version from before March 2026 or later than today's
revision 16451.
Philipp
_______________________________________________
Sdcc-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sdcc-user
