From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH v2 2/2] newlib/.../getreent.c: Allow to be provided by host and do so for RTEMS
Date: Fri, 13 Oct 2017 09:16:00 -0000 [thread overview]
Message-ID: <20171013091515.GD20139@calimero.vinschen.de> (raw)
In-Reply-To: <81d2f590-0370-9318-4d6d-c60254a1c068@oarcorp.com>
[-- Attachment #1: Type: text/plain, Size: 3087 bytes --]
On Oct 12 20:31, Joel Sherrill wrote:
> On 10/11/2017 8:54 AM, Joel Sherrill wrote:
> >
> > Sorry to top post but replying from my phone on a plane.
> >
> > Some of our tests are managing to get duplicate symbol errors when linking.
> >
> > I put the dummy symbol in to follow the pattern in the file I patterned this after. I would have to look at the source again to see what file that was
> >
> >
> > On Oct 11, 2017, 9:49 AM, at 9:49 AM, Corinna Vinschen <vinschen@redhat.com> wrote:
> > Hi Joel,
> >
> > On Oct 11 07:57, Joel Sherrill wrote:
> > RTEMS provides the option to have a global or per-thread reentrancy
> > as part of application configuration. As part of this, RTEMS provides
> > the implementation of __getreent() as appropriate. Allow the target
> > to determine if this method is present in libc.a.
> > ---
> > newlib/configure.host<http://configure.host> | 2 +-
> > newlib/libc/reent/getreent.c | 8 ++++++++
> > 2 files changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/newlib/configure.host<http://configure.host> b/newlib/configure.host<http://configure.host>
> > index fb3362b..7f397dd 100644
> > --- a/newlib/configure.host<http://configure.host>
> > +++ b/newlib/configure.host<http://configure.host>
> > @@ -605,7 +605,7 @@ case "${host}" in
> > default_newlib_io_long_long="yes"
> > default_newlib_io_c99_formats="yes"
> > newlib_cflags="${newlib_cflags} -D_COMPILING_NEWLIB"
> > - newlib_cflags="${newlib_cflags} -DCLOCK_PROVIDED -DMALLOC_PROVIDED
> > -DEXIT_PROVIDED -DSIGNAL_PROVIDED -DREENTRANT_SYSCALLS_PROVIDED
> > -DHAVE_NANOSLEEP -DHAVE_BLKSIZE -DHAVE_FCNTL -DHAVE_ASSERT_FUNC"
> > +newlib_cflags="${newlib_cflags} -DCLOCK_PROVIDED -DMALLOC_PROVIDED
> > -DEXIT_PROVIDED -DSIGNAL_PROVIDED -DGETREENT_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"
> > ;;
> > diff --git a/newlib/libc/reent/getreent.c
> > b/newlib/libc/reent/getreent.c
> > index 60ae6fb..124abce 100644
> > --- a/newlib/libc/reent/getreent.c
> > +++ b/newlib/libc/reent/getreent.c
> > @@ -1,5 +1,11 @@
> > /* default reentrant pointer when multithread enabled */
> >
> > +#ifdef GETREENT_PROVIDED
> > +
> > +int _dummy_getreent;
> > +
> >
> > So, why do you need this? If you implement your own __getreent,
> > there's
> > no reason for this _dummy_getreent to exist, no?
> >
> > Btw., Cygwin implements its own __getreent(), too, without having to
> > change newlib/libc/reent/getreent.c at all...
>
> Is it OK to push these patches?
I still need an explanation for _dummy_getreent. It's kind of ugly.
Why exaclty is it required?
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-10-13 9:15 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 [this message]
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 ` [PATCH v2 1/2] newlib/configure.host: Remove obsolete definition of _I386MACH_ALLOW_HW_INTERRUPTS Joel Sherrill
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=20171013091515.GD20139@calimero.vinschen.de \
--to=vinschen@redhat.com \
--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).