This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/66722] New: libiberty/pex-unix.c warning: initialization from incompatible pointer type
- From: "richard at netbsd dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 01 Jul 2015 14:15:57 +0000
- Subject: [Bug other/66722] New: libiberty/pex-unix.c warning: initialization from incompatible pointer type
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66722
Bug ID: 66722
Summary: libiberty/pex-unix.c warning: initialization from
incompatible pointer type
Product: gcc
Version: 4.9.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: richard at netbsd dot org
Target Milestone: ---
Created attachment 35886
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35886&action=edit
pex_unix_wait returns pid_t (as does wait())
noticed while building:
>../../gcc-4.9.3/libiberty/pex-unix.c:325:3: warning: initialization from incompatible pointer type
>../../gcc-4.9.3/libiberty/pex-unix.c:325:3: warning: (near initialization for 'funcs.wait')
>../../gcc-4.9.3/libiberty/pex-unix.c:325:3: warning: initialization from incompatible pointer type
>../../gcc-4.9.3/libiberty/pex-unix.c:325:3: warning: (near initialization for 'funcs.wait')
attached patch get over the int/pid_t confusion:
Also, from inspection I noticed waitpid() needs correction too.