From: YunQiang Su <wzssyqa@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: YunQiang Su <yunqiang.su@cipunited.com>,
binutils <binutils@sourceware.org>
Subject: Re: [PATCH v5 3/4] Gold/MIPS: Add targ_extra_size=64 for mips32 triples
Date: Fri, 17 Nov 2023 22:57:44 +0800 [thread overview]
Message-ID: <CAKcpw6VJTHBqroJtTqQHoE+kVpB34CFpS-YppE_meaPNHRjZ3g@mail.gmail.com> (raw)
In-Reply-To: <5f52f8a3-a033-49b5-9fc5-aa7546ebb42e@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Nick Clifton <nickc@redhat.com> 于 2023年11月17日周五 22:36写道：
> Hi YunQiang Su,
>
> > So we can enable 64bit ELF support for MIPS32 toolchain.
> >
> > This patch can fix build failure with configure:
> > --target=mips-linux-gnu \
> > --enable-targets=mips64-linux-gnuabi64,mips64-linux-gnuabin32
> > The error message is like:
> > undefined reference to `gold::Output_data_reloc_base<9, true, 32,
> false>::
>
> Patch approved and applied.
>
thanks. can i backport it to 2.41?
> Cheers
> Nick
>
>
>
next prev parent reply other threads:[~2023-11-17 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 5:05 [PATCH v5 0/4] Gold/MIPS: Improve MIPS support in configure.tgt YunQiang Su
2023-11-13 5:05 ` [PATCH v5 1/4] Gold: Add targ_extra_little_endian to configure.ac YunQiang Su
2023-11-13 5:05 ` [PATCH v5 2/4] Gold/MIPS: Drop mips*le/mips*el* triple pattern YunQiang Su
2023-11-13 5:05 ` [PATCH v5 3/4] Gold/MIPS: Add targ_extra_size=64 for mips32 triples YunQiang Su
2023-11-17 14:35 ` Nick Clifton
2023-11-17 14:57 ` YunQiang Su [this message]
2023-11-20 12:11 ` Nick Clifton
2023-11-13 5:05 ` [PATCH v5 4/4] Gold/MIPS: Add mips64*/mips64*el triple support YunQiang Su
2023-11-13 5:11 ` [PATCH v5 0/4] Gold/MIPS: Improve MIPS support in configure.tgt YunQiang Su
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=CAKcpw6VJTHBqroJtTqQHoE+kVpB34CFpS-YppE_meaPNHRjZ3g@mail.gmail.com \
--to=wzssyqa@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=yunqiang.su@cipunited.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).