Bug 1865487 - simde: FTBFS in Fedora rawhide/f33
Summary: simde: FTBFS in Fedora rawhide/f33
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: simde
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jun Aruga
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-08-03 21:10 UTC by Fedora Release Engineering
Modified: 2020-08-06 02:58 UTC (History)
1 user (show)

Fixed In Version: simde-0.0.0-5.git396e05c.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-06 02:58:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2020-08-03 21:10 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2020-08-03 21:10 UTC, Fedora Release Engineering
no flags Details
state.log (1017 bytes, text/plain)
2020-08-03 21:10 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2020-08-03 21:10:13 UTC
simde failed to build from source in Fedora rawhide/f33

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix simde 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,
simde will be orphaned. Before branching of Fedora 34,
simde will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source

Comment 1 Fedora Release Engineering 2020-08-03 21:10:15 UTC
Created attachment 1709624 [details]
build.log

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

Comment 2 Fedora Release Engineering 2020-08-03 21:10:16 UTC
Created attachment 1709625 [details]
root.log

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

Comment 3 Fedora Release Engineering 2020-08-03 21:10:17 UTC
Created attachment 1709626 [details]
state.log

Comment 4 Jun Aruga 2020-08-04 21:18:03 UTC
The error "clang-10: error: unsupported argument 'auto' to option 'flto='" happened on the following cmake command with modified %optflags.

```
# with flags
echo "=== 2.2. tests on clang with flags ==="
# Some flags and specs are not available with clang.
# https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/W5UFLUADNB4VF3OBUBSNAPOQL6XBCP74/
optflags_clang=$(echo "%{optflags}" | \ 
  sed -e 's| -fstack-clash-protection||' -e 's| -specs=[^ ]*||g')
mkdir test/build-clang-with-flags
pushd test/build-clang-with-flags
CC=clang CXX=clang++ cmake \
  -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \
  -DCMAKE_C_FLAGS="${optflags_clang}" \
  -DCMAKE_CXX_FLAGS="${optflags_clang}" \
  ..  
```

``
+ CC=clang
+ CXX=clang++
+ cmake -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON '-DCMAKE_C_FLAGS=-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong  -m64 -mtune=generic -fasynchronous-unwind-tables -fcf-protection' '-DCMAKE_CXX_FLAGS=-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong  -m64 -mtune=generic -fasynchronous-unwind-tables -fcf-protection' ..
...

    clang-10: error: unsupported argument 'auto' to option 'flto='

```


The following commit triggered the error.
https://src.fedoraproject.org/rpms/redhat-rpm-config/c/4637e1bd5512b869bd07c58b7545d2528a9bc4c8


Solution: use `%global toolchain clang` in the part using clang.
https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/master/f/macros#_44

Comment 5 Fedora Update System 2020-08-06 02:58:45 UTC
FEDORA-2020-65cbd94222 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.