Re: popen returns int (do I need to define __USE_POSIX2 etc?)
- From: mark.bergman@xxxxxxxxxxxxx
- Date: 28 Apr 2006 08:09:01 -0700
mark.bergman@xxxxxxxxxxxxx wrote:
I am using RHEL 4 (amd64), and I made a short program calling popen(),
including <stdio.h>
It seems that popen() returns an int, not FILE* as per the manual page!
I have found that (as well as -ansi) I need to use -D_POSIX_C_SOURCE=2
(is this the best option?)
However, I have another warning being generated from strdup() prototype
not being included - what am I supposed to define to avoid that?
Mark
.
- References:
- popen returns int (do I need to define __USE_POSIX2 etc?)
- From: mark . bergman
- popen returns int (do I need to define __USE_POSIX2 etc?)
- Prev by Date: popen returns int (do I need to define __USE_POSIX2 etc?)
- Next by Date: Permission to mount disks
- Previous by thread: popen returns int (do I need to define __USE_POSIX2 etc?)
- Next by thread: Permission to mount disks
- Index(es):
Relevant Pages
|
