On Sunday, Jun 29, 2003, at 12:12 US/Eastern, David R. Morrison wrote:
What does this imply for
our binary distribution?
fyi, Debian renamed almost every C++ library package to deal with this
one.
---
This SF.Net email sponsored by: Free pre-
Hi Max.
There are really two issues here:
1) how do we ensure that our users are using the gcc version we expect?
2) how do we transition from gcc 3.1 to gcc 3.3?
I agree that we could do a much better job with #1 than we have in the past.
However, at the moment I'm more concerned about #2.
Yo
regardless I think this is a great idea and should be implemented even
right now in 10.2
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 th
just an idea but while reading this I got an idea
I like the fink.conf value but it shouldn't be able to be modded by the
user
so regarless we set it at bootstrap and in the fink pkg or base-files
lets add a util that they can move up that value with, it would then
get all the pkgs with a GCC:
So, how to deal with the ABI changes (again).
Let's first see what exactly we have to deal with:
1) We need to ensure that all the C++ code on a system is compiled with
the same version of GCC, either 3.1 or 3.3. (exceptions can be made for
C++ code which is completely self contained, i.e. whic
