> On Sep 15, 2022, at 12:47 PM, Rob Gowin <r...@gowin.net> wrote:
> 
> There are suggestions on the interweb that adding -DNS_FORMAT_ARGUMENT(A)= to 
> compiler options will work around this problem.
> 

That seems unwise.

https://stackoverflow.com/questions/18449176/objective-c-format-string-is-not-a-string-literal-potentially-insecure-warn
Objective-C: "format string is not a string literal (potentially insecure)" 
warning with macro
stackoverflow.com
 provides a detailed explanation of what that NS_FORMAT_ARGUMENTS is for. I 
don't see anything in gnc-filepath-utils.cpp that would incite that warning.

https://discuss.tvm.apache.org/t/macos-latest-command-line-tools-clt-crashes-build-for-metal/12413
 advocates editing NSBundle.h to change the return type of 
localizedAttributedStringForKey: from NSAttributedString* to NSString*. That 
also seems unwise.

https://forum.arduino.cc/t/build-question-about-old-node-module-requested-by-package-json/936228reports
 that the user was able to make the error go away by upgrading his OS to 
macOS12. I didn't see the host macOS version mentioned on any of the other 
reports of this failure, but it wouldn't be the first time that I've 
encountered problems with building using a newer MacOSX SDK than the running 
macOS version. One can get older versions of Xcode and the command line tools 
at https://developer.apple.com/downloads; you have to sign in with your Apple 
ID. I don't know if you have to be an enrolled developer too.

Regards,
John Ralls



_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to