public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "james.hilliard1 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29621] librtld.os: in function `__register_frame': libgcc/unwind-dw2-fde.c:136: undefined reference to `malloc' Date: Thu, 29 Sep 2022 19:51:35 +0000 [thread overview] Message-ID: <bug-29621-131-JgPQA9sNN9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29621-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29621 --- Comment #2 from James Hilliard <james.hilliard1 at gmail dot com> --- (In reply to Adhemerval Zanella from comment #1) > Are you sure it is not related on how you build your toolchain? I am asking > because Joseph has a build service that constantly check glibc build against > multiple architectures and we have not seen this issue [1]. It's a possibility but it's unclear what could be causing this. > > I have rebuild toolchain for or1k and mips64el using gcc-10/gcc-11 along > with binutils 2.39 and glibc-2.36 branches and I have seen only an ICE in > the compiler when using --enable-profile with GCC (by removing the configure > switch I could complete the build). I'm seeing these builds failing with errors when --disable-profile is passed: http://autobuild.buildroot.net/results/883/883b171a856a63540908976592683527fdb21cd2/glibc-2.36-44-g2628500f5dff1dd99c49a09b418b3b1ea3a6b5d3/build/config.log http://autobuild.buildroot.net/results/883/883b171a856a63540908976592683527fdb21cd2/build-end.log Configured like this looks like(note that autobuilder host is aarch64 based, however I'm seeing similar errors on our x86_64 build hosts): /home/autobuild/autobuild/instance-4/output-1/build/glibc-2.36-44-g2628500f5dff1dd99c49a09b418b3b1ea3a6b5d3/configure --target=mipsel-buildroot-linux-gnu --host=mipsel-buildroot-linux-gnu --build=aarch64-unknown-linux-gnu --prefix=/usr --enable-shared --with-pkgversion=Buildroot --disable-profile --disable-werror --without-gd --with-headers=/home/autobuild/autobuild/instance-4/output-1/host/mipsel-buildroot-linux-gnu/sysroot/usr/include --enable-kernel=5.16 Easiest way to reproduce buildroot autobuilder errors is like this(using config for above failure as an example): git clone https://github.com/buildroot/buildroot.git cd buildroot wget http://autobuild.buildroot.net/results/883/883b171a856a63540908976592683527fdb21cd2/config mv config .config make glibc To make the same build using your normal local glibc git tree for testing glibc changes: Simply create a local.mk file inside the buildroot tree: echo "GLIBC_OVERRIDE_SRCDIR = /home/buildroot/glibc" > local.mk Then to rebuild/resync testing changes from your local glibc checkout: make glibc-rebuild Reference manual for local.mk overrides: https://buildroot.org/downloads/manual/manual.html#_using_buildroot_during_development > > [1] https://sourceware.org/pipermail/libc-testresults/2022q3/009900.html -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-29 19:51 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-27 19:44 [Bug libc/29621] New: " james.hilliard1 at gmail dot com 2022-09-27 19:44 ` [Bug libc/29621] " james.hilliard1 at gmail dot com 2022-09-29 17:45 ` adhemerval.zanella at linaro dot org 2022-09-29 19:51 ` james.hilliard1 at gmail dot com [this message] 2022-10-17 12:42 ` adhemerval.zanella at linaro dot org 2022-10-26 18:54 ` james.hilliard1 at gmail dot com 2022-10-26 19:10 ` adhemerval.zanella at linaro dot org 2022-10-26 19:33 ` james.hilliard1 at gmail dot com 2022-10-27 14:04 ` adhemerval.zanella at linaro dot org 2022-10-27 19:57 ` james.hilliard1 at gmail dot com 2022-10-27 21:05 ` adhemerval.zanella at linaro dot org 2022-10-27 21:35 ` james.hilliard1 at gmail dot com 2022-10-28 5:28 ` fweimer at redhat dot com 2022-10-28 13:19 ` adhemerval.zanella at linaro dot org 2022-10-28 13:36 ` adhemerval.zanella at linaro dot org 2022-10-28 16:18 ` james.hilliard1 at gmail dot com 2022-10-28 16:32 ` adhemerval.zanella at linaro dot org 2022-10-28 21:23 ` james.hilliard1 at gmail dot com 2022-11-24 17:01 ` arnout at mind dot be 2022-11-24 17:21 ` arnout at mind dot be 2022-11-24 17:27 ` fweimer at redhat dot com 2023-08-07 9:37 ` sam at gentoo dot org 2024-01-11 9:41 ` fweimer at redhat 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=bug-29621-131-JgPQA9sNN9@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).