| Summary: | ogre 1.0.4 install fails due to libtool relinking crap | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Carlos Rendon <crendon> |
| Component: | [OLD] Library | Assignee: | Gentoo Games <games> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | crusaderky, fcoiffie, patrick |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
eclass-debug.log
environment Preprocessed source 1 Preprocessed source 2 Preprocessed source 3 Preprocessed source 4 emerge log |
||
|
Description
Carlos Rendon
2005-09-09 08:43:09 UTC
Created attachment 68038 [details]
eclass-debug.log
portage said it would be a good idea to attach this
Created attachment 68039 [details]
environment
portage asked me to post this files with this bug
Created attachment 68040 [details]
Preprocessed source 1
Created attachment 68042 [details]
Preprocessed source 2
Created attachment 68043 [details]
Preprocessed source 3
Created attachment 68044 [details]
Preprocessed source 4
Let's see the actual error messages please. Go ahead and attach the entire output from the merge if that's easier. Created attachment 68052 [details]
emerge log
result of emerge ogre &> ogre.log
not sure what your original comment is talking about, the build fails during install due to some ugly libtool relinking issues i hit this on my amd64 box and wasnt really able to figure out wtf was going on if you do `emerge -C ogre && emerge ogre`, does it work ? That worked beatifully, I do not now why I did not think to try that myself. Although, it really should be able to work without us having to unmerge and then emerge *** Bug 113269 has been marked as a duplicate of this bug. *** *** Bug 115954 has been marked as a duplicate of this bug. *** *** Bug 135026 has been marked as a duplicate of this bug. *** |