Fair point, I've sent https://sourceware.org/pipermail/newlib/2025/022085.html
to the the newlib mailing list, doing the same change, with the email body /
commit message asking them just that question. Fingers crossed!
John
On Fri, Aug 8, 2025, at 4:24 PM, Joseph Myers wrote:
> On Thu, 7 Aug 2025, John Ericson wrote:
>
> > The VPATH workaround however is akin to:
> >
> > mkdir -p $build/mach0/mach1/libgcc
> > cd $build/mach0/mach1/libgcc
> > ln -s $gcc_source/libgcc/* ./
> > ./configure
> >
> > and it's that --- using the build dir with the symlinked sources inside
> > as the src/obj dir for an in-place build --- that breaks the
> > `multi_basedir=${srcdir}/..` assumption. It is only this VPATH
> > workaround, and *not* srcdir = objdir in general, that I'd like to
> > officially drop stop support for.
> >
> > How does that sound?
>
> I think it's reasonable to eliminate such a workaround, but I don't know
> how the newlib community feels, should they wish to update the shared
> toplevel build infrastructure with changes from GCC.
>
> --
> Joseph S. Myers
> josmy...@redhat.com
>
>
