Re: Failed: phase compiling: r-base34-3.4.4-1 failed

Robert Wyatt <[email protected]>
Newsgroups gmane.os.apple.fink.beginners
Organization http://bentones.us/
Message-ID <[email protected]>
Just to add a data point, yes, it still fails with the current CLI tools 
(although I didn't try it with the Beta version... would you like me to?):

- checking for Xcode version... 11.2
- checking for Xcode CLI tools version... 11.2.0.0.1.1571444319

Package manager version: 0.45.0
Distribution version: selfupdate-git Fri Nov  8 12:27:10 2019, 10.14.5, 
x86_64

* My machine is a: uname -m; sysctl hw.model; sysctl 
machdep.cpu.brand_string
x86_64
hw.model: Macmini6,2
machdep.cpu.brand_string: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz

installing 'sysdata.rda'
dyld: lazy symbol binding failed: Symbol not found: _timespec_get
   Referenced from: 
/sw/src/fink.build/r-base35-3.5.3-1/R-3.5.3/lib/libR.dylib
   Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _timespec_get
   Referenced from: 
/sw/src/fink.build/r-base35-3.5.3-1/R-3.5.3/lib/libR.dylib
   Expected in: /usr/lib/libSystem.B.dylib

/bin/sh: line 1: 49712 Done                    echo 
"tools:::sysdata2LazyLoadDB(\"./R/sysdata.rda\",\"../../../library/tools/R\")"
      49713 Abort trap: 6           | R_DEFAULT_PACKAGES=NULL LC_ALL=C 
R_ENABLE_JIT=0 TZ=UTC ../../../bin/R --vanilla --slave
make[4]: *** [sysdata] Error 134




John Wiggins via Fink-beginners wrote:
> It may well be because of the few applications I compile with fink, but I have the latest release Xcode (11.2) and Command Line Tools (11.0) and have run "update-all" without error.
> I do get this fink warning when I run update-all:
> 	WARNING: Xcode.app version (11.2) and Xcode Command Line Tools version (11.0)
> 	may not be compatible.
> 	You may experience build errors.
>
> I do plan to use installed the corresponding CLT when it is no longer beta, or if I get a compile error I’ll update to the latest beta is available, as you do.
> On one of the Apple developer lists I did ask, and someone responded that if the CLT release does not appear right after a new XC release, then other folks generally assume it is alright stay with release-level of each even when the numbers do not match.
>
> tks,
> jw
>
>
>> On Nov 5, 2019, at 4:52 AM, Hanspeter Niederstrasser <[email protected]> wrote:
>>
>> On 11/5/19 1:54 AM, Tom Liehe via Fink-beginners wrote:
>>> My method of dealing with this has been 1) sudo rm /Library/Developer/CommandLineTools 2) xcode-select —install
>>> Fink still complains, but otherwise seems to work:
>>> WARNING: Xcode.app version (11.2) and Xcode Command Line Tools version (11.0)
>>> may not be compatible. You may experience build errors.
>>> Whan an install fails, the message at the end says:
>>> Xcode.app: 11.2
>>> Xcode command-line tools: 11.0.0.0.1.1567737322
>>> So the question is: how do I get version 11.2 of the command line tools? Or is it ok as is?
>> I'm not sure if 'xcode-select -install' installs beta versions of the command line tools. I always just fetch the latest installers from developer.apple.com. I currently have Xcode.app-11.2 and CLI-11.2beta2 with no apparent ill effects.
>>
>> Hanspeter
>>
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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



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