Steve Langasek wrote: > I can't imagine any sane reason why you should need to build-conflict > against a version of the compiler. It certainly isn't warranted for any > package that properly uses "gcc" and "g++" as the names when invoking the > compiler.
libextractor uses automatically gcc-3.3 if installed, instead of gcc-4.0 (due to some issues with MacOSX in the past). > If your package's build rules are for some reason trying to > invoke "g++-3.3" when present, you should fix *that*, not add a spurious > build-conflict. Ok, thanks for clarification. -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
