Summary: | confcache-0.3.3 breaks mysql-5.0.16 at innobase configure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ed Catmur <ed> |
Component: | [OLD] Development | Assignee: | Brian Harring (RETIRED) <ferringb> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | flameeyes, vivo |
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ed Catmur
2005-11-23 04:24:19 UTC
autoconf setup doesn't like cache, offhand. mono is the same way. Not sureabout how to fix this one besides introducing a RESTRICT="confcache" of some sort when portage integration occurs- thoughts? If I add "--cache-file=/dev/null" at configure in the ebuilds could that help ? no it does'nt help, ./configure [...] --cache-file=/dev/null [...] --build=i686-pc-linux-gnu --cache-file config.cache now if portage put it _before_ the ebuild defined options no other changes and documentation is needed. cheers Diego, your change fixes this right? Ed, my bzr repo is at http://dev.gentoo.org/~ferringb/bzr/confcache , game for trying a checkout for verification? Hmm no, my changes checks for CC before invalidating it and should resolve that part (basically it should ignore CC changing as long as it's the same that's cached) but the problem with CFLAGS remains. And it's not a problem of confcache, it's _really_ a problem of the buildsystem, CFLAGS shouldn't be abused in general, and in particular when using cygnus-style sub-configures. Fix via adding RESTRICT="confcache" |