Summary: | sys-process/pidof-bsd-20050501-r3 does not use valid ANSI C | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | Richard Yao (RETIRED) <ryao> |
Component: | FreeBSD | Assignee: | Gentoo/BSD Team <bsd+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | QA | Keywords: | Bug |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | FreeBSD | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 408963 | ||
Attachments: |
sys-process/pidof-bsd-20050501-r3 build failure
Patch proposal to fix build failure |
Description
Richard Yao (RETIRED)
2012-05-23 00:06:42 UTC
Created attachment 312771 [details, diff]
Patch proposal to fix build failure
I have attached a patch that fixes this. Let me know if it is okay to commit.
Taking another look at this, we could call this one a bug in Clang, because the build system is passing -std=gnu99 and it is not using the GCC behavior. I would prefer it if we used proper ANSI C though. (In reply to comment #2) > Taking another look at this, we could call this one a bug in Clang, because > the build system is passing -std=gnu99 and it is not using the GCC behavior. > I would prefer it if we used proper ANSI C though. I had a chat with apinski in #gcc on freenode. It seems that the GCC developers consider the return value to be undefined, so the code should return whatever happens to be on the stack or in the return register. its due to a gentoo-made patch: amend pidof-bsd-20050501-pname.patch and commit, should be fine Committed to CVS. |