Summary: | [gcc4] pam and shadow not compiling due to pam headers problem | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Markus Rothe (RETIRED) <corsair> |
Component: | [OLD] GCC Porting | Assignee: | PAM Gentoo Team (OBSOLETE) <pam-bugs+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | halcy0n, ppc64 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 117482 | ||
Attachments: |
pam-0.78-r2.txt
shadow-4.0.7-r3.txt /usr/include/asm-ppc64/types.h pam fix shadow fix new and improved pam fix :) |
Description
Markus Rothe (RETIRED)
2005-09-27 11:57:44 UTC
Created attachment 69360 [details]
pam-0.78-r2.txt
Created attachment 69361 [details]
shadow-4.0.7-r3.txt
Created attachment 69362 [details]
/usr/include/asm-ppc64/types.h
Want to try this again with a newer gcc-4 (4.1.0_beta, maybe)? same result using 4.1.0-beta20051216 Both of these occur for the same reason. A user space header is defining __u8 before asm/types.h is pulled in. Just need to reorder the includes so this happens. Created attachment 76871 [details, diff]
pam fix
Created attachment 76872 [details, diff]
shadow fix
base-system and pam-bugs, please apply the patch for your app. Thanks :) i dont like it at all Yea, this way does suck. I'll just fix the pam header. Created attachment 76877 [details, diff]
new and improved pam fix :)
Since our pam is linux only, I can go ahead and just include asm/types.h, as far as I know.
Actually, pam works fine on gcc4 on amd64. Can someone point why ppc64 and amd64 differs? Okay added a patch that should fix this. |