Opened 2 years ago

Last modified 2 years ago

#65172 assigned defect

GPXSee Error but builds

Reported by: dershow Owned by: sikmir (Nikolay Korotkiy)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: GPXSee

Description

I just upgraded GPXSee from 10.3_0 to 10.7_0 and the configure gave an error, but the build continued and the application seems to run OK. I thought that it was worth reporting despite the fact that it does seem to complete:

--->  Computing dependencies for GPXSee
--->  Fetching archive for GPXSee
--->  Attempting to fetch GPXSee-10.7_0.darwin_20.x86_64.tbz2 from https://packages.macports.org/GPXSee
--->  Attempting to fetch GPXSee-10.7_0.darwin_20.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/GPXSee
--->  Attempting to fetch GPXSee-10.7_0.darwin_20.x86_64.tbz2 from https://mse.uk.packages.macports.org/GPXSee
--->  Fetching distfiles for GPXSee
--->  Attempting to fetch GPXSee-10.7.tar.gz from https://distfiles.macports.org/GPXSee
--->  Verifying checksums for GPXSee
--->  Extracting GPXSee
--->  Applying patches to GPXSee
--->  Configuring GPXSee
xcodebuild: error: SDK "macosx11" cannot be located.
xcrun: error: sh -c '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk macosx11 -find ld 2> /dev/null' failed with exit code 16384: (null) (errno=No such file or directory)
xcrun: error: unable to find utility "ld", not a developer tool or in PATH
--->  Building GPXSee
--->  Staging GPXSee into destroot
--->  Installing GPXSee @10.7_0
--->  Cleaning GPXSee
--->  Computing dependencies for GPXSee
--->  Deactivating GPXSee @10.3_0
--->  Cleaning GPXSee
--->  Activating GPXSee @10.7_0
--->  Cleaning GPXSee
--->  Uninstalling GPXSee @10.3_0
--->  Cleaning GPXSee

Change History (2)

comment:1 Changed 2 years ago by jmroot (Joshua Root)

Owner: set to sikmir
Status: newassigned

This output is probably being generated by the qmake5 portgroup.

comment:2 Changed 2 years ago by sikmir (Nikolay Korotkiy)

With last update (https://github.com/macports/macports-ports/pull/15046) use_xcode yes was added, it should fix this error. At least I don't see such error on my macos 10.13.

Note: See TracTickets for help on using tickets.