I'm actually a little confused as to why each *package* needs the gcc:
3.1 | 3.3 flags. Its only important to which version of gcc3 we compile
with, not which code we compile.
Shouldn't fink just keep track of which gcc3 a given package was
compiled with instead of making a duplicate info file f
Hi. After the discussion last week, I agree with you, and don't plan to have
fink invoke gcc_select. In fact, I've put code into fink on CVS which
checks that version of gcc you are running (when it matters, as indicated
by the GCC directive), and if the version is incorrect, advises you to
run g
John Davidorff Pell <[EMAIL PROTECTED]> wrote:
> I'm actually a little confused as to why each *package* needs the gcc:
> 3.1 | 3.3 flags. Its only important to which version of gcc3 we compile
> with, not which code we compile.
> Shouldn't fink just keep track of which gcc3 a given package was
