From: Jeff Law <jeffreyalaw@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Newlib <newlib@sourceware.org>
Subject: Recent change broke bfin-elf
Date: Fri, 11 Feb 2022 09:06:08 -0700 [thread overview]
Message-ID: <35cc6015-d380-be7a-6441-d787d06ceec3@gmail.com> (raw)
This change:
> commit 66dfedc28778e81d9d75a4a3fa1e74192138bf62
> Author: Mike Frysinger <vapier@gentoo.org>
> Date: Wed Feb 2 01:06:21 2022 -0500
>
> libgloss: merge bfin into top-level Makefile
>
> Avoid a recursive make to speed things up a bit.
Broke the bfin-elf port with:
../../../../..//newlib-cygwin/libgloss/bfin/basiccrt.S:28:10: fatal
error: sys/platform.h: No such file or directory
28 | #include <sys/platform.h>
next reply other threads:[~2022-02-11 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 16:06 Jeff Law [this message]
2022-02-11 22:43 ` Mike Frysinger
2022-02-11 22:46 ` Jeff Law
2022-02-12 6:36 ` [PATCH/committed] libgloss: bfin: fix local header usage after automake move 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=35cc6015-d380-be7a-6441-d787d06ceec3@gmail.com \
--to=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).