From: Jeff Johnston <jjohnstn@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: newlib@sourceware.org, gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: For GCC, newlib combined tree, newlib build-tree testing, use standard search paths
Date: Mon, 15 May 2023 12:04:04 -0400 [thread overview]
Message-ID: <CAOox84u2SifHZtUHohTTR652tTFA7cvr4r-L95ONYtfLbpViaA@mail.gmail.com> (raw)
In-Reply-To: <875y8urpkb.fsf@euler.schwinge.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
Sounds fine Thomas. Thanks.
-- Jeff J.
On Mon, May 15, 2023 at 4:01 AM Thomas Schwinge <thomas@codesourcery.com>
wrote:
> Hi!
>
> On 2023-05-08T21:50:56+0200, I wrote:
> > Ping: OK to push to newlib main branch the attached
> > "For GCC, newlib combined tree, newlib build-tree testing, use standard
> search paths"?
> > Or, has anybody got adverse comments/insight into this?
>
> Given that nobody has any comments, I'll push this later this week.
> (..., and be available to address any issue this, unlikely, may cause.)
>
>
> Grüße
> Thomas
>
>
> > On 2023-04-14T22:03:28+0200, I wrote:
> >> Hi!
> >>
> >> OK to push to newlib main branch the attached
> >> "For GCC, newlib combined tree, newlib build-tree testing, use standard
> search paths"
> >> -- or is something else wrong here, or should this be done differently?
> >> (I mean, I'm confused why this doesn't just work; I'm certainly not the
> >> first person to be testing such a setup?)
> >>
> >> I'm not doing anything special here: just symlink 'newlib' into the GCC
> >> source directory, build the combined tree, and then run 'make check', as
> >> mentioned in the attached Git commit log.
> >>
> >>
> >> Grüße
> >> Thomas
>
>
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201,
> 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer:
> Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München;
> Registergericht München, HRB 106955
>
prev parent reply other threads:[~2023-05-15 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 20:03 Thomas Schwinge
2023-05-08 19:50 ` Thomas Schwinge
2023-05-15 8:01 ` Thomas Schwinge
2023-05-15 16:04 ` Jeff Johnston [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=CAOox84u2SifHZtUHohTTR652tTFA7cvr4r-L95ONYtfLbpViaA@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=newlib@sourceware.org \
--cc=thomas@codesourcery.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).