Summary: | setools-3.1 configure fails with BWidget 1.7 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Steve Arnold <nerdboy> |
Component: | Current packages | Assignee: | Chris PeBenito (RETIRED) <pebenito> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Updated setools 3.1 ebuild |
Description
Steve Arnold
![]() ![]() Created attachment 116875 [details]
Updated setools 3.1 ebuild
I've already updated the bwidget package to 1.8.0 (all ~arch for now).
It's actually configure.ac that's somewhat brain-dead here; I played with modifying the auto_path thing as described in the docs, and although it made it past the Tk load error, it never did properly detect BWidget (and I tried several different install locations). I made a patched version of the setools ebuild that used and installed the internal 1.8.0 bwidget, but that was just more trouble than it was worth. This one works fine so far on x86 and amd64, and I should be able to try it on ppc later on today. I haven't been able to reproduce this on any of my 3 amd64 machines :\ Weird... I assume you're doing: app-admin/setools-3.1 USE="X" ? Yes. I was able to finally reproduce the problem with configure, but once I added --disable-bwidget-check it still worked fine with bwidget 1.7. Are there any specific errors or misbehaving widgets in the apol gui that I can look for (I didn't see any)? I got a Tcl/Tk error box when I tried to run apol. It only worked with 1.8 for me (at least on amd64). set dep to 1.8 in 3.1 and 3.2. |