Has anyone started to consider how we should handle
the release of the gcc 4.2 compilers for Xcode 3.0 once
they are out of the Preview stage? I am wondering if we
might modify fink to detect the installation of the
Apple gcc 4.2 compilers and default over to them unless
the package used a flag
sounds reasonable.
most packages should just work with 4.2
but complicated ones will need patches
I think support for 4.2 in fink should be enabled as early as
possible, so that "beta testers of 4.2" could report issues
On 12/11/07, Jack Howarth <[EMAIL PROTECTED]> wrote:
>Has anyone started
Alexey,
What I had in mind was to default fink to use the gcc-4.2 and
g++-4.2 compilers if present on a system but to allow both the
ability to override this behavior on an info file basis as well
as system-wide through an optional entry in fink.conf.
I really would be a good idea to beat on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jack Howarth wrote:
> Alexey,
>What I had in mind was to default fink to use the gcc-4.2 and
> g++-4.2 compilers if present on a system but to allow both the
> ability to override this behavior on an info file basis as well
> as system-wide through
Benjamin,
I would still like to see some way to do a quick and dirty
port of fink unstable to the new compilers. How about just providing
an option in fink.conf to allow the user to default his info files
to build on GCC 4.2 regardless if they are set to GCC 4.0?
The idea would be to make it ea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jack Howarth wrote:
> Benjamin,
> I would still like to see some way to do a quick and dirty
> port of fink unstable to the new compilers. How about just providing
> an option in fink.conf to allow the user to default his info files
> to build on G
On Tue, December 11, 2007 10:20, Benjamin Reed wrote:
>> I would still like to see some way to do a quick and dirty
>> port of fink unstable to the new compilers. How about just providing
>> an option in fink.conf to allow the user to default his info files
>> to build on GCC 4.2 regardless if
Matthew,
Can you give me some advice on how to modify the current
fink cvs code to default over to the Apple gcc 4.2 compilers?
Apple has named them gcc-4.2 and g++-4.2 so they don't collide
with our gcc packages. I would like to stress test these compilers
in the next few weeks.
On Dec 11, 2007, at 9:56 AM, Benjamin Reed wrote:
Jack Howarth wrote:
Alexey,
What I had in mind was to default fink to use the gcc-4.2 and
g++-4.2 compilers if present on a system but to allow both the
ability to override this behavior on an info file basis as well
as system-wide through an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Johnson wrote:
> No, fortunately, the ABI didn't change. 4.2.1 should be a drop-in
> replacement, assuming that stricter error checking and/or bugs don't
> cause problems. Of course, we all know what happens when we assume... :)
Ah, if that's
Benjamin,
That sounds great, but we should still provide a way for
an info file to force gcc-4.0 and g++-4.0 to be used
even in the presence of gcc-4.2 and g++-4.2. It would also
be nice to provide a fink.conf option to do the same
globally. That should prevent anyone from complaining about
bei
On Dec 11, 2007, at 2:27 PM, Jack Howarth wrote:
Benjamin,
That sounds great, but we should still provide a way for
an info file to force gcc-4.0 and g++-4.0 to be used
even in the presence of gcc-4.2 and g++-4.2. It would also
be nice to provide a fink.conf option to do the same
globally. Th
On Dec 11, 2007, at 10:47, Jack Howarth wrote:
Can you give me some advice on how to modify the current
fink cvs code to default over to the Apple gcc 4.2 compilers?
Apple has named them gcc-4.2 and g++-4.2 so they don't collide
with our gcc packages. I would like to stress test these compile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Sachs wrote:
> From a cursory inspection, it looks like Fink just takes the system's
> default. Leopard doesn't have gcc_select, so use the attached with_gcc
> script. A la sudo, prefix any command you want to execute with
> "with_gcc" and i
On Tue, Dec 11, 2007 at 10:53:31PM -0500, Benjamin Reed wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Matthew Sachs wrote:
>
> > From a cursory inspection, it looks like Fink just takes the system's
> > default. Leopard doesn't have gcc_select, so use the attached with_gcc
> > scr
15 matches
Mail list logo
