public inbox for
 help / color / mirror / Atom feed
From: Alexey Lapshin <>
To: ""
Cc: "" <>,
	"" <>
Subject: Re: [PATCH v2] newlib: fix sys headers installation path
Date: Mon, 11 Sep 2023 13:26:34 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> This patch fixes the header install problem for RTEMS. Why did the
> xtensa port work without this fix? This seems to be a generic issue.

This because of files from "newlib/libc/sys/xtensa/include/" used mostly while newlib build.

While build applications used chip specific core-isa.h file.. E.g.

That's the reason why I did not catch the issue.

  reply	other threads:[~2023-09-11 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 12:44 Alexey Lapshin
2023-09-11 12:45 ` Alexey Lapshin
2023-09-11 12:53   ` [PATCH v2] " Alexey Lapshin
2023-09-11 13:09     ` Sebastian Huber
2023-09-11 13:26       ` Alexey Lapshin [this message]
2023-09-13  6:11         ` Sebastian Huber
2023-09-13 13:37           ` Alexey Lapshin
2023-09-18 12:22             ` Sebastian Huber
2023-09-18 15:47               ` Jeff Johnston

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).