Summary: | dev-lang/lazarus-0.9.22-r1 won't compile due problems with svn2revisioninc.pas | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcel Klein <marcel> |
Component: | Current packages | Assignee: | Maintainers for Miscelleneous Language Packages [OBSOLETE] <lang-misc+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fauli, seventhguardian |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 183725 | ||
Bug Blocks: | |||
Attachments: | Lazarus output when I try to compile a project |
Description
Marcel Klein
2007-06-29 07:28:24 UTC
Have you made any modifications to /etc/fpc.cfg ? And if you have, could you please show your configuration? No. It is the standard gentoo configuration, so no modifications. This is caused by a change in portage behaviour. The version you are using is more aggressive in stripping packages' object files. I've asked the portage people about it, and I've added RESTRICT=strip to the fpc ebuild until I have an answer. If you would please re-sync, and then re-emerge fpc, you should have no more problems with building lazarus. Thanks for the report. I'll keep this report open until the proper action is decided. I see. But you are right for now it compiles fine, thank you. Created attachment 123491 [details]
Lazarus output when I try to compile a project
Hm, sorry to bother you again but I guess there are still some problems left (but I'm not sure if it has the same background...)
When I try to compile a project in lazarus I always get these errors [see attachment]
Even if I just start a new project and try to compile it, so I'm not able to compile any graphical projects.
Thank you again, that is the same problem. I had disabled the stripping for fpc's units, but lazarus installs its own units, so it needs to be disabled temporarily in the ebuild for lazarus too, which I've now done. Ok, works. Thank you. Hello, How about closing the bug then? :) Reported as fixed. This was never fixed, this was worked around. It's fixed now. |