Matthias Klose, le Mon 30 Apr 2012 12:41:49 +0200, a écrit : > On 30.01.2012 16:10, Samuel Thibault wrote: > > Samuel Thibault, le Mon 30 Jan 2012 11:17:42 +0100, a écrit : > >> I have a package which would like to build a gcc plugin. I should > >> however not make it build-depend on a particular gcc-4.[567]-plugin-dev > >> package as the default version changes over time. Could gcc-defaults > >> also provide a gcc-plugin-dev package? > > > > Actually, thinking a bit more about it, I guess I actually have > > to build my plugin several times, once for each supported gcc > > version. So we'd need something similar to python, i.e. something > > like gcc-all-plugin-dev, and a way to iterate over all supported gcc > > versions. > > Is this really needed? many plugins need modifications for different GCC > versions, and it should be easy to add such a "loop" or make magic to build > for > different versions. There are not (yet) that many plugins for GCC.
My comments were before our discussion about a dpkg trigger to rebuild the plugins automatically. I agree that we can't really blindly hope that plugins can compile with newer versions. Samuel -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120430174847.gk11...@type.famille.thibault.fr