X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Sender:	rich AT phekda DOT freeserve DOT co DOT uk
Message-ID:	<3C64612A.62D21537@phekda.freeserve.co.uk>
Date:	Fri, 08 Feb 2002 23:37:14 +0000
From:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586)
X-Accept-Language:	de,fr
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: posix_spanw family
References:	<15DBDD66E28 AT HRZ1 DOT hrz DOT tu-darmstadt DOT de>
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

Juan Manuel Guerrero wrote:
> To port gettext-0.11at least  the following posix functions are needed:
> 
> posix_spawn_file_actions_init
> posix_spawn_file_actions_adddup2
> posix_spawn_file_actions_addclose
> posix_spawn_file_actions_addopen
> posix_spawnp
> posix_spawn_file_actions_destroy

Looking at the draft 7 (pre-standardisation) of the new POSIX standard, I see
that these functions are part of the POSIX realtime extensions. They are
intended to replace fork()/exec(). Since we don't support fork(), I don't see
how we can support posix_spawn*().

Why does gettext need these functions?
 
> Has someone started to code those functions?

I don't think so.

At some point I'm going to go through the list of unimplemented POSIX
functions (as shown by tests/libclink) and try to implement some of them.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -