public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/31488] undefined reference to `fmod'" error on i586 Date: Thu, 14 Mar 2024 15:59:23 +0000 [thread overview] Message-ID: <bug-31488-131-Q9LfiCCh1P@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31488-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31488 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- Could you provide the configure options, including the GCC one? I am trying to reproduce it on 2.38 release branch and fmod is present: i586-linux-gnu-master$ objdump -t math/libm.so | grep -w fmod 000104b0 w F .text 000000b8 fmod And this would be readily triggered by check-abi and math tests. Also, 16439f419b270184ec501c531bf20d83b6745fb0 commit should not matter for i686 (you can check that it adds the fmod@2.38 to all but i386 abi). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-14 15:59 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-14 14:01 [Bug math/31488] New: undefined reference to `fmod'" error for i586 akhilesh.k at samsung dot com 2024-03-14 14:06 ` [Bug math/31488] " akhilesh.k at samsung dot com 2024-03-14 14:07 ` [Bug math/31488] undefined reference to `fmod'" error on i586 akhilesh.k at samsung dot com 2024-03-14 15:59 ` adhemerval.zanella at linaro dot org [this message] 2024-03-14 16:08 ` schwab@linux-m68k.org 2024-03-14 16:14 ` schwab@linux-m68k.org 2024-03-14 16:16 ` adhemerval.zanella at linaro dot org 2024-03-14 22:38 ` sam at gentoo dot org 2024-05-10 9:41 ` akhilesh.k at samsung dot com 2024-05-10 16:19 ` adhemerval.zanella at linaro dot org
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-31488-131-Q9LfiCCh1P@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).