public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: vinschen@redhat.com
Cc: newlib@sourceware.org
Subject: Re: [PATCH] libgloss: riscv: Convert to non-recursive automake
Date: Fri, 26 Aug 2022 07:51:38 -0700 (PDT)	[thread overview]
Message-ID: <mhng-fb437b92-23c3-4d97-83ae-f5502078e76b@palmer-mbp2014> (raw)
In-Reply-To: <Ywjdc+TW77bp8SnZ@calimero.vinschen.de>

On Fri, 26 Aug 2022 07:49:23 PDT (-0700), vinschen@redhat.com wrote:
> On Aug 23 16:12, Palmer Dabbelt wrote:
>> PR 29515 points out our documentation builds are broken, let's just move
>> over to the new non-recursive builds.
>>
>> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
>> ---
>> I think something as small as adding an empty "html" target could make that bug
>> report go away, but when poking around I couldn't figure out why our
>> Makefile.in was so different.  I ended up running into vapier's build system
>> conversion patches and figured it would be easier to just throw away our
>> current build configuration rather than trying to figure out how it works.
>>
>> This builds for me and the resulting libraries look generally OK, but I don't
>> personally use newlib right now so I don't have anything specific setup for
>> testing.
>>
>> I haven't included the generated files from running autoconf/automake as I'm
>> getting a lot of diff right now due to some version mis-matches on my
>> development box.  If folks like this then I'm happy to sort that out, just
>> figured I'd send something along now to see if this is the right way to go --
>> it's a lot of diff just to make "make html" work, but as far as I can tell the
>> plan is to convert all subdirs over eventually so it seems sane to me.
>
> Pushed with regenerated configurey.

Thanks!

      reply	other threads:[~2022-08-26 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 23:12 Palmer Dabbelt
2022-08-26 14:49 ` Corinna Vinschen
2022-08-26 14:51   ` Palmer Dabbelt [this message]

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=mhng-fb437b92-23c3-4d97-83ae-f5502078e76b@palmer-mbp2014 \
    --to=palmer@rivosinc.com \
    --cc=newlib@sourceware.org \
    --cc=vinschen@redhat.com \
    /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).