public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Lucas A. M. Magalhaes" <lamm@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org, dje.gcc@gmail.com, meissner@linux.ibm.com
Subject: Re: [PATCH] powerpc: Remove LINK_OS_EXTRA_SPEC{32, 64} from --with-advance-toolchain
Date: Tue, 09 Nov 2021 16:03:55 -0300	[thread overview]
Message-ID: <163648463591.2066721.11967044588512686137@localhost.localdomain> (raw)
In-Reply-To: <20211109141957.GX614@gate.crashing.org>

Quoting Segher Boessenkool (2021-11-09 11:19:58)
> Hi!
> 
> On Tue, Nov 09, 2021 at 10:39:46AM -0300, Lucas A. M. Magalhaes wrote:
> > Ping.
> 
> I did not get the original, and neither did the archives?
> 
Strange, it's on the archives.
https://gcc.gnu.org/pipermail/gcc-patches/2021-October/582643.html
Looking at my local mails, I did't receive it as well.

> > Historically this was added to fill gaps from ld.so.cache on early AT
> > releases. This now are just causing errors and rework. Since AT5.0 the
> > AT's ld.so is using a correctly configured ld.so.cache and sets the
> > DT_INTERP to AT's ld.so. This two factors are sufficient for an AT
> > builded program to get the correct libraries.
> > 
> > GCC congured with --with-advance-toolchain has issues building GlibC
> > releases because it adds DT_RUNPATH to ld.so and that's unsupported.
> > 
> > 2021-03-11  Lucas A. M. Magalhães  <lamm@linux.ibm.com>
> 
> 2021-11-03
> 
> >       * config.gcc (powerpc*-*-*): Remove -rpath from
> >         --with-advance-toochain
> 
> The start of the line aligns with the star.  Changelog lines end in a
> full stop.  It's "toolchain".
> 
> The patch is okay for trunk.  Thanks!  Do you need backports as well?
> Those are fine as well :-)
I don't think we need a backport.
Segher can you push this with the changes or should I send a V2?

---
Lucas A. M. Magalhães

  reply	other threads:[~2021-11-09 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 13:39 Lucas A. M. Magalhaes
2021-11-09 14:19 ` Segher Boessenkool
2021-11-09 19:03   ` Lucas A. M. Magalhaes [this message]
2021-11-10 14:39     ` Segher Boessenkool
2021-11-10 14:21   ` [PATCH v2] " Lucas A. M. Magalhaes
2021-11-10 14:37     ` Segher Boessenkool
  -- strict thread matches above, loose matches on Subject: below --
2021-10-26 18:52 [PATCH] " Lucas A. M. Magalhaes

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=163648463591.2066721.11967044588512686137@localhost.localdomain \
    --to=lamm@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=meissner@linux.ibm.com \
    --cc=segher@kernel.crashing.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).