So GNU libtool and the whole autotools suite does seem to help a lot with complicated builds that need auto-detection of all sorts of things, but they can also be an exercise in totally obtuse errors, bizarre scripting, and frustration. I suppose all build systems really share those qualities in some respect. One thing that I’ve run into with puredata/pd-extended is this strange error dump from libtool that seems to be unfindable via search engines. Here’s a snippet:
../libtool: line 844: X--tag=CC: command not found ../libtool: line 844: X--tag=CC: command not found ../libtool: line 844: X--tag=CC: command not found ../libtool: line 844: X--tag=CC: command not found ../libtool: line 877: libtool: ignoring unknown tag : command not found ../libtool: line 877: libtool: ignoring unknown tag : command not found ../libtool: line 844: X--mode=compile: command not found ../libtool: line 844: X--mode=compile: command not found ../libtool: line 877: libtool: ignoring unknown tag : command not found ../libtool: line 877: libtool: ignoring unknown tag : command not found ../libtool: line 844: X--mode=compile: command not found ../libtool: line 844: X--mode=compile: command not found ../libtool: line 1011: *** Warning: inferring the mode of operation is deprecated.: command not found
Why on earth did libtool prepend that ‘X’ to the command line options and try to run them as commands? WTF? This has baffled me to no end… until I realized its because a one version of libtool does not like files generated by a different version of libtool! Arg. I solved this by deleting the m4 folder in my project, then restoring what files are needed in that folder by doing git reset --hard
Blog of Annoying Technical Details 