Lenore,

Depending on if you need to use R soon or not, perhaps downloading the prebuilt version from the R site [r-project.org] would work for you? I can understand if trying to get the macports version to work can be an itch to scratch. :-)

I've been using the prebuilt version directly from the r-project for many years. I haven't noticed anything that it didn't do properly.

B.

On 27.04.2020 08:00, macports-users-requ...@lists.macports.org wrote:

Date: Mon, 27 Apr 2020 06:19:05 -0500
From: Ryan Schmidt <ryandes...@macports.org>
To: Lenore Horner <lenorehor...@sbcglobal.net>
Cc: MacPorts Users <macports-users@lists.macports.org>
Subject: Re: R-app
Message-ID: <082123f6-9d5c-48b6-ba41-52ed8f863...@macports.org>
Content-Type: text/plain;       charset=utf-8



On Apr 26, 2020, at 07:56, Lenore Horner wrote:

I filled a ticket 2 weeks ago with log because R-app doesn’t build.

Looks like you're referring to https://trac.macports.org/ticket/60345 which 
I've closed as a duplicate of https://trac.macports.org/ticket/59482.


I’m afraid that understanding what the log is telling me - beyond that there 
are lots of files it can’t find/ can’t write to - is over my head.  Is R-app 
permanently broken or is there some way other than filing a ticket to get help 
with getting it to compile?  I’m on 10.14.6.

The first error I see in the log is
:info:build 2020-04-11 09:57:05.434 xcodebuild[30927:709640] Error 
Domain=com.apple.CoreSimulator.SimError Code=159 "Unable to determine SimDeviceSet, 
set_path=/opt/local/var/macports/home/Library/Developer/CoreSimulator/Devices" 
UserInfo={NSLocalizedDescription=Unable to determine SimDeviceSet, 
set_path=/opt/local/var/macports/home/Library/Developer/CoreSimulator/Devices, 
NSUnderlyingError=0x7fd651108ff0 {Error Domain=NSPOSIXErrorDomain Code=12 "Cannot allocate 
memory" UserInfo={NSLocalizedFailureReason=Allocation or initialization failed., 
NSLocalizedDescription=Failed to initialize simulator device set.}}}

We don't need iOS/iPadOS/tvOS/watchOS simulators for MacPorts since we're only 
building for macOS. It's baffling why xcodebuild wants to have anything to do 
with the simulators when they're not needed nor wanted. Hopefully this is just 
a warning you can ignore.


But then there are a series of can’t open or can’t create files starting with
:info:build 2020-04-11 09:57:05.506 xcodebuild[30927:709638] [MT] IDELogStore: 
Failed to open log store at 
/opt/local/var/macports/home/Library/Developer/Xcode/DerivedData/R-cowjbsghamrjwebkaacwdxnbihql/Logs/Build
:info:build 2020-04-11 09:57:05.506 xcodebuild[30927:709638] [MT] IDELogStore: Failed to 
open Build log store: Error Domain=IDEFoundationErrorDomain Code=1 "Unable to create 
log store directory at 
'/opt/local/var/macports/home/Library/Developer/Xcode/DerivedData/R-cowjbsghamrjwebkaacwdxnbihql/Logs/Build':
 (513) You don’t have permission to save the file “Build” in the folder “Logs”." 
UserInfo={NSLocalizedDescription=Unable to create log store directory at 
'/opt/local/var/macports/home/Library/Developer/Xcode/DerivedData/R-cowjbsghamrjwebkaacwdxnbihql/Logs/Build':
 (513) You don’t have permission to save the file “Build” in the folder “Logs”.}. User 
info: {
:info:build     NSLocalizedDescription = "Unable to create log store directory at 
'/opt/local/var/macports/home/Library/Developer/Xcode/DerivedData/R-cowjbsghamrjwebkaacwdxnbihql/Logs/Build':
 (513) You don\U2019t have permission to save the file \U201cBuild\U201d in the folder 
\U201cLogs\U201d.";
:info:build }.

This sounds like the usual Xcode 10+ derived data problem. See 
https://trac.macports.org/ticket/57137. Don't know why nobody who's using Xcode 
10+ has developed a general fix for that yet.


And why is SnowLeopard coming in?
:info:build --- xcodebuild: WARNING: Configuration SnowLeopard64 is not in the 
project. Building default configuration.

The R-app portfile instructs xcodebuild to use a configuration called 
SnowLeopard64. No such configuration exists in this software (anymore; 
presumably one by that name used to exist; currently it seems to contain 
configurations named Lion64 and MLion64) so it builds whatever the default 
configuration of this Xcode project called is instead. The portfile should be 
changed to specify whatever the actual configuration name is, or if the default 
one is suitable then that line can just be removed.


Then I finally noticed a report error to apple line.  I’ll do that in a few 
moments.  But generally a ton of stuff seems to be going ok and then I start 
getting ibtool warnings and in particular complaints that building for older 
than 10.6 is not supported.  Since I’m on 10.14.6, something’s gone awry.

Yes the real error I think is:

error: Compiling for earlier than macOS 10.6 is no longer supported

Nothing has gone awry per se; it's just that the particular file about which 
xcodebuild shows this error message (the dutch translation of the syntax colors 
preference pane) (and perhaps other xib files as well) is configured to build 
for older than 10.6 (perhaps unintentionally, since the rest of the project 
seems to be meant for 10.7 and later), and the latest Xcode no longer allows 
building for older than 10.6. The xib file(s) will have to be adjusted by the 
software's developer (or, if they are unavailable, the portfile's maintainer) 
to specify a different (newer) deployment target, or ideally not to specify one 
at all (if that is possible for xib files) and let MacPorts do it. A newer 
version of R-app is available from the developer; the first step should 
probably be to try to update the port to that version.





------------------------------

Subject: Digest Footer

_______________________________________________
macports-users mailing list
macports-users@lists.macports.org
https://lists.macports.org/mailman/listinfo/macports-users

------------------------------

End of macports-users Digest, Vol 164, Issue 20
***********************************************

Reply via email to