Re: [Fink-devel] gcc_select 3

2003-10-02 Thread David R. Morrison
We're still in the process of upgrading packages to be ready for gcc 3.3.
The "enforcement" of the fink declaration "GCC: 3.1" was not done in the
past, but is now being done with the recent upgrade.

Your best strategy if you are using panther is to make sure that the
dists symlink points to 10.2-gcc3.3 .  In that tree, you'll find that
all stable packages can be compiled with gcc 3.3.

For packages in 10.2-gcc3.3/unstable, you might need to edit the GCC line
in the info file from 3.1 to 3.3.  We're working on this, but each package
needs to be tested.

  -- Dave


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel


[Fink-devel] gcc_select 3

2003-10-02 Thread Yarden Livnat
Greatings,

I have upgraded to fink 13.9 from the cvs and run ./inject.pl
I'm running on Panther which means I'm using gcc3.3 by default
I had very few problems compiling programs via fink, that is until 
today. Now that the gcc_select is up it forces me to switch to 
"gcc_select 3" before compiling. This is bad as everything else in 
compiled with 3.3 not 3.1 . I don't understand why it thinks I have to 
use 3.1 even when the same program compiled fine before on 3.3...

I also tried to fix the link: dists -> 10.2-gcc3.3 but to no avail.

I am not a fink developer and thus use the anonymous@ cvs. (I don't 
know if this is the cause).

any pointers how I can avoid the select_gcc 3 ?

thanks,

	Yarden 



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel