From: Jeff Johnston <jjohnstn@redhat.com>
To: imi415 <imi415@imi.moe>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: Newlib provided syscalls on SH
Date: Tue, 9 Aug 2022 15:29:23 -0400 [thread overview]
Message-ID: <CAOox84sV6zek5YYdpsRRr9w4O30C-eOQ4cHsZ2KjBFOVvpUZWQ@mail.gmail.com> (raw)
In-Reply-To: <720b9093-3afb-677e-771c-77d323ab39fd@imi.moe>
Hi Yilin,
You will need to patch the libc/sys/sh/Makefile.inc to match what is done
in libc/sys/arm/Makefile.inc. This is fairly simple. When you are done,
then you can
use the --disable-newlib-supplied-syscalls to omit whatever you want in the
libc/sys/sh directory. Feel free to submit the patch here when you have
it working to your satisfaction.
-- Jeff J.
On Mon, Aug 8, 2022 at 3:56 AM imi415 via Newlib <newlib@sourceware.org>
wrote:
> Hi all,
>
> I'm trying to build newlib for SuperH(sh) architecture, and the syscalls
> under the "newlib/libc/sys/sh" directory
>
> are built no matter whether "--disable-newlib-supplied-syscalls" is
> provided.The target is a bare-metal target
>
> so I need to provide these syscalls myself, same as other bare-metal
> targets do.
>
> I have checked the Makefile.am under the directory and there seems to be
> no special treatments for the "MAY_SUPPLY_SYSCALLS" option.
>
> Do I have to patch newlib for this or is there another way overriding
> these syscalls?
>
> P.S. The build environment is generated by Crosstool-NG.
>
>
> Thanks & Best Regards,
>
> Yilin Sun
>
>
prev parent reply other threads:[~2022-08-09 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 7:56 imi415
2022-08-09 19:29 ` 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=CAOox84sV6zek5YYdpsRRr9w4O30C-eOQ4cHsZ2KjBFOVvpUZWQ@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=imi415@imi.moe \
--cc=newlib@sourceware.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).