Minutes of the 18 September 2014 Teleconference Austin-675 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 19 September 2014 Attendees: Andrew Josey, The Open Group Don Cragun, IEEE PASC OR Joerg Schilling FOKUS Fraunhofer Mark Ziegast, SHware Systems Eric Blake, Red Hat Matthew Dempsky, OpenBSD Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group Richard Hansen, BBN Apologies David Clissold, IBM Martin Rehak, Oracle Mark Brown, Canonical * General news On the PASC PAR approval progress - still open. Don currently has the action to progress. * Outstanding actions +Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 Don has an action to produce a proposal. +Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN http://austingroupbugs.net/view.php?id=561 Eric has an action to update the proposal. +Bug 0000573: Please add '+' to the portable filename character set OPEN http://austingroupbugs.net/view.php?id=573 Joerg has an action to prepare a proposed change. +Bug 0000592: consistent use of struct timespec OPEN http://austingroupbugs.net/view.php?id=592 Jim had provided additional information in bugnote 1627. This was discussed and Jim took an action to provide further information. +Bug 0000598: OH shading and new interfaces OPEN http://austingroupbugs.net/view.php?id=598 Eric has an action to propose a new solution with self-contained headers. +Bug 0000517: EBNF support OPEN http://austingroupbugs.net/view.php?id=517 Action on Joerg to look at this. +Bug 0000633: SIGEV_THREAD delivery renders many signal interfaces unsafe OPEN http://austingroupbugs.net/view.php?id=633 We noted that feedback has settled down on the mailing list, and will discuss next session. +Bug 0000657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN http://austingroupbugs.net/view.php?id=657 Eric has an action to propose wording to clarify the behavior for fmemopen(), and also to contact the glibc developers to get their feedback. +Bug 0000658: Undefined/unspecified behavior clauses in description of open have race conditions OPEN http://austingroupbugs.net/view.php?id=658 It was noted that there is some overlap with changes in TC1. Eric took an action to update the proposal to resolve the overlaps appropriately. +Bug 0000615: pthread_setcancelstate should be async-signal-safe OPEN http://austingroupbugs.net/view.php?id=615 We now have reports on AIX and Apple. Jim to report back on whether pthread_cancelstate() is async-signal-safe on Solaris. Andrew to ask HP whether pthread_cancelstate() is async-signal-safe on HP-UX. +Bug 0000672: Necessary step(s) to synchronize filename operations on disk OPEN http://austingroupbugs.net/view.php?id=672 Geoff has a new proposed resolution in note 1618. Decided to solicit input from FS developers. Eric to go to Linux, David to AIX and Jim to Solaris. Jim has completed his action (see bugnote 1691). Andrew should chase HP and Apple for input. +Bug 0000663: Specification of str[n]casecmp is ambiguous reopened http://austingroupbugs.net/view.php?id=663 Action on David to follow up with the IBM developers about the EBCDIC collation sequence. Bug 696 either NAME_MAX shouldn't be optional, or readdir_r() needs clarification http://www.austingroupbugs.net/view.php?id=696 Don has an action to propose a resolution. Bug 0000721: Internal storage vs static storage OPEN http://austingroupbugs.net/view.php?id=721 This item is still open. Bug 0000375: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef OPEN http://austingroupbugs.net/view.php?id=375 This is still left open due to discussions pending on the reflector. Bug 0000789: Add set -o pipefail OPEN http://austingroupbugs.net/view.php?id=789 * Current Business - Open Actions Bug #851: pthread_atfork orphans handlers in unloaded shared libraries OPEN http://www.austingroupbugs.net/view.php?id=851 Action item: Andrew should try and contact to Finnbarr Murphy. (Status: Andrew has sent a query to Finnbarr via linked.in and also to his direct email - no update this week) Bug #854: requirement for additional built-in utilities to be searched for via $PATH was not and is not existing practice OPEN http://austingroupbugs.net/view.php?id=854 Action: Andrew to ask David Korn to comment on this bug and the previous email discussion of the issue (seq 21270). Action completed - awaiting response from David. Bug #859: Add posix_random family of interfaces OPEN http://austingroupbugs.net/view.php?id=859 Action on The Open Group Base WG to respond whether they will sponsor. - Bug processing Bug #857: Make rules which do not create the target file or do unexpected things with its timestamp re-OPENED http://austingroupbugs.net/view.php?id=857 Comments were received after the previous meeting and a further response is being prepared - we will revisit next week. Bug 0000865: Use of % or $ in subst1 while expanding $(string1:subst1=[subst2]) should be avoided Accepted as Marked http://austingroupbugs.net/view.php?id=865 This item is tagged for TC2-2008 Interpretation response: The standard states the requirements for macro substitution in make, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Long standing existing practice is to treat a % in macro substitution as special (to perform pattern expansions). Notes to the Editor (not part of this interpretation): On page 2941 line 97280 section make Change from: If string1 in a macro expansion contains a macro expansion, the results are unspecified. to: If string1 in a macro expansion contains a macro expansion, the results are unspecified. If a character appears as part of subst1 or subst2 after any macros have been recursively expanded, the results are unspecified. On page 2954 line 97849 section make Change the FUTURE DIRECTIONS section from: None. to: A future version of this standard may require that macro expansions using the forms $(string1:[op]%[os]=[np][%][ns]) or ${string1:[op]%[os]=[np][%][ns]} are treated as pattern macro expansions. Bug #866: No precedence between include lines and macro definitions Accepted as Marked http://austingroupbugs.net/view.php?id=866 This item is tagged for TC2-2008 Add the following to APPLICATION USAGE: after line 97603 This version of POSIX.1:2008 does not specify precedence between macro definition and include directives. Thus the behavior of include =foo.mk is unspecified. To define a variable named include, either the whitespace before the should be removed, or another macro should be used, as in INCLUDE_NAME = include $(INCLUDE_NAME) =foo.mk On the other hand, if the intent is to include a file which starts with an , either the filename should be changed to ./=foo.mk, or the makefile should be written as INCLUDE_FILE = =foo.mk include $(INCLUDE_FILE) Next Steps ---------- The next call is on September 25, 2014 (a Thursday) Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: http://posix@posix.rhansen.org:9001/p/201x-mm-dd password=2115756#