Summary: | dev-db/libiodbc-3.52.7 fails to build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Kahle (RETIRED) <tomka> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log with failures |
Description
Thomas Kahle (RETIRED)
2011-11-12 13:29:48 UTC
Created attachment 292275 [details]
build.log with failures
OK, it builds fine with USE="-gtk" Here's what I have installed: eix -e gtk+ [I] x11-libs/gtk+ [...] Installed versions: 2.24.5-r1(2)(09:02:16 PM 11/12/2011)(cups introspection xinerama -aqua -debug -doc -examples -test -vim-syntax) 3.0.12-r1(3)(09:11:35 PM 11/12/2011)(cups introspection xinerama -aqua -debug -doc -examples -test -vim-syntax) Looks like a RescueCD path failure. But on a not quite related note: could we patch #if (_MSC_VER >= 900) line of /usr/include/iodbc/sqltypes.h to read #if defined(_MSC_VER) && (_MSC_VER >= 900) cause the former causes a lot warning noise on any recent (well, by now, not quite so) gcc version ? yeah right. It's a false positive. Does not occour outside of the chroot. Does it still fail if you build with the new ebuild and patches in bug 450782? (In reply to comment #5) > Does it still fail if you build with the new ebuild and patches in bug > 450782? If it was a RescueCD failure, most likely it will still happen - those are due an implementation detail of libtool, not any particular package. Though, AFAICT, the header problem I've mentioned is still present. are you still hitting this with 3.52.8-r2? |