RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1991941 - emacs fails to build with gcc-11.2.1-2.1.el9
Summary: emacs fails to build with gcc-11.2.1-2.1.el9
Keywords:
Status: CLOSED DUPLICATE of bug 1975151
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: emacs
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Jacek Migacz
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-10 12:51 UTC by Miloš Prchlík
Modified: 2021-08-10 13:42 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-10 13:21:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-93019 0 None None None 2021-08-10 12:54:46 UTC
Red Hat Issue Tracker RHELPLAN-93020 0 None None None 2021-08-10 12:54:49 UTC

Description Miloš Prchlík 2021-08-10 12:51:11 UTC 
Description of problem:

$ rpmbuild -bc SPECS/emacs.spec
...
  CC       macros.o
  CC       keymap.o
  CC       sysdep.o
../../src/sysdep.c:1819:22: error: variably modified 'sigsegv_stack' at file scope
 1819 | static unsigned char sigsegv_stack[SIGSTKSZ];
      |                      ^~~~~~~~~~~~~
make[3]: *** [Makefile:402: sysdep.o] Error 1
make[3]: Leaving directory '/tmp/tmp.2Usu8Gxn9S/BUILD/emacs-27.1/build-gtk/src'
make[2]: *** [Makefile:424: src] Error 2
make[2]: Leaving directory '/tmp/tmp.2Usu8Gxn9S/BUILD/emacs-27.1/build-gtk'
make[1]: *** [Makefile:1119: bootstrap] Error 2
make[1]: Leaving directory '/tmp/tmp.2Usu8Gxn9S/BUILD/emacs-27.1/build-gtk'
error: Bad exit status from /var/tmp/rpm-tmp.4EtN06 (%build)

The full log can be found at [1].

The rebuild used to work in the past, see [2]. There is some difference between toolchain NVRs used, gcc-11.1.1-6.1.el9.x86_64 => gcc-11.2.1-2.1.el9.x86_64, and glibc-devel-2.33-14.el9 => glibc-devel-2.34-1.el9.


[1] http://lab-02.rhts.eng.bos.redhat.com/beaker/logs/tasks/130192+/130192794/taskout.log
[2] https://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2021/07/55290/5529079/10236232/128343091/taskout.log


Version-Release number of selected component (if applicable):

emacs-27.1-3.el9
gcc-11.2.1-2.1.el9
glibc-devel-2.34-1.el9
binutils-2.35.2-6.el9


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Jacek Migacz 2021-08-10 13:21:53 UTC 

*** This bug has been marked as a duplicate of bug 1975151 ***
Note You need to log in before you can comment on or make changes to this bug.