public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Indu Bhagat <indu.bhagat@oracle.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, doko@ubuntu.com, sam@gentoo.org
Subject: Re: [[PATCH][GCC13] 0/2] Fix combined tree build of GCC 13 with Binutils 2.41
Date: Tue, 5 Dec 2023 15:39:50 -0800	[thread overview]
Message-ID: <20afaa96-db32-4154-9520-8b258e490dd1@oracle.com> (raw)
In-Reply-To: <ZW+aC0rEznxS9Mg8@tucnak>

On 12/5/23 13:45, Jakub Jelinek wrote:
> On Tue, Dec 05, 2023 at 01:36:30PM -0800, Indu Bhagat wrote:
>> To resolve the issue of combined Binutils (2.41) + GCC (13) failing to
>> install (https://sourceware.org/bugzilla/show_bug.cgi?id=31108), we will
>> need some backports.  This specific issue is with using --enable-shared
>> in the combined tree build; it arises due to missing install-*
>> dependencies in the top-level makefiles.
>>
>> I think it makes sense to bring both of the following two commits (from
>> the trunk) to the GCC13 branch:
>>
>> 	commit eff0e7a4ae31d1e4e64ae37bbc10d073d8579255
>> 	Author: Indu Bhagat <indu.bhagat@oracle.com>
>> 	Date:   Wed Jan 18 23:17:49 2023 -0800
>> 	toplevel: Makefile.def: add install-strip dependency on libsframe
>>      
>>
>> 	commit dab58c93634bef06fd289f49109b5c370cd5c380
>> 	Author: Indu Bhagat <indu.bhagat@oracle.com>
>> 	Date:   Tue Nov 15 15:07:04 2022 -0800
>> 	bfd: linker: merge .sframe sections
>>
>> This patch set cherry-picks the above two commits to GCC13 branch.  The
>> patches apply cleanly with no conflicts.
> 
> Won't this break building gcc 13 with in-tree older binutils which don't have
> libsframe at all?  I think binutils 2.39 and older don't have it.
> 

I tested with binutils-2_39-branch and releases/gcc-13 as well (with 
--enable-shared --disable-bootstrap). It builds and installs fine.

Indu


      reply	other threads:[~2023-12-05 23:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 21:36 Indu Bhagat
2023-12-05 21:36 ` [[PATCH][GCC13] 1/2] bfd: linker: merge .sframe sections Indu Bhagat
2023-12-05 21:36 ` [[PATCH][GCC13] 2/2] toplevel: Makefile.def: add install-strip dependency on libsframe Indu Bhagat
2023-12-05 21:45 ` [[PATCH][GCC13] 0/2] Fix combined tree build of GCC 13 with Binutils 2.41 Jakub Jelinek
2023-12-05 23:39   ` Indu Bhagat [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=20afaa96-db32-4154-9520-8b258e490dd1@oracle.com \
    --to=indu.bhagat@oracle.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=sam@gentoo.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).