From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: [PATCH] newlib: libc: merge build up a directory
Date: Mon, 14 Mar 2022 20:07:32 -0400 [thread overview]
Message-ID: <Yi/YxO8kuMMdac1p@vapier> (raw)
In-Reply-To: <Yi8fz+9ipzpTIzvT@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]
On 14 Mar 2022 11:58, Corinna Vinschen wrote:
> On Mar 13 22:48, Mike Frysinger wrote:
> > On 01 Mar 2022 20:39, Mike Frysinger wrote:
> > > --- a/newlib/libc/stdio/Makefile.inc
> > > +++ b/newlib/libc/stdio/Makefile.inc
> > > ...
> > > + %D%/vfiwscanf.c \
> > > + %D%/vfwscanf.c
> > > + %D%/vprintf.c \
> > > ...
> >
> > found a missing \ here fwiw
>
> The patch applies and I added that backslash. Then I removed all
> Makefile.in files from newlib and called `autoreconf', which ran
> through without any warning or error.
>
> However, clean building Cygwin with parallel make fails reproducably:
>
> $ $src/configure
> $ make -j42
> make[3]: Entering directory '$bin/x86_64-pc-cygwin/newlib'
> GEN stmp-targ-include
> make[3]: *** No rule to make target 'fdopen64.c', needed by 'libc_a-fdopen64.o'. Stop.
> make[3]: *** Waiting for unfinished jobs....
>
> So I tried with make -j1 and it still fails the same way.
>
> This happens for both, i686 as well as x86_64 Cygwin.
my cygwin builds broke a while ago and i don't know why. although i
just tried them again, and they've unbroke themselves. who knows.
at any rate, looks like stdio64 is annoying in that cygwin is the only
target that tests it :(. so that's why all my other ~30 targets are
passing. i'll have a v2 up with all the issues fixed, and i'll do a
deep dive on the generated objects/libs. i was holding off on doing
that until it sounded like people were OK with the general direction
of the code since it takes so long (both in terms of generating the
data, and in me digging through it). i think we're at that point now.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-15 0: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
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 [this message]
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=Yi/YxO8kuMMdac1p@vapier \
--to=vapier@gentoo.org \
--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).