Re: Failed: phase compiling: xcode-0-0 failed

> On Aug 16, 2021, at 12:00 PM, Heinz Nabielek via Fink-beginners <[email protected]> wrote:
> 
> I HAVE A PERFECTLY GOOD XCODE 12.1 TOGETHER WITH THE COMMAND LINE TOOLS INSTALLED AND PERFECTLY GOOD WORKING.
> WHY ON EARTH DOES FINK COMPLAIN???
> 
> HEINZ
> 
> 
> The following 3 packages will be installed or updated:
> fink-package-precedence libopenjp2.7 libopenjp2.7-shlibs
> The following additional package will be installed:
> xcode
> 
> ### execution of /tmp/fink.f8kUB failed, exit code 1
> ### execution of /tmp/fink.EPPWE failed, exit code 1
> Removing runtime build-lock...
> Removing build-lock package...
> /opt/sw/bin/dpkg-lockwait -r fink-buildlock-xcode-0-0
> (Reading database ... 49285 files and directories currently installed.)
> Removing fink-buildlock-xcode-0-0 ...
> Failed: phase compiling: xcode-0-0 failed
> 
> Package manager version: 0.45.99.git
> Distribution version: selfupdate-rsync Mon Aug 16 20:49:18 2021, 10.15, x86_64
> Trees: local/main stable/main
> Xcode.app: 12.1
> No recognized Xcode CLI installed
> Max. Fink build jobs:  1
> 
> _______________________________________________
> Fink-beginners mailing list
> [email protected]
> List archive:
> https://sourceforge.net/p/fink/mailman/fink-users/
> Subscription management:
> https://lists.sourceforge.net/lists/listinfo/fink-beginners

One of the best ways to alienate people who want to help you is to send all-caps messages.  Doubly so when you’re “yelling” at UNPAID VOLUNTEERS for something that YOU DIDN”T PAY FOR.

Here’s what’s going on in more detail than you want.  I don’t really care.
1. Back when Xcode included command-line tools, we started using an “xcode” virtual package to indicate the version of that.  I believe that the test we used is the same as we use for the “xcode.app” virtual package now.
2. When the Command-Line Tools split off from Xcode we elected to persist using “xcode” to indicate the command-line-tools version.
3.  Unfortunately, at that time, there wasn’t a good command output that gave the command-line tools package version other than to check the receipt.  Now the clang compiler version is approximately the same as the Command-Line Tools package version, but that wasn’t the case originally.  In hindsight, we shouldn’t have done that, but I didn’t want to change the established behavior.
4.  Apple is really bad about handling packages, so every OS update breaks the command-line tools receipt detection.  Other things, too.
5.  Fink is an unmonetized VOLUNTEER PROJECT, and we have the equivalent of about 1 full-time person at most to fix stuff.  Probably less than that.

Yes, this is annoying.  You can work around it by using “fink dumpinfo -finfofile” to get the names of any packages that cause this problem and then remove the “xcode” dependency.  Then use “fink index -f” to rebuild the package cache.  This is less of a hassle than reinstalling the command-line tools, probably. 

The long-term fix would be for us to update fink to use a more robust detection mechanism, like maybe just the clang output.

—akh

_______________________________________________
Fink-beginners mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-beginners