Opened 2 years ago

Closed 2 years ago

#65940 closed defect (invalid)

Configuring qt5-qtbase failure under Monterey Intel

Reported by: cgilles (HumanDynamo) Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: qt5-qtbase

Description

Target : macbook pro 2015 Intel with MacOS Monterey 12.5.1 and xcode 14.0.1

Building a fresh macport env for digiKam fail at qt5-qtbase:

--->  Computing dependencies for qt5-qtbase
--->  Dependencies to be installed: double-conversion
--->  Fetching distfiles for double-conversion
--->  Attempting to fetch double-conversion-3.2.1.tar.gz from https://distfiles.macports.org/double-conversion
--->  Verifying checksums for double-conversion
--->  Extracting double-conversion
--->  Configuring double-conversion
--->  Building double-conversion
--->  Staging double-conversion into destroot
--->  Installing double-conversion @3.2.1_0
--->  Activating double-conversion @3.2.1_0
--->  Cleaning double-conversion
--->  Fetching distfiles for qt5-qtbase
--->  Attempting to fetch qtbase-everywhere-opensource-src-5.15.6.tar.xz from https://distfiles.macports.org/qt5
--->  Verifying checksums for qt5-qtbase
--->  Extracting qt5-qtbase
--->  Applying patches to qt5-qtbase
--->  Configuring qt5-qtbase
Error: Failed to configure qt5-qtbase: configure failure: command execution failed
Error: See /opt/digikam.org.x86_64/var/macports/logs/_opt_digikam.org.x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qtbase/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port qt5-qtbase failed

Log is attached for investigations.

Attachments (1)

main.log.zip (25.9 KB) - added by cgilles (HumanDynamo) 2 years ago.

Download all attachments as: .zip

Change History (12)

Changed 2 years ago by cgilles (HumanDynamo)

Attachment: main.log.zip added

comment:1 Changed 2 years ago by cgilles (HumanDynamo)

For more details of the process used to build the digiKam macports env, Look the scripts here:

https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/macports

The scripts are robust and used since many years now. All previous dependencies compile fine and stop at Qt5-qtbase:

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/01-build-macports.sh#L294

comment:2 Changed 2 years ago by cgilles (HumanDynamo)

Note : I migrated my Macbook pro from Big Sur to Monterey one day ago with Xcode updates. I cleaned all Macports install and re-install all from scratch with the script. The last stable Macports is used now.

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

Owner: set to MarcusCalhoun-Lopez
Status: newassigned

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

:debug:sysinfo SDK 12
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.13
:warn:clean The macOS 12 SDK does not appear to be installed. Ports may not build correctly.

Outdated CLTs? ProblemHotlist#reinstall-clt

Or if you intended to use a 10.13 SDK, that hasn't been configured correctly.

comment:5 Changed 2 years ago by cgilles (HumanDynamo)

The 10.13 SDK is intented of course, to have a binary compatibility with previous MacOS version. The 10.13 SDK is of course installed :

# pwd
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
# ls -al
total 0
drwxr-xr-x  6 root  wheel  192  5 oct 19:56 .
drwxr-xr-x  6 root  wheel  192 14 sep 14:29 ..
drwxr-xr-x  7 root  wheel  224 14 sep 14:54 MacOSX.sdk
drwxr-xr-x  5 root  wheel  160  5 oct 19:56 MacOSX10.13.sdk
lrwxr-xr-x  1 root  wheel   10  5 oct 18:17 MacOSX12.3.sdk -> MacOSX.sdk
lrwxr-xr-x  1 root  wheel   10  5 oct 18:17 MacOSX12.sdk -> MacOSX.sdk

And configured in XCode :

# pwd 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform
# cat Info.plist 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>AdditionalInfo</key>
	<dict>
		<key>BuildMachineOSBuild</key>
		<string>$(MAC_OS_X_PRODUCT_BUILD_VERSION)</string>
		<key>CFBundleSupportedPlatforms</key>
		<array>
			<string>MacOSX</string>
		</array>
		<key>DTCompiler</key>
		<string>$(GCC_VERSION)</string>
		<key>DTPlatformBuild</key>
		<string>$(PLATFORM_PRODUCT_BUILD_VERSION)</string>
		<key>DTPlatformName</key>
		<string>macosx</string>
		<key>DTPlatformVersion</key>
		<string>12.3</string>
		<key>DTSDKBuild</key>
		<string>$(SDK_PRODUCT_BUILD_VERSION)</string>
		<key>DTSDKName</key>
		<string>$(SDK_NAME)</string>
		<key>DTXcode</key>
		<string>$(XCODE_VERSION_ACTUAL)</string>
		<key>DTXcodeBuild</key>
		<string>$(XCODE_PRODUCT_BUILD_VERSION)</string>
		<key>LSMinimumSystemVersion</key>
		<string>$($(DEPLOYMENT_TARGET_SETTING_NAME))</string>
	</dict>
	<key>CFBundleDevelopmentRegion</key>
	<string>English</string>
	<key>CFBundleIdentifier</key>
	<string>com.apple.platform.macosx</string>
	<key>CFBundleName</key>
	<string>macOS Platform</string>
	<key>CFBundleShortVersionString</key>
	<string>12.3</string>
	<key>CFBundleVersion</key>
	<string>12.3</string>
	<key>DefaultProperties</key>
	<dict>
		<key>COMPRESS_PNG_FILES</key>
		<string>NO</string>
		<key>DEFAULT_COMPILER</key>
		<string>com.apple.compilers.llvm.clang.1_0</string>
		<key>DEPLOYMENT_TARGET_SETTING_NAME</key>
		<string>MACOSX_DEPLOYMENT_TARGET</string>
		<key>EMBEDDED_PROFILE_NAME</key>
		<string>embedded.provisionprofile</string>
		<key>STRIP_PNG_TEXT</key>
		<string>NO</string>
	</dict>
	<key>Description</key>
	<string>macOS</string>
	<key>FamilyIdentifier</key>
	<string>macosx</string>
	<key>FamilyName</key>
	<string>macOS</string>
	<key>Icon</key>
	<string>Icon.icns</string>
	<key>Identifier</key>
	<string>com.apple.platform.macosx</string>
	<key>MinimumSDKVersion</key>
	<string>10.13</string>                  <<<<<<<<======== !!!!!!!
	<key>Name</key>
	<string>macosx</string>
	<key>Type</key>
	<string>Platform</string>
	<key>Version</key>
	<string>12.3</string>
</dict>
</plist>

See the details of configuration in scripts:

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/config.sh#L23

Gilles

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

Well, macosx_sdk_version clearly hasn't been set to that in macports.conf.

comment:7 Changed 2 years ago by cgilles (HumanDynamo)

Oh, so i can install the MacOS SDK directy with macport instead to do it with my script ?

https://ports.macports.org/port/MacOSX10.13.sdk

comment:8 Changed 2 years ago by cgilles (HumanDynamo)

In fact instead using "macosx_sdk_version" we use since a very long time "macosx_deployment_target":

https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/01-build-macports.sh#L204

comment:9 Changed 2 years ago by cgilles (HumanDynamo)

Ok, adding "macosx_sdk_version" do the job in macports.conf.

https://invent.kde.org/graphics/digikam/-/commit/18e206e74994301a1c241b01896d1b91e45ebc10

qt5-qtbase compile fine now. The rest of macports continue to compile. If i found another dysfunction, i will open a new file.

Please close this file, and thanks for your support

Best Gilles Caulier

comment:10 in reply to:  8 Changed 2 years ago by jmroot (Joshua Root)

Replying to cgilles:

In fact instead using "macosx_sdk_version" we use since a very long time "macosx_deployment_target":

Those are two different settings that do different things. It sounds like you want to set both.

comment:11 in reply to:  9 Changed 2 years ago by jmroot (Joshua Root)

Resolution: invalid
Status: assignedclosed

Replying to cgilles:

Ok, adding "macosx_sdk_version" do the job in macports.conf.

https://invent.kde.org/graphics/digikam/-/commit/18e206e74994301a1c241b01896d1b91e45ebc10

qt5-qtbase compile fine now. The rest of macports continue to compile. If i found another dysfunction, i will open a new file.

Please close this file, and thanks for your support

OK, closing.

Note: See TracTickets for help on using tickets.