On 2011-12-31 17:04:19 +0100, Matthias Klose wrote: > A wrapper will never remind you using the new library paths at runtime.
At runtime? Do you mean that one needs to change the library path also for running the generated executable? The README.Debian file doesn't say anything like that. According to the README.Debian file, the wrapper is just what we need. > The snapshot package is meant to get early feedback about the > development version of GCC, either for a rebuild test, or to easily > test for compiler errors on porter boxes. It's not a package meant > for regular development. I really prefer to have users either set > environment variables or create the wrapper scripts on their own. The package description doesn't say that it isn't for regular development. BTW, is there any reason why gcc-snapshot needs the library path to be changed explicitly (to run the compiler) while this is not needed for gcc-4.4, gcc-4.5, etc.? -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- 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/20111231192441.gj5...@xvii.vinc17.org
