-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David R. Morrison wrote:
| There is one other issue, though, which is how we handle the upgrade to
| the 10.4 tree. We've discussed this a few times without ever reaching
| a conclusion.
Well, 1) no need to upgrade to intel/10.4 (nobody has it of
On Nov 28, 2005, at 12:30 PM, TheSin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So what needs to get done before we can start a 10.4 (gcc4) tree,
as the rumors that x86 will be out in Jan and it will REQUIRE gcc4
only. I'm willing to help where I can to help speed this up.
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So what needs to get done before we can start a 10.4 (gcc4) tree, as
the rumors that x86 will be out in Jan and it will REQUIRE gcc4
only. I'm willing to help where I can to help speed this up.
- ---
TS
http://southofheaven.org/
Chaos is the beg
On Aug 8, 2005, at 10:44 AM, Martin Costabel wrote:
Lacking instructions on how to run my own 10.4 tree
Instructions have now been added to the wiki, at
http://ldx3.psfc.mit.edu:2500/akhfinkwiki/published/The+10.4+tree
Please let me know if these need clarification or correction.
-- Dave
On Aug 8, 2005, at 10:44 AM, Martin Costabel wrote:
Lacking instructions on how to run my own 10.4 tree and therefore
how to find real problems with it,
Martin: I am making some instructions, but will have to wait until SF
finishes their scheduled upgrade of CVS services.
I am at the st
Lacking instructions on how to run my own 10.4 tree and therefore how to
find real problems with it, I am at the stage of imagining problems:
Concerning C++ code libraries in the future 10.4 tree, IIUC there will
be two non-intersecting subtrees ("T4" and "T3"), the first one compiled
with g++
On Jul 5, 2005, at 10:58 PM, Philip Lamb wrote:
Obviously we have 10.4-transitional using g++-3.3, but how is Fink
going to enforce a complete rebuild of c++-based packages for users
under 10.4? Another issue is that we will potentially have packages
which cannot link to anything pre gcc4..
Hi all,
Can anyone illuminate a little as to what the current strategy is for
implementation of a 10.4 tree?
Obviously we have 10.4-transitional using g++-3.3, but how is Fink
going to enforce a complete rebuild of c++-based packages for users
under 10.4? Another issue is that we will pot
