config: Update config.rpath from gnulib

Andrea Pinski andrew.pinski@oss.qualcomm.com
Wed Oct 7 21:34:48 GMT 2026


On Wed, Oct 7, 2026 at 5:57 AM Jeff Law <jeffrey.law@oss.qualcomm.com> wrote:
>
>
>
> On 10/7/26 12:20 AM, Uros Bizjak wrote:
> > Ping.
> >
> > On Wed, Sep 30, 2026 at 11:44 AM Uros Bizjak <ubizjak@gmail.com> wrote:
> >> Sync config.rpath with build-aux/config.rpath from gnulib
> >> (commit e93789db7e86).
> >>
> >> The old copy invoked egrep, which GNU grep 3.8 and later warns is
> >> obsolescent.  As a result, every configure run printed
> >>
> >>    checking for shared library run path origin... egrep: warning: egrep
> >>    is obsolescent; using grep -E
> >>
> >> into the build log.  The updated script uses plain grep for these
> >> checks.  The update also picks up other upstream changes.
> >>
> >> ChangeLog:
> >>
> >> * config.rpath: Update from gnulib.
> >>
> >> Bootstrapped on x86_64-linux-gnu.
> >>
> >> OK for mainline?
> Yes.  We probably should have an explicit policy that allows this kind
> of resync during stage1 without explicit approval.

Agreed.   config.{sub,guess} should most likely be in the same boat here too.
Target libraries should have a similar policy too (libffi and
libsanitizer); though those should be tested slightly more before the
sync is finalized.

Thanks,
Andrea

>
> jeff


More information about the Gcc-patches mailing list