On Tue, Nov 11, 2008 at 02:15:29PM +0000, Jörn Engel wrote: > On Tue, 11 November 2008 15:01:46 +0100, Johannes Berg wrote: > > > > Well, sort of. The patch is actually determined at sparse build time, so > > right now sparse requires you to build it against the same compiler that > > you are currently using. If you rebuild sparse with your shiny new > > compiler you'll notice that it'll end up with a different path in > > pre-process.h. > > Then the short-term solution for debian is clear. Simply rebuild the > package and add a dependency on a specific gcc version. Which sucks badly because the default gcc is not always the same on every arch, and more importantly, people may want to use different GCCs. It would look like a better idea to ask gcc for its include path properly. -- ·O· Pierre Habouzit ··O madcoder@xxxxxxxxxx OOO http://www.madism.org
Attachment:
pgpoCJda348e5.pgp
Description: PGP signature
