On Mon, Jun 20, 2011 at 12:35:07PM +0200, Matthias Klose wrote: > > cpp's preprocessing behavior is architecture independent > I don't think so. the predefined macros differ depending on the > architecture / operating system. Ok, true. > > but its header > > search paths are not. Could accidentally installing a foreign arch version > > of cpp break native packages that depend on it finding the native headers? > why not, assuming that there is architecture dependent information in an > architecture specific header? > for the use of cpp to preprocess an series.in file (python2.7 package), I'm > relying on the architecture pre-defines. Alright. Then cpp should be Multi-Arch: allowed, and those reverse-depends which don't care about architecture defines and includes can use the ':any' syntax to depend on cpp. > Is this only an issue with cpp, or with gcc too (holding headers and .o > files) too? I haven't yet encountered any cases where this matters for gcc, so I would recommend only changing cpp for now. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature