From: Joel Sherrill <joel@rtems.org>
To: newlib@sourceware.org
Cc: Joel Sherrill <joel@rtems.org>
Subject: [PATCH v2 1/2] newlib/configure.host: Remove obsolete definition of _I386MACH_ALLOW_HW_INTERRUPTS
Date: Wed, 11 Oct 2017 13:49:00 -0000 [thread overview]
Message-ID: <1507726664-4231-2-git-send-email-joel@rtems.org> (raw)
In-Reply-To: <1507726664-4231-1-git-send-email-joel@rtems.org>
The *-*-rtems* targets defined this even though the conditional
was no longer present in i386/setjmp.S.
---
newlib/configure.host | 2 --
1 file changed, 2 deletions(-)
diff --git a/newlib/configure.host b/newlib/configure.host
index ba2d8c6..fb3362b 100644
--- a/newlib/configure.host
+++ b/newlib/configure.host
@@ -608,8 +608,6 @@ case "${host}" in
newlib_cflags="${newlib_cflags} -DCLOCK_PROVIDED -DMALLOC_PROVIDED -DEXIT_PROVIDED -DSIGNAL_PROVIDED -DREENTRANT_SYSCALLS_PROVIDED -DHAVE_NANOSLEEP -DHAVE_BLKSIZE -DHAVE_FCNTL -DHAVE_ASSERT_FUNC"
# turn off unsupported items in posix directory
newlib_cflags="${newlib_cflags} -D_NO_GETLOGIN -D_NO_GETPWENT -D_NO_GETUT -D_NO_GETPASS -D_NO_SIGSET -D_NO_WORDEXP -D_NO_POPEN -D_NO_POSIX_SPAWN"
- # turn off using cli/sti in i386 setjmp/longjmp
- newlib_cflags="${newlib_cflags} -D_I386MACH_ALLOW_HW_INTERRUPTS"
;;
# VxWorks supplies its own version of malloc, and the newlib one
# doesn't work because VxWorks does not have sbrk.
--
1.8.3.1
prev parent reply other threads:[~2017-10-11 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 12:58 [PATCH v2 0/2] RTEMS configure.host patches Joel Sherrill
2017-10-11 12:58 ` [PATCH v2 2/2] newlib/.../getreent.c: Allow to be provided by host and do so for RTEMS Joel Sherrill
2017-10-11 13:54 ` Corinna Vinschen
2017-10-11 16:28 ` Joel Sherrill
2017-10-13 6:09 ` Joel Sherrill
2017-10-13 9:16 ` Corinna Vinschen
2017-11-13 9:59 ` Joel Sherrill
2017-11-13 15:46 ` Corinna Vinschen
2017-11-14 8:01 ` Florian Schmidt
2017-10-17 11:40 ` Sebastian Huber
2017-10-11 13:49 ` Joel Sherrill [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=1507726664-4231-2-git-send-email-joel@rtems.org \
--to=joel@rtems.org \
--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).