| Summary: | sci-libs/indilib-0.6 fails multilib-strict | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Arttu Valo <arttuv69> |
| Component: | [OLD] Library | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | QA | Keywords: | InVCS |
| Priority: | High | ||
| Version: | 2008.0 | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log showing the multilib-strict failure at the end | ||
|
Description
Arttu Valo
2009-09-14 13:47:23 UTC
PLease provide more information and reopen bug. Atleast the complete build.log is needed. Created attachment 204120 [details]
build.log showing the multilib-strict failure at the end
Darn, sorry for snipping out the two lines of portage message which explicitly stated the multilib-failure, and not attaching anything.
But I've lived under the delusion(?) that multilib-strict basically just checks the install path, so that libs are not simply dumped to /usr/lib, but into /usr/$(get_libdir). So I expected it to be sort of self-evident and easily reproducible without attachments. Anyway, here's a build.log from one of my old amd64 boxes.
(In reply to comment #2) > the install path, so that libs are not simply dumped to /usr/lib, but into > /usr/$(get_libdir). So I expected it to be sort of self-evident and easily > reproducible without attachments. Anyway, here's a build.log from one of my old Thats true, but I personally like to see what happened to the reporter even when it is that trivial. Sometimes it is only on the first view that easy and there are some really strange things in the user setup. But thanks for reporting, reopen bug. Fixed in cvs. Thanks for report. |