Hi folks:
I started a clean stable 64-bit for 10.6 for purposes of testing
migration of some of my packages to stable.
Although gcc44 is in stable, its dependency libmpfr1 is not, so gcc44
won't build in stable.
HTH,
Bill
William G. Scott
Contact info:
Fixed.
-- Dave
On Sep 5, 2009, at 5:23 PM, William G. Scott wrote:
Hi folks:
I started a clean stable 64-bit for 10.6 for purposes of testing
migration of some of my packages to stable.
Although gcc44 is in stable, its dependency libmpfr1 is not, so gcc44
won't build in stable.
Dave,
Thanks. Since Apple has effectively orphaned FSF gcc, I have
spent a lot of time making sure that the current release is
patched up to remove false failures in the gcc testsuite so
real bugs are exposed. Those changes would all have to be
backported to the earlier gcc releases to make
Hi,
I learned from the commit messages (see below) that packages in stable
using gcc43 cannot be used on x86_64. I have gcc44 version for all of
my packages in unstable, but I cannot move them as gcc44 is not yet
stable. Any plans to promote gcc44 to stable?
Thanks,
Remi
On Aug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remi Mommsen wrote:
Hi,
I learned from the commit messages (see below) that packages in stable
using gcc43 cannot be used on x86_64. I have gcc44 version for all of my
packages in unstable, but I cannot move them as gcc44 is not yet stable.
Any
I have no objections to any of the gcc4X packages in unstable
being moved to stable. It would be nice if all of them were
since they pave the way for installing gcc45 when released.
Jack
On Tue, Aug 25, 2009 at 03:46:23PM -0400, Alexander Hansen wrote:
-BEGIN PGP SIGNED
Let me encourage you guys to wait until I've finished monkeying with
stable, with the goal of making sure everything in stable compiles on
10.6 when it is released. That process should be finished by Friday
or Saturday, and then we can think about what other things to move to
stable.
Dave,
I assume you are taking about i386 support only for 10.6 as the
gcc44 package is required for x86_64 fink support on either
Leopard or SL.
Jack
On Wed, Aug 26, 2009 at 06:43:57AM +0900, David R. Morrison wrote:
Let me encourage you guys to wait until I've finished monkeying
I just noticed that we need to limit gcc42 and gcc43 to build
only on 10.4 and 10.5. Only gcc44 and later will contain the
necessary checks for darwin10. They may build on darwin10 but
will have flawed testsuite results. If you are planning a
10.6 release with either of the those (instead of
Just to clarify this issue with gcc in more detail. While those
gcc releases which don't recognize darwin10 could be run on darwin10
as prebuilt binaries, the compiler itself would be miscompiled under
darwin10 (so you can't build the package itself but could run a
copy built under darwin9).
Thanks, Jack.
For the current push to get the stable tree ready for 10.6 before
Friday, we'll suppress all of the gcc42 and gcc43 dependent packages
from 10.6 under both architectures. There will be plenty of time in
coming weeks to fix everything in unstable and then move to stable
when
11 matches
Mail list logo
