mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Georgi Chorbadzhiyski <gf@unixsol.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH 0/4] Fix function definitions.
Date: Fri, 09 Mar 2012 10:22:18 +0200	[thread overview]
Message-ID: <4F59BDBA.70206@unixsol.org> (raw)
In-Reply-To: <4F59BD70.9020105@unixsol.org>

On 3/9/12 10:21 AM, Georgi Chorbadzhiyski wrote:
> On 3/9/12 10:14 AM, Georgi Chorbadzhiyski wrote:
>> Define several functions if _BSD_SOURCE is set. _XOPEN_SOURCE
>> should also be checked but I can't be bothered, because _BSD_SOURCE
>> works.
>>
>> Background for these patches:
>> http://lists.landley.net/pipermail/toybox-landley.net/2012-March/000309.html
>>
>> Georgi Chorbadzhiyski (4):
>> include/stdlib.h: Define clearenv() if (_SVID_SOURCE || _BSD_SOURCE)
>> is set.
>> include/unistd.h: Define sethostname() if _BSD_SOURCE is set.
>> include/unistd.h: Define vfork() if _BSD_SOURCE is set.
>> include/sys/types.h: major(), minor() and makedev() should be defined
>> if _BSD_SOURCE is set.
>>
>> include/stdlib.h | 5 ++++-
>> include/sys/types.h | 5 ++++-
>> include/unistd.h | 10 ++++++++--
>> 3 files changed, 16 insertions(+), 4 deletions(-)
>>
>
> Hmm...it seems this is not enough. See include/unistd.h
>
> #ifdef _GNU_SOURCE
> int brk(void *);
> void *sbrk(intptr_t);
> pid_t forkall(void);
> int vhangup(void);
> int getpagesize(void);
> int usleep(unsigned);
> unsigned ualarm(unsigned, unsigned);
> int setgroups(size_t, const gid_t []);
> int setresuid(uid_t, uid_t, uid_t);
> int setresgid(gid_t, gid_t, gid_t);
> char *get_current_dir_name(void);
> #endif
>
> Most of the above according to their man pages should be defined if
> _BSD_SOURCE is set.
>
> Should the headers be filled with feature checks (that would make them
> quite ugly) or assume we have _GNU_SOURCE defined and remove any _GNU_SOURCE
> checks?

...for functions that are not pure GNU extensions like strndupa.

-- 
Georgi Chorbadzhiyski
http://georgi.unixsol.org/


  reply	other threads:[~2012-03-09  8:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09  8:14 Georgi Chorbadzhiyski
2012-03-09  8:14 ` [PATCH 1/4] include/stdlib.h: Define clearenv() if (_SVID_SOURCE || _BSD_SOURCE) is set Georgi Chorbadzhiyski
2012-03-09  8:14 ` [PATCH 2/4] include/unistd.h: Define sethostname() if _BSD_SOURCE " Georgi Chorbadzhiyski
2012-03-09  8:14 ` [PATCH 3/4] include/unistd.h: Define vfork() " Georgi Chorbadzhiyski
2012-03-09  8:14 ` [PATCH 4/4] include/sys/types.h: major(), minor() and makedev() should be defined " Georgi Chorbadzhiyski
2012-03-09  8:21 ` [PATCH 0/4] Fix function definitions Georgi Chorbadzhiyski
2012-03-09  8:22   ` Georgi Chorbadzhiyski [this message]
2012-03-09  8:33   ` Rich Felker
2012-03-09  9:16     ` Georgi Chorbadzhiyski
2012-03-09 15:11       ` Rob Landley
2012-03-09 16:38         ` Rich Felker
2012-03-16 19:05           ` Isaac Dunham
2012-03-16 22:48             ` Rich Felker
2012-04-05 21:06               ` Isaac Dunham

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=4F59BDBA.70206@unixsol.org \
    --to=gf@unixsol.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).