Re: [PATCH] newlib: libc: merge build up a directory

Mike Frysinger <[email protected]>
Newsgroups gmane.comp.lib.newlib
Message-ID <Yihvb+swfIXbaLhT@vapier>
On 09 Mar 2022 09:07, Corinna Vinschen wrote:
> On Mar  1 20:39, Mike Frysinger wrote:
> > Convert all the libc/ subdir makes into the top-level Makefile.  This
> > allows us to build all of libc from the top Makefile without using any
> > recursive make calls.  This is faster and avoids the funky lib.a logic
> > where we unpack subdir archives to repack into a single libc.a.  The
> > machine override logic is maintained though by way of Makefile include
> > ordering, and source file accumulation in libc_a_SOURCES.
> > 
> > There's a few dummy.c files that are no longer necessary since we aren't
> > doing the lib.a accumulating, so punt them.
> 
> The patch doesn't apply cleanly on current master.  Can you please have
> a look?

it needs my other patch series:
https://sourceware.org/pipermail/newlib/2022/019388.html

i missed that you had replied to that, so i'll follow up to that.
-mike
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmIob28ACgkQQWM7n+g3
9YEk5w/+Kap31Rrn0IrvxOnsQLF166voPu+jUAyS8A4A52Vz2ORKLNYf0r3CzDaz
pZ3AQoECd6pbBbqwAJeVk4xpyaQp5loHNTkCQzGvJ8jMqh8HwmZIK6Z8iZ5mXKvc
83DQ8m1sR4y2ZkuIb+7et14grZi71pprIatHgjgxXkQE4MozEEfOA2SqEIL3HzRs
ufnJuWoa4ooAtpmQBTek1XohNGR8rByke6ln9qOF5ltrp03eZ5CgweK9xE9/qDfm
pOGHo6ypYxKU7ke85hxsFreeBMb/+GfmX3daM0PUmC6QWB+FC9MRp4HplvS17x6b
xcHiejE3ljM7ToUZbmZiLbXXRzqeJmyH8MkB1sVPq+LcY4aiYbGytSHAEjEwoZ6L
gcYFgy+tUpG5XpTQcfaekFoPERwDoRvHMQTqXzw26BZIeQurs8rXjLVaEWwdF7BA
7vJDMat9gBCXAxxiD81SoU30M3XAbZ90ik8+0UIQxbMqxr5HQt8D1FIAQVk4uiyk
0yc1va4KAfJVBiqsB4rCx4wEISoOaiQ5DmDEFS6AsLB2Alis7XlXlrcUUBW3vARb
8OSzZ/K8yPApAUQ57+qWC5Rcdlgs5tCtljdN+FbSDpyLyggwD+QTmqQZWcRfwdXj
Em9z1OiirASd2WnjRhf38aUBKl7BVexpsRwpdPmW82NgFTd+10I=
=INy6
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.