From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] newlib: libc: merge build up a directory
Date: Wed, 9 Mar 2022 09:07:50 +0100 [thread overview]
Message-ID: <YihgVlUirQlagZTx@calimero.vinschen.de> (raw)
In-Reply-To: <20220302013959.511-1-vapier@gentoo.org>
Hi Mike,
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?
$ git am x.patch
Applying: newlib: libc: merge build up a directory
error: patch failed: newlib/libc/machine/xstormy16/Makefile.am:1
error: newlib/libc/machine/xstormy16/Makefile.am: patch does not apply
error: patch failed: newlib/libc/stdlib/Makefile.am:1
error: newlib/libc/stdlib/Makefile.am: patch does not apply
Patch failed at 0001 newlib: libc: merge build up a directory
[...]
Thanks,
Corinna
next prev parent reply other threads:[~2022-03-09 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 1:39 Mike Frysinger
2022-03-09 8:07 ` Corinna Vinschen [this message]
2022-03-09 9:12 ` Mike Frysinger
2022-03-13 21:18 ` Mike Frysinger
2022-03-14 2:48 ` Mike Frysinger
2022-03-14 10:58 ` Corinna Vinschen
2022-03-15 0:07 ` Mike Frysinger
2022-03-15 3:04 ` [PATCH v2] " Mike Frysinger
2022-03-15 3:15 ` Mike Frysinger
2022-03-16 7:24 ` Corinna Vinschen
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=YihgVlUirQlagZTx@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.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).