OpenPAM/OpenPAM
OpenPAM
/
OpenPAM
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

FOPEN_MAX wasn't such a reliable <stdio.h> indicator after all, so 

use _IOFBF instead.


git-svn-id: svn+ssh://svn.openpam.org/svn/openpam/trunk@269 185d5e19-27fe-0310-9dcf-9bff6b9f3609
This commit is contained in:
Dag-Erling Smørgrav 2003-07-14 23:53:19 +00:00
parent a131b240b3
commit 27480e5170
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
include/security/openpam.h
View File

@ -31,7 +31,7 @@
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* $P4: //depot/projects/openpam/include/security/openpam.h#25 $
* $P4: //depot/projects/openpam/include/security/openpam.h#26 $
*/
#ifndef _SECURITY_OPENPAM_H_INCLUDED
@ -120,10 +120,10 @@ pam_vprompt(pam_handle_t *_pamh,
/*
* Read cooked lines.
* Checking for FOPEN_MAX is a fairly reliable way to detect the presence
* of <stdio.h>
* Checking for _IOFBF is a fairly reliable way to detect the presence
* of <stdio.h>, as SUSv3 requires it to be defined there.
*/
#ifdef FOPEN_MAX
#ifdef _IOFBF
char *
openpam_readline(FILE *_f,
int *_lineno,