Did the 2.0.0 tarball get created multiple times? about austin HOT 3 CLOSED

I've started a CI run with the new sha and a hack for the argparse.c issue. It'll fail initially because homebrew rejects changes where the SHA is updated without the URL changing but the project maintainers can override that: Homebrew/homebrew-core#67648

from austin.

Thanks for reporting this! I was afraid something like this would happen at some point so I changed the travis job to publish on tag rather than on any push to master. Before I did this though there must have been some new commits on master that retriggered the generation of the release artifacts. This is now unlikely to happen again in the future.

I plan on releasing version 2.1.0 relatively soon, which I presume would "fix" this issue, but perhaps it would be best to have version 2.0.0 in Homebrew working again regardless?

from austin.

Thanks for looking into it. I'll see about getting the homebrew formula building again.

It looks like there are other compile issues for MacOS 11 that need to be sorted out:

argparse.c:62:1: error: static declaration of 'strtonum' follows non-static declaration
strtonum(char * str, long * num) {
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/stdlib.h:351:2: note: previous declaration is here
        strtonum(const char *__numstr, long long __minval, long long __maxval, const char **__errstrp)
        ^
argparse.c:453:67: error: too few arguments to function call, expected 4, have 2
      strtonum((char *) arg, (long *) &(pargs.t_sampling_interval)) == 1 ||
      ~~~~~~~~                                                    ^

from austin.