On Saturday, June 28, 2003, at 02:07 PM, Max Horn wrote:
Now, to ensure that really the correct GCC is used, we could insert our own symlinks for gcc into the $PATH during the compile phase - a bit like the /sw/bin/cc symlinks cctools-extra installs. In particular, that symlink would point to either /usr/bin/gcc2, /usr/bin/gcc3 or /usr/bin/gcc-3.3. Of course we'd have to make sure cctools still works, if installed, which complicates things a bit more. And of course we have to inserts lots of error checking code etc. (we could even go so far and first "ask" gcc for its version to deal with unknown GCC versions etc.)
A bit cleaner would be to just provide proper default values of CC/CXX etc. environment / make variables. Alas, I am not confident that this will have any effect in general, so it probably isn't generic enough for our needs.
With this approach, we'd effectively guarantee that exactly the GCC version we want is used for compilations, no matter what the user does with gcc_select. We can also easily switch to gcc 3.3, if desired, again w/o having to force the user to do a gcc_select.
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
