public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com> To: doko at debian dot org <sourceware-bugzilla@sourceware.org> Cc: gdb-prs@sourceware.org Subject: Re: [Bug sim/28302] New: [11 Regression] gdb fails to build with glibc 2.34 ( Date: Fri, 10 Sep 2021 06:59:52 +0900 [thread overview] Message-ID: <CAAfxs75LzoZbOt7FTqOkpNOc4ExfG3wT=LQGOpPicby5h0kdXw@mail.gmail.com> (raw) In-Reply-To: <bug-28302-4717@http.sourceware.org/bugzilla/> I ran into this failure today, there is a discussion about the reason behind glibc making this change. https://public-inbox.org/libc-alpha/87y2ew8i1w.fsf@igel.home/T/ It's kind of hacky but this patch worked as a fix for me. diff --git a/sim/common/gentmap.c b/sim/common/gentmap.c index 9f30e66e378..f690193f471 100644 --- a/sim/common/gentmap.c +++ b/sim/common/gentmap.c @@ -83,6 +83,14 @@ gen_targ_map_c (void) printf ("#include \"targ-vals.h\"\n"); printf ("\n"); + /* Make SIGSTKSZ a constant again. */ + printf ("#ifdef __USE_SC_SIGSTKSZ\n"); + printf ("# undef SIGSTKSZ\n"); + printf ("# define SIGSTKSZ 8192\n"); + printf ("#endif\n"); + + printf ("\n"); + printf ("/* syscall mapping table */\n"); printf ("CB_TARGET_DEFS_MAP cb_init_syscall_map[] = {\n"); for (t = &sys_tdefs[0]; t->symbol; ++t) On Fri, Sep 3, 2021 at 4:18 PM doko at debian dot org via Gdb-prs <gdb-prs@sourceware.org> wrote: > > https://sourceware.org/bugzilla/show_bug.cgi?id=28302 > > Bug ID: 28302 > Summary: [11 Regression] gdb fails to build with glibc 2.34 ( > Product: gdb > Version: 11.1 > Status: NEW > Severity: normal > Priority: P2 > Component: sim > Assignee: unassigned at sourceware dot org > Reporter: doko at debian dot org > CC: vapier at gentoo dot org > Target Milestone: --- > > gdb fails to build on the gdb-11 branch with glibc-2.34, in the sim directory, > at least on arm-linux-gnueabihf and aarch64-linux-gnu: > > In file included from /usr/include/signal.h:328, > from ../../gnulib/import/signal.h:52, > from targ-map.c:7: > targ-map.c:412:17: error: initializer element is not constant > 412 | { "SIGSTKSZ", SIGSTKSZ, TARGET_SIGSTKSZ }, > | ^~~~~~~~ > targ-map.c:412:17: note: (near initialization for > ‘cb_init_signal_map[18].host_val’) > make[5]: *** [Makefile:522: targ-map.o] Error 1 > make[5]: Leaving directory '/<<PKGBUILDDIR>>/build/default/sim/aarch64' > make[4]: *** [Makefile:1271: all-recursive] Error 1 > make[4]: Leaving directory '/<<PKGBUILDDIR>>/build/default/sim' > make[3]: *** [Makefile:898: all] Error 2 > make[3]: Leaving directory '/<<PKGBUILDDIR>>/build/default/sim' > make[2]: *** [Makefile:8030: all-sim] Error 2 > > configured with > > --build=aarch64-linux-gnu --host=aarch64-linux-gnu --prefix=/usr > --libexecdir="\${prefix}/lib/gdb" --disable-werror --disable-maintainer-mode > --disable-dependency-tracking --disable-silent-rules --disable-gdbtk > --disable-shared --with-system-readline --with-expat --with-system-zlib > --without-guile --with-debuginfod --with-babeltrace --enable-tui --with-lzma > --with-python=python3 --with-xxhash --with-mpfr > > -- > You are receiving this mail because: > You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-09 22:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-03 7:18 doko at debian dot org 2021-09-03 7:18 ` [Bug sim/28302] " doko at debian dot org 2021-09-03 13:05 ` luis.machado at linaro dot org 2021-09-03 13:06 ` luis.machado at linaro dot org 2021-09-03 13:13 ` luis.machado at linaro dot org 2021-09-03 13:18 ` fweimer at redhat dot com 2021-09-09 21:59 ` Stafford Horne [this message] 2021-09-09 22:00 ` shorne at gmail dot com 2021-09-14 15:15 ` ats-sourceware at offog dot org 2021-10-03 16:09 ` vapier at gentoo dot org 2022-01-12 5:04 ` brobecker at gnat dot com 2022-01-16 10:08 ` brobecker at gnat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAAfxs75LzoZbOt7FTqOkpNOc4ExfG3wT=LQGOpPicby5h0kdXw@mail.gmail.com' \ --to=shorne@gmail.com \ --cc=gdb-prs@sourceware.org \ --cc=sourceware-bugzilla@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).