Summary: | [configure] --with-macbookpro autodetection broken / build break | ||
---|---|---|---|
Product: | hal | Reporter: | Stef van der Made <svandermade> |
Component: | build | Assignee: | David Zeuthen (not reading bugmail) <zeuthen> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | high | CC: | guenther, svandermade |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | proposed fix |
Description
Stef van der Made
2006-12-23 08:55:06 UTC
Running into the same issue here, hal-0.5.8.1. The mention auto-detection of Macbook Pro obviously fails. Also, neither --without-macbookpro nor --with-macbookpro=no do help. Configure results always include these lines, regardless of the options: use libpci: no build Macbook Pro utils: yes A related issue is, that the Macbook Pro utils should not be enabled anyway, if libpci is not available. I have the same issue. the .configure script always gives back build "Macbook Pro utils: yes" while I say --with-macbookpro=no or --without-macbookpro The source of the problem is a misnamed variable in configure.in The fix is simple: replace: use_macbookpro -> with_macbookpro -Joseph I tried using both options of --with-macbookpro=no or --without-macbookpro and the comment 3 idea and for some reason it is still not working. Created attachment 8390 [details] [review] proposed fix The above patch seems to fix this issue for me, after running some quick tests. Additionally to the already mentioned use_macbookpro oops, usage of HAVE_LIBPCI seems to be false, too. libpci presence is now correctly tested as a condition whether the Macbook Pro utils actually *can* be built or not. Adjusting Summary. Severity major, since this breaks the build. I can confirm the fix for hal-0.5.8.1 This is already fixed in git. Close this bug now |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.