From: Jeff Johnston <jjohnstn@redhat.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
Mike Frysinger <vapier@gentoo.org>,
newlib@sourceware.org
Subject: Re: Various libgloss problems after recent changes
Date: Wed, 22 Feb 2023 13:06:33 -0500 [thread overview]
Message-ID: <CAOox84sboRbQR=OShetQC2Z9SwpmzDtR0EFxmKxNjKgCzhSRQQ@mail.gmail.com> (raw)
In-Reply-To: <74695b10-d7c7-9d79-0760-687ed966da34@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
Great, thanks.
On Wed, Feb 22, 2023 at 12:55 PM Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
> On 2/22/23 09:20, Jeff Johnston wrote:
> > Yes, I found that and fixed it in the patch I attached. Are you saying
> > that patch didn't work as well?
> > I did forget to add the new arm.mh <http://arm.mh> file I created but I
> > have done so locally and have reposted the patch here.
> Your most recent patch works.
>
> jeff
>
>
next prev parent reply other threads:[~2023-02-22 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 0:48 Jeff Law
2023-02-09 22:54 ` Jeff Johnston
2023-02-10 11:21 ` Richard Earnshaw
2023-02-10 16:54 ` Jeff Law
2023-02-21 21:39 ` Jeff Johnston
2023-02-22 7:16 ` Jeff Law
2023-02-22 16:20 ` Jeff Johnston
2023-02-22 16:40 ` Jeff Law
2023-02-22 17:54 ` Jeff Law
2023-02-22 18:06 ` Jeff Johnston [this message]
2023-02-10 17:16 ` Jeff Johnston
2023-12-04 6:49 ` Mike Frysinger
2023-02-10 16:52 ` Jeff Law
2023-12-04 7:03 ` [PATCH 1/2] Revert "Fix libgloss/newlib build to conditionally use top include dir" Mike Frysinger
2023-12-04 7:03 ` [PATCH 2/2] libgloss: drop $(INCLUDES) when using $(AS) Mike Frysinger
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='CAOox84sboRbQR=OShetQC2Z9SwpmzDtR0EFxmKxNjKgCzhSRQQ@mail.gmail.com' \
--to=jjohnstn@redhat.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=jeffreyalaw@gmail.com \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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).