Re: LTO is broken in Rawhide/33 containers

2020-09-17 Thread Petr Pisar
On Thu, Sep 17, 2020 at 01:24:26AM -0400, Elliott Sales de Andrade wrote:
> When using Fedora's containers, LTO appears to be broken. I'm not sure
> who to report this to, the container builder or gcc.
>
> $ podman run --pull=always --rm -it registry.fedoraproject.org/fedora:rawhide
> # dnf install -y gcc
> # echo 'int main(void) { int class=0; return class; }' > sanitycheck.c
> # gcc -flto=auto sanitycheck.c -o sanitycheck
> lto-wrapper: fatal error: execvp: No such file or directory
> compilation terminated.
> /usr/bin/ld: error: lto-wrapper failed
> collect2: error: ld returned 1 exit status
> 
> The test file is what Meson compiles as a check. This also fails on
> fedora:33. For good measure, you can throw in a `dnf update -y`, but
> it does not update/fix anything.
> 
> Running a similar check in `mock -r fedora-rawhide-x86_64` --shell works fine.
> 
This looks like . Please
use Bugzilla for reporting bugs in a packaging.

-- Petr


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org


LTO is broken in Rawhide/33 containers

2020-09-16 Thread Elliott Sales de Andrade
When using Fedora's containers, LTO appears to be broken. I'm not sure
who to report this to, the container builder or gcc.

$ podman run --pull=always --rm -it registry.fedoraproject.org/fedora:rawhide
# dnf install -y gcc
# echo 'int main(void) { int class=0; return class; }' > sanitycheck.c
# gcc -flto=auto sanitycheck.c -o sanitycheck
lto-wrapper: fatal error: execvp: No such file or directory
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status

The test file is what Meson compiles as a check. This also fails on
fedora:33. For good measure, you can throw in a `dnf update -y`, but
it does not update/fix anything.

Running a similar check in `mock -r fedora-rawhide-x86_64` --shell works fine.

-- 
Elliott
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org