Re: Fink-beginners Digest, Vol 166, Issue 4

James Coyle via Fink-beginners <[email protected]>
Newsgroups gmane.os.apple.fink.beginners
Message-ID <[email protected]> 
I too cannot run fink update-all even though I’ve reinstalled the Command Line tools from the Apple web site, and agreed to the license. As with other users, the Command Line Tools aren’t being recognized.

The last post on this was more than ten days ago.  Was a fix provided in some other forum? Thanks

> On Apr 5, 2020, at 5:19 PM, [email protected] wrote:
> 
> Send Fink-beginners mailing list submissions to
> 	[email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/fink-beginners
> or, via email, send a message with subject or body 'help' to
> 	[email protected]
> 
> You can reach the person managing the list at
> 	[email protected]
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Fink-beginners digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Fink not recognizing command line tools even after
>      postinstall script (Hanspeter Niederstrasser)
>   2. Re: Fink not recognizing command line tools even after
>      postinstall script (Lebois, Lauren Ann Mcdonough)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sun, 5 Apr 2020 09:03:17 -0500
> From: Hanspeter Niederstrasser <[email protected]>
> To: David Axler <[email protected]>, fink-beginners
> 	<[email protected]>, "Lebois, Lauren Ann Mcdonough"
> 	<[email protected]>
> Subject: Re: [Fink-beginners] Fink not recognizing command line tools
> 	even after postinstall script
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 4/4/20 9:43 PM, David Axler wrote:
>>> ?sudo xcodebuild -licence? will be rejected.
>> It needs to be ?sudo xcodebuild -license?
> 
>> 
>>> On Apr 4, 2020, at 4:29 PM, Alexander Hansen <[email protected]> wrote:
>>> 
>>> 
>>> 
>>>> On Apr 4, 2020, at 08:03, Hanspeter Niederstrasser <[email protected] <mailto:[email protected]>> wrote:
>>>> 
>>>> On 4/3/20 8:58 PM, Lebois, Lauren Ann Mcdonough wrote:
>>>>> Hello Fink Gurus,
>>>>> I've recently updated my macOS and Developer Tools, and reinstalled Fink, but when I go to use the command 'fink selfupdate-rsync', I get the following error:
>>>>> Before changing your selfupdate method to 'rsync', you must install
>>>>> the Xcode Command Line Tools package from
>>>>> http://developer.apple.com <http://developer.apple.com/> (after free registration),
>>>>> or via the Downloads tab of the Xcode Preferences.
>>>>> Failed: Selfupdate method 'rsync' cannot be used
>>>>> However, I've already installed the Xcode Command Line Tools package... it seems Fink doesn't recognize the change.  Per the Fink FAQ, to address this, I tried running:
>>>>> /sw/lib/fink/postinstall.pl
>>>>> However, I now get the following error:
>>>>> ~ % /sw/lib/fink/postinstall.pl
>>>>> Checking system... i386-apple-darwin18.7.0
>>>>> Use of uninitialized value $gcc in regexp compilation at /sw/lib/perl5/Fink/Services.pm line 1348.
>>>>> Use of uninitialized value $gcc in concatenation (.) or string at /sw/lib/perl5/Fink/Bootstrap.pm line 164.
>>>>> This system was not released at the time this Fink release was made.
>>>>> Prerelease versions of Mac OS X might work with Fink, but there are no guarantees.
>>>>> can't write temporary file: Permission denied at /sw/lib/perl5/Fink/Config.pm line 617.
>>>>> In case it is helpful my Mac OS version is Mojave Version 10.14.6.  My X Code version is 10.3.
>>>> 
>>>> That's a mistake in the FAQ (Q5.24 presumbably). The instructions to run postinstall.pl were probably valid long ago but forgotten to be updated when things changed. For some time now, Apple keeps breaking how the Command Line Tools are registered every single time the OS is updated. You need to actually reinstall the Command Line Tools. Easiest method is to redownload from developer.apple.com <http://developer.apple.com/> (make sure to match the XCode.app version).
>>>> 
>>>> Hanspeter
>>>> 
>>> 
>>> Yeah, my recollection is that using postinstall.pl for a fix was for a problem from around 10.5 or 10.6.  For modern Xcode Command Line Tools versions, using ?sudo xcode-select --install ? (provided that you have Xcode.app installed) will _sometimes_ download a new version of the command-line tools when you?ve updated the OS.  This seems not always to work, however, and Hanspeter?s advice works under essentially all circumstances.
>>> 
>>> One other thing to note is that you will need to run ?sudo xcodebuild -licence? after installing the Command Line Tools so that root and fink?s fink-bld user can utilize them.  If you actually installed the Command Line Tools after updating your OS, this is likely to solve your problem.
> 
> I've updated the FAQ with the discussion from this thread.
> 
> http://www.finkproject.org/faq/usage-fink.php?phpLang=en#lost-command-line-tools
> 
> Hanspeter
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Sun, 5 Apr 2020 22:26:35 +0000
> From: "Lebois, Lauren Ann Mcdonough" <[email protected]>
> To: David Axler <[email protected]>, fink-beginners
> 	<[email protected]>, Hanspeter Niederstrasser
> 	<[email protected]>
> Subject: Re: [Fink-beginners] Fink not recognizing command line tools
> 	even after postinstall script
> Message-ID:
> 	<BL0PR04MB64848133D91B3B63958E1FE58EC50@BL0PR04MB6484.namprd04.prod.outlook.com>
> 	
> Content-Type: text/plain; charset="windows-1252"
> 
> Hi all,
> 
> Thank you so much!  Unfortuantely, I'm still stuck.  As advised, I've completed a manual download of the Xcode Command Line Tools package from the developer.apple.com website (specifically this package to match my macos version and xcode version: Command_Line_Tools_macOS_10.14_for_Xcode_10.3.dmg).  After opening the dmg file and a supposedly successful install based on the installer.  I've run the command "sudo xcodebuild -license" and typed 'agree' to the license, but I still get the following error when I try to update fink:
> 
> % fink selfupdate-rsync
> 
> Please note: the simple command 'fink selfupdate' should be used for routine
> updating; you only need to use a command like 'fink selfupdate-cvs' or 'fink
> selfupdate --method=rsync' if you are changing your update method.
> 
> Before changing your selfupdate method to 'rsync', you must install
> the Xcode Command Line Tools package from
> http://developer.apple.com (after free registration),
> or via the Downloads tab of the Xcode Preferences.
> Failed: Selfupdate method 'rsync' cannot be used
> 
> Any advice appreciated.
> Best,
> Lauren
> 
> 
> 
> 
> _____________________________________________________
> Lauren A. M. Lebois, PhD
> Director of Neuroimaging, Dissociative Disorders and Trauma Research Program<http://www.ddtrp.com><http://www.mcleanhospital.org/research-programs/dissociative-disorders-and-trauma-research-program?key=0>
> Instructor in Psychiatry, <http://www.mcleanhospital.org/research-programs/neurobiology-fear-laboratory> Ressler Neurobiology of Fear Lab<http://www.resslerlab.com/>
> McLean Hospital / Harvard Medical School
> 115 Mill St
> Oaks Building room 330
> Belmont, MA 02478
> email: [email protected]
> phone: 617.855.3166
> 
> ________________________________
> From: Hanspeter Niederstrasser <[email protected]>
> Sent: Sunday, April 5, 2020 10:03 AM
> To: David Axler <[email protected]>; fink-beginners <[email protected]>; Lebois, Lauren Ann Mcdonough <[email protected]>
> Subject: Re: [Fink-beginners] Fink not recognizing command line tools even after postinstall script
> 
>        External Email - Use Caution
> 
> On 4/4/20 9:43 PM, David Axler wrote:
>>> ?sudo xcodebuild -licence? will be rejected.
>> It needs to be ?sudo xcodebuild -license?
> 
>> 
>>> On Apr 4, 2020, at 4:29 PM, Alexander Hansen <[email protected]> wrote:
>>> 
>>> 
>>> 
>>>> On Apr 4, 2020, at 08:03, Hanspeter Niederstrasser <[email protected] <mailto:[email protected]>> wrote:
>>>> 
>>>> On 4/3/20 8:58 PM, Lebois, Lauren Ann Mcdonough wrote:
>>>>> Hello Fink Gurus,
>>>>> I've recently updated my macOS and Developer Tools, and reinstalled Fink, but when I go to use the command 'fink selfupdate-rsync', I get the following error:
>>>>> Before changing your selfupdate method to 'rsync', you must install
>>>>> the Xcode Command Line Tools package from
>>>>> http://developer.apple.com <http://developer.apple.com/> (after free registration),
>>>>> or via the Downloads tab of the Xcode Preferences.
>>>>> Failed: Selfupdate method 'rsync' cannot be used
>>>>> However, I've already installed the Xcode Command Line Tools package... it seems Fink doesn't recognize the change.  Per the Fink FAQ, to address this, I tried running:
>>>>> /sw/lib/fink/postinstall.pl
>>>>> However, I now get the following error:
>>>>> ~ % /sw/lib/fink/postinstall.pl
>>>>> Checking system... i386-apple-darwin18.7.0
>>>>> Use of uninitialized value $gcc in regexp compilation at /sw/lib/perl5/Fink/Services.pm line 1348.
>>>>> Use of uninitialized value $gcc in concatenation (.) or string at /sw/lib/perl5/Fink/Bootstrap.pm line 164.
>>>>> This system was not released at the time this Fink release was made.
>>>>> Prerelease versions of Mac OS X might work with Fink, but there are no guarantees.
>>>>> can't write temporary file: Permission denied at /sw/lib/perl5/Fink/Config.pm line 617.
>>>>> In case it is helpful my Mac OS version is Mojave Version 10.14.6.  My X Code version is 10.3.
>>>> 
>>>> That's a mistake in the FAQ (Q5.24 presumbably). The instructions to run postinstall.pl were probably valid long ago but forgotten to be updated when things changed. For some time now, Apple keeps breaking how the Command Line Tools are registered every single time the OS is updated. You need to actually reinstall the Command Line Tools. Easiest method is to redownload from developer.apple.com <http://developer.apple.com/> (make sure to match the XCode.app version).
>>>> 
>>>> Hanspeter
>>>> 
>>> 
>>> Yeah, my recollection is that using postinstall.pl for a fix was for a problem from around 10.5 or 10.6.  For modern Xcode Command Line Tools versions, using ?sudo xcode-select --install ? (provided that you have Xcode.app installed) will _sometimes_ download a new version of the command-line tools when you?ve updated the OS.  This seems not always to work, however, and Hanspeter?s advice works under essentially all circumstances.
>>> 
>>> One other thing to note is that you will need to run ?sudo xcodebuild -licence? after installing the Command Line Tools so that root and fink?s fink-bld user can utilize them.  If you actually installed the Command Line Tools after updating your OS, this is likely to solve your problem.
> 
> I've updated the FAQ with the discussion from this thread.
> 
> http://www.finkproject.org/faq/usage-fink.php?phpLang=en#lost-command-line-tools
> 
> Hanspeter
> 
> 
> The information in this e-mail is intended only for the person to whom it is
> addressed. If you believe this e-mail was sent to you in error and the e-mail
> contains patient information, please contact the Partners Compliance HelpLine at
> http://www.partners.org/complianceline . If the e-mail was sent to you in error
> but does not contain patient information, please contact the sender and properly
> dispose of the e-mail.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> 
> ------------------------------
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> Fink-beginners mailing list
> [email protected]
> http://news.gmane.org/gmane.os.apple.fink.beginners
> 
> ------------------------------
> 
> End of Fink-beginners Digest, Vol 166, Issue 4
> **********************************************



_______________________________________________
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
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.