public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] Remove FreeBSD specifics from RTEMS <arpa/inet.h>
Date: Mon, 12 Jun 2017 12:01:00 -0000	[thread overview]
Message-ID: <20170612120126.GM13513@calimero.vinschen.de> (raw)
In-Reply-To: <20170612064218.11969-1-sebastian.huber@embedded-brains.de>

[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]

On Jun 12 08:42, Sebastian Huber wrote:
> For whatever reason FreeBSD renames several functions provided by
> <arpa/inet.h> and uses weak references to provide the standard function
> names.  This causes problems on targets lacking proper support for weak
> references.  We do not need this function renaming on RTEMS.
> 
> Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>
> ---
>  newlib/libc/sys/rtems/include/arpa/inet.h | 21 ---------------------
>  1 file changed, 21 deletions(-)
> 
> diff --git a/newlib/libc/sys/rtems/include/arpa/inet.h b/newlib/libc/sys/rtems/include/arpa/inet.h
> index d71c92748..91e3a828a 100644
> --- a/newlib/libc/sys/rtems/include/arpa/inet.h
> +++ b/newlib/libc/sys/rtems/include/arpa/inet.h
> @@ -112,27 +112,6 @@ struct in_addr {
>  #define	_STRUCT_IN_ADDR_DECLARED
>  #endif
>  
> -/* XXX all new diversions!! argh!! */
> -#if __BSD_VISIBLE
> -#define	inet_addr		__inet_addr
> -#define	inet_aton		__inet_aton
> -#define	inet_lnaof		__inet_lnaof
> -#define	inet_makeaddr		__inet_makeaddr
> -#define	inet_neta		__inet_neta
> -#define	inet_netof		__inet_netof
> -#define	inet_network		__inet_network
> -#define	inet_net_ntop		__inet_net_ntop
> -#define	inet_net_pton		__inet_net_pton
> -#define	inet_cidr_ntop		__inet_cidr_ntop
> -#define	inet_cidr_pton		__inet_cidr_pton
> -#define	inet_ntoa		__inet_ntoa
> -#define	inet_ntoa_r		__inet_ntoa_r
> -#define	inet_pton		__inet_pton
> -#define	inet_ntop		__inet_ntop
> -#define	inet_nsap_addr		__inet_nsap_addr
> -#define	inet_nsap_ntoa		__inet_nsap_ntoa
> -#endif /* __BSD_VISIBLE */
> -
>  __BEGIN_DECLS
>  #ifndef _BYTEORDER_PROTOTYPED
>  #define	_BYTEORDER_PROTOTYPED
> -- 
> 2.12.3

Please apply.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2017-06-12 12:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12  6:42 Sebastian Huber
2017-06-12 12:01 ` Corinna Vinschen [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=20170612120126.GM13513@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).