Hi, Thanks a lot for your continuing work on mbuffer!
What do you think about the attached trivial patch that makes mbuffer consistently look for host tools, not target tools, when cross-compiling? It was brought to my attention by Helmut Grohne, who does a lot of work on cross-building Debian packages, in a Debian bug: https://bugs.debian.org/972427 As far as I understand the difference between build, host, and target architectures in the GNU autotools paradigm, if an object file that was built for the host system needs to be examined, the host version of objdump should be used, just as the host version of the compiler was used to generate it. Of course, it is possible that we could be missing some specific reason that you chose to look for a target tool. Thanks in advance and keep up the great work! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
Description: Unbreak cross-compilation: we do not need target tools. Forwarded: no Author: Helmut Grohne <hel...@subdivi.de> Bug-Debian: https://bugs.debian.org/972427 Last-Update: 2020-10-25 --- a/configure.in +++ b/configure.in @@ -113,7 +113,7 @@ AC_SYS_LARGEFILE AC_STRUCT_ST_BLKSIZE -AC_CHECK_TARGET_TOOLS(OBJDUMP,gobjdump objdump) +AC_CHECK_TOOLS(OBJDUMP,gobjdump objdump) AC_HEADER_ASSERT AC_CHECK_LIB(pthread, pthread_mutex_init)
signature.asc
Description: PGP signature
