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.
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 MESSAGE
Dear Fink developers,
Many of you will have noticed a lot of changes in the stable tree over
the past day. I am attempting to ensure that a user who installs Snow
Leopard on the day it is released, and sticks to the stable tree, will
not see any compile failures. I may or may not finish in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David R. Morrison wrote:
> Dear Fink developers,
>
> Many of you will have noticed a lot of changes in the stable tree over
> the past day. I am attempting to ensure that a user who installs Snow
> Leopard on the day it is released, and sticks to
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.
T
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 wit
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 gcc44)
I have added...
Distribution: 10.4
to gcc4 and...
Distribution: 10.4, 10.5
to gcc42 and gcc43 in fink unstable to
prevent users from trying to use these
packages under 10.6. While we could try
backporting all of the changes I had
committed to gcc 4.4 for darwin10
compatibility, it might be e
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). The
On Tue, Aug 25, 2009 at 08:54:21PM -0400, Jack Howarth wrote:
>I have added...
>
> Distribution: 10.4
>
> to gcc4 and...
>
> Distribution: 10.4, 10.5
>
> to gcc42 and gcc43 in fink unstable to
> prevent users from trying to use these
> packages under 10.6. While we could try
> backporting a
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
12 matches
Mail list logo
