https://bugzilla.redhat.com/show_bug.cgi?id=1882871



--- Comment #3 from ruki <[email protected]> ---
I have fixed it. The new spec url:
https://github.com/xmake-io/xmake/blob/spec/scripts/rpmbuild/SPECS/xmake.spec

> 1. You need to call the %set_build_flags macro to ensure that Fedora's 
> CXXFLAGS are set properly.

Is this necessary? I saw that many other rpm packages do not add this. for
example:
https://src.fedoraproject.org/rpms/premake/blob/master/f/premake.spec

When I add it, it will cause the xmake program to crash on the fedora i386
platform.

Crash log:
https://download.copr.fedorainfracloud.org/results/waruqi/xmake/fedora-31-i386/01686127-xmake/builder-live.log.gz

> + LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-ld'

It seems that this ldflags is causing this problem and it works fine for all
platforms if do not add %set_build_flags


BTW, All tasks on copr /fedora-eln-* always fail to download.

```
Errors during downloading metadata for repository 'eln':
  - Status code: 404 for
https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/compose/Everything/x86_64/os/repodata/repomd.xml
(IP: 152.19.134.198)
Error: Failed to download metadata for repo 'eln': Cannot download repomd.xml:
Cannot download repodata/repomd.xml: All mirrors were tried
```

https://copr.fedorainfracloud.org/coprs/waruqi/xmake/build/1687682/
https://download.copr.fedorainfracloud.org/results/waruqi/xmake/fedora-eln-x86_64/01687682-xmake/builder-live.log.gz


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to