On 2024-08-15 13:37, Sam James wrote: > More annoying to have an error suppressed that is not obvious to debug, > especially if one isn't aware of this behaviour.
By default (unless you pass --silent), libtool prints the compiler commands it is executing, which includes the output redirection to /dev/null on the second command. So if the second invocation crashes, you can just copy+paste the last command line libtool printed without the redirection to /dev/null to see the output, and now you are aware of this behaviour, right? Cheers, Nick
