Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 2261766

Summary: usd: FTBFS in Fedora rawhide/f40
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: usdAssignee: Ben Beasley <code>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: code, luya_tfz, negativo17
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: usd-23.11-10.fc41 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-03 13:54:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2269811    
Bug Blocks: 2231791    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2024-01-29 22:41:33 UTC
usd failed to build from source in Fedora rawhide/f40

https://koji.fedoraproject.org/koji/taskinfo?taskID=112453597


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
Please fix usd at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
usd will be orphaned. Before branching of Fedora 41,
usd will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Fedora Release Engineering 2024-01-29 22:41:38 UTC
Created attachment 2013756 [details]
build.log

Comment 2 Fedora Release Engineering 2024-01-29 22:41:43 UTC
Created attachment 2013757 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2024-01-29 22:41:46 UTC
Created attachment 2013758 [details]
state.log

Comment 4 Ben Beasley 2024-03-19 15:21:07 UTC
There were some problems with USD’s dependencies, but it looks like they are resolved now.

F41 scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=115166346
F40 scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=115166349

Comment 5 Ben Beasley 2024-03-19 17:47:05 UTC
Reopening, because shortly after the successful scratch build, I tried a real build, and it failed in F40 (not F41).

https://koji.fedoraproject.org/koji/taskinfo?taskID=115169545

/usr/bin/ld: warning: libtbb.so.12, needed by /usr/lib64/libOpenImageIO.so, may conflict with libtbb.so.2
/usr/bin/ld: /usr/lib64/libgdal.so.34: undefined reference to `arrow::KeyValueMetadata::Contains(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const'
/usr/bin/ld: /usr/lib64/libgdal.so.34: undefined reference to `arrow::KeyValueMetadata::Get(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const'
collect2: error: ld returned 1 exit status

The above is due to the unintended ABI break in libarrow, bug 2269811, which is now affecting F40 due to https://bodhi.fedoraproject.org/updates/FEDORA-2024-e075b0f5cf and https://bodhi.fedoraproject.org/overrides/libarrow-15.0.2-1.fc40.

Comment 6 Fedora Update System 2024-04-03 13:50:17 UTC
FEDORA-2024-be3463bb24 (luxcorerender-2.7-0.16.beta1.fc41, OpenImageIO-2.5.7.0-2.fc41, and 3 more) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-be3463bb24

Comment 7 Fedora Update System 2024-04-03 13:54:21 UTC
FEDORA-2024-be3463bb24 (luxcorerender-2.7-0.16.beta1.fc41, OpenImageIO-2.5.7.0-2.fc41, and 3 more) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.