Re: Success and Failure in macOS Big Sur

Chris Schram via Fink-users <[email protected]>
Newsgroups gmane.os.apple.fink.general
Organization Where the hell is Langlois, Oregon?
Message-ID <[email protected]>
On 2021-06-10, Daniel Macks <[email protected]> wrote:
> On 6/10/21, 3:09 AM, "Chris Schram via Fink-users" <[email protected]> wrote:
>     [slrn tries and tries, but eventually fails.]
>
>     /opt/sw/src/fink.build/slrn-1.0.3-2/slrn-1.0.3/src/misc.c:376:4: error: implicit declaration of function 'VA_COPY' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
>        VA_COPY(ap1, ap);
>        ^
>     1 error generated.
>     make[1]: *** [/opt/sw/src/fink.build/slrn-1.0.3-2/slrn-1.0.3/src/objs/misc.o] Error 1
>     make: *** [all] Error 2
>     ### execution of /usr/bin/make failed, exit code 2
>     ### execution of /tmp/fink.JvGdh failed, exit code 2
>     Removing runtime build-lock...
>     Removing build-lock package...
>     /opt/sw/bin/dpkg-lockwait -r fink-buildlock-slrn-1.0.3-2
>
> I just pushed a probable fix for this one. It's same version-revision, but now during the build you should see:
>
>  checking for an implementation of va_copy()... yes
>  checking for an implementation of __va_copy()... yes
>
> whereas during your failed build you probably saw those each as "no". I don't have Big Sur, so if slrn is still failing, make sure you have the latest changes (/opt/sw/fink/dists/stable/main/finkinfo/net/slrn.patch is 820 bytes not ~300 bytes) and we can try some other ideas.
>
> dan

Dan, That fixed it for Big Sur. Thanks for the quick turnaround.

-- 
[email protected] is a filtered spam magnet. Email replies may be lost.
You're better off replying to this newsgroup.



_______________________________________________
Fink-users mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.