From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>,
gcc@gcc.gnu.org, GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Build errors for older versions
Date: Thu, 25 Apr 2024 09:00:18 -0700 [thread overview]
Message-ID: <CAMe9rOox8ZTxBqdaacAq3uX=tArVMWhtkQoQ6cdrQKM+FpsNRw@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1naVvAcwYFpAkenZSt=Wbk9ZvZ_9sChcPZ-7RZJc1v3iQ@mail.gmail.com>
On Thu, Apr 25, 2024 at 8:55 AM Andrew Pinski <pinskia@gmail.com> wrote:
>
> On Thu, Apr 25, 2024 at 4:21 AM Stefan Schulze Frielinghaus via Gcc
> <gcc@gcc.gnu.org> wrote:
> >
> > Hi all,
> >
> > while bisecting I recently ran into build errors like
> >
> > In file included from /devel/gcc/libgcc/../gcc/tsystem.h:101,
> > from /devel/gcc/libgcc/libgcov.h:42,
> > from /devel/gcc/libgcc/libgcov-interface.c:26:
> > /usr/include/stdlib.h:931:6: error: wrong number of arguments specified for 'malloc' attribute
> > 931 | __attr_dealloc_free __wur;
> > | ^~~~~~~~~~~~~~~~~~~
> > /usr/include/stdlib.h:931:6: note: expected between 0 and 0, found 2
> >
> > My host system is Fedora 39 on x86_64 while trying to build
> > r11-3896-g61a43de58cb6de. The error does not appear if I'm using e.g.
> > Fedora 34. Is this known and if so does there exist a workaround such
> > that building older versions on a recent OS works?
>
> Basically glibc's check for GCC version is only designed for released
> versions of GCC. So bisecting GCC means sometimes that check will
> break.
> I have not fully looked into it but maybe glibc folks can provide a
> workaround to disable the version check to assume a much older version
> of GCC here.
>
> Thanks,
> Andrew Pinski
I keep the older versions of GCC around for this case:
[hjl@gnu-cfl-3 usr]$ ls -d /usr/gcc*
/usr/gcc-10.2.1-32bit /usr/gcc-12.3.1-32bit /usr/gcc-14.0.1-x32
/usr/gcc-10.2.1-mx32 /usr/gcc-12.3.1-mx32 /usr/gcc-6.4.1-x32
/usr/gcc-10.2.1-x32 /usr/gcc-12.3.1-x32 /usr/gcc-7.4.1-x32
/usr/gcc-11.2.1-32bit /usr/gcc-13.2.1-32bit /usr/gcc-8.4.1-x32
/usr/gcc-11.2.1-mx32 /usr/gcc-13.2.1-mx32 /usr/gcc-9.3.1-x32
/usr/gcc-11.2.1-x32 /usr/gcc-13.2.1-x32
[hjl@gnu-cfl-3 usr]$
--
H.J.
prev parent reply other threads:[~2024-04-25 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 11:19 Stefan Schulze Frielinghaus
2024-04-25 15:54 ` Andrew Pinski
2024-04-25 16:00 ` H.J. Lu [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='CAMe9rOox8ZTxBqdaacAq3uX=tArVMWhtkQoQ6cdrQKM+FpsNRw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=pinskia@gmail.com \
--cc=stefansf@linux.ibm.com \
/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).