| Summary: | dev-util/codeblocks-9999 fails to build (PATCH) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | brankob |
| Component: | Current packages | Assignee: | Sergey Torokhov <torokhov-s-a> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | jstein, proxy-maint, wxwidgets |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
first patch
second patch |
||
Created attachment 764452 [details, diff]
second patch
Thank you for report and patches! I hope to check it this weekend with gcc-11.2.0 and one of 11.2.1 Could you please attach full build.log for USE="contrib" (with FileManager anabled)? I have installed app-admin/gamin + dev-libs/libgamin (but not installed app-admin/fam) and configuration phase with USE="contrib" for codeblocks-9999 works for me. The build.log for second issue also will be usefull. The second patch is already in upstream. I can't reproduce the build issue for FileManager for latest stable gcc-11.2.1_p20220115. Maybe it was also fixed by upstream. I close this issue as obsolete. Please fill free to reopen it if build process will fail again with the same error. Please attach the full build.log next time. |
Created attachment 764451 [details, diff] first patch it seems that there are two issues: 1. FileManager modules relies on fam and its configuration fails to use app-admin/gamin. I've disabled it in the ebuild by changing the ebuild to skip that module. It manifests during the confire of somethign deep in its bowels, whicgh seeks for fam and doesn't find it on systems that have gamin. I tried to find it but got lost in a quagmire of different build systems. So basically I deactivated the File manager module by changing the ebuild line to in src_configure/econf to : $(use_with contrib contrib-plugins all,-FileManager) 2. Code has shitty include dependency, which fails with latest regular gcc versions ( I'm using gcc-11.2.1_p20220115), which don't tolerate this. I've fixed that with two attached patch files.