public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/26563] libmvec_nonshared.a file removed, spec2017/525 build failed because of missing symbol _ZGVdN4v___exp_finite
Date: Tue, 01 Sep 2020 17:57:31 +0000	[thread overview]
Message-ID: <bug-26563-131-qmrPGw3jiP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26563-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26563

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The point of the removal was that all the references to *_finite symbols 
had already been removed from the glibc headers (bits/math-finite.h was 
removed), so nothing should be generating a reference to those symbols 
when building with the headers from a glibc where libmvec_nonshared.a 
doesn't provide corresponding wrappers.  So you need to find out what is 
using e.g. outdated glibc headers rather than those corresponding to the 
glibc version being used.  (Note that .o / .a files built with an old 
glibc can't be linked with a new glibc if they use symbols that have been 
obsoleted - there's backwards compatibility only for fully linked 
executables / shared libraries using such symbols, not unlinked object 
files.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2020-09-01 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 17:44 [Bug math/26563] New: " skpgkp2 at gmail dot com
2020-09-01 17:45 ` [Bug math/26563] " skpgkp2 at gmail dot com
2020-09-01 17:57 ` joseph at codesourcery dot com [this message]

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-26563-131-qmrPGw3jiP@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: link
Be 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).