The current Fink release (0.36.4.1) dynamically generates the compiler wrappers for clang/clang++ (via functions in Fink::PkgVersion). We currently remove the wrappers when updating fink, and new ones are generated for the next build operation. This isn't 100% reliable, though.
I've generated a work-in-progress branch in the fink github repository (i.e. I don't think it's quite ready to be a pull request) called "compiler_wrapper_in_deb". As the name suggests, in this branch all of the compiler wrappers get installed in the .deb. Fink::PkgVersion hasn't been altered, because I haven't had time to explore the full ramifications of altering the wrapper generation there (not well commented or documented). For example, are temporary wrappers generated to build dpkg-bootstrap? Also, in the event of user error, in principle the various ensure* functions will attempt to regenerate the compiler wrappers, which is useful. Though I'd argue that it's poor from a maintenance standpoint to have separate copies of the wrapper scripts stored as heredocs within PkgVersion.pm and as normal files, which is what we've been doing for a while now. Anyway, feedback is appreciated. -- Alexander Hansen, Ph.D. Fink User Liaison My package updates: http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
