Re: aarch64 mock gcc/annobin errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 3, 2020 at 4:25 PM Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote:
> I'm running an F32 aarch64 guest qemu VM on an x86_64 F32 host, and, in that
> VM, I attempted to build something fairly simple via mock. This is my reward:
>
> configure:3590: gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-
> D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-
> strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -
> specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -
> fstack-clash-protection  -Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -
> specs=/usr/lib/rpm/redhat/redhat-hardened-ld conftest.c  >&5
>
> annobin: conftest.c: AArch64: The annobin plugin is out of date with respect
> to  gcc
> *** WARNING *** there are active plugins, do not report this as a bug unless
> you can reproduce it without enabling any plugins.
> Event                            | Plugins
> PLUGIN_FINISH_UNIT               | annobin: Generate final annotations
> PLUGIN_START_UNIT                | annobin: Generate global annotations
> PLUGIN_ALL_PASSES_START          | annobin: Generate per-function annotations
> PLUGIN_ALL_PASSES_END            | annobin: Register per-function end symbol
> conftest.c:1: internal compiler error: Segmentation fault
>
> First time I've seen something like that, any idea what to do here, for this?
> This if from a first build in mock, which presumably pulled in the most
> recent versions of all rpms into the chroot.

Are you building for a rawhide target?  If so, mock is pulling in rpms
from the most recent rawhide compose.  Add "--enablerepo=local" to get
the very latest rpms from koji.

There have been a fewl instances recently of the annobin plugin not
matching gcc.  As far as I know, the issue has been resolved, so
hopefully the extra mock flag will work for you.
-- 
Jerry James
http://www.jamezone.org/
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux