Summary: | aiksaurus-1.0.1 failes to build with gtk 2.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kristiaan Lenaerts <kristiaan.lenaerts> |
Component: | Current packages | Assignee: | Alastair Tse (RETIRED) <liquidx> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | charon |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 45747 | ||
Attachments: |
the diff for configure
fixed ebuild |
Description
Kristiaan Lenaerts
2004-04-04 06:35:47 UTC
Created attachment 28679 [details, diff]
the diff for configure
*** This bug has been marked as a duplicate of 45747 *** Created attachment 28823 [details]
fixed ebuild
updated the ebuild to apply the patch, I'm not sure if there should be a
revision bump (if you have it compiled before, there is no reason to switch,
it's only a compile issue)
If Kristiaan Lenaerts' updated ebuild works, can it be incorporated in portage? I'm having this problem too... BTW why is it "Resolved - Duplicate" when the bug is still there? my mistake I just tried Kristiaan Lenaerts' ebuild. It complains that $EPATCH_SOURCE doesn't exist, which is of course: /usr/portage/app-text/aiksaurus/files/gtk+-2.4-fix.patch So that doesn't work either, how do I get it to build? I need lyx :( Are you sure you placed the patch (wrongly named "the diff for configure", my fault) in the rigth directory? The only way I can reproduce your problem is when I rename the patch to something else, or when there is no patch at all. The reason I started this bug was for lyx too, you can always install aiksaurus-0.15 and go on from there, that worked fine over here. Daath, does this patch work for you now? Over here, I have not a single problem, but if it doesn't work for you, and there is no extra info, the solution will never get into portage. I'm marking this bug as blocking the GTK+-2.4 Tracking bug, mayby this will generate some more interest... Thanks for your report, fixed in cvs. Please test. 1.2.1 released |