Compiling for 10.2

[Damon Courtney]

     I mailed a while back but never got a response, so I'm trying  
again.  These are my CFLAGS:

CFLAGS=-arch ppc -arch i386 -mmacosx-version-min=10.2

     Am I doing something wrong to get my build to run on 10.2+?  I  
thought I had it right, but reports from users say that it's not  
working on earlier versions.  Any help (or even response) is  
appreciated.

D

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Tcl-mac mailing list
tcl-mac@...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

[Tim Jones-2]

On Jul 2, 2008, at 9:07 AM, Damon Courtney wrote:

>     I mailed a while back but never got a response, so I'm trying
> again.  These are my CFLAGS:
>
> CFLAGS=-arch ppc -arch i386 -mmacosx-version-min=10.2
>
>     Am I doing something wrong to get my build to run on 10.2+?  I
> thought I had it right, but reports from users say that it's not
> working on earlier versions.  Any help (or even response) is
> appreciated.

Hi Damon,

For 10.2 compatibility, you'll most likely need a live 10.2 system to  
build against.

tim


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Tcl-mac mailing list
tcl-mac@...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

[Kevin Walzer-5]

Damon Courtney wrote:
>      I mailed a while back but never got a response, so I'm trying  
> again.  These are my CFLAGS:
>
> CFLAGS=-arch ppc -arch i386 -mmacosx-version-min=10.2
>
>      Am I doing something wrong to get my build to run on 10.2+?  I  
> thought I had it right, but reports from users say that it's not  
> working on earlier versions.  Any help (or even response) is  
> appreciated.

Do you have the 10.2 SDK installed? That's the first thing you need.

Here is what the README in tk8.5.3/macosx says about building for older
platforms:

- It is also possible to build with Apple's IDE via the projects in
tk/macosx,
take care to only use the project matching your DevTools and OS version:
     * Wish.pbproj for Xcode or ProjectBuilder on 10.3 and earlier, this
has a
        'Tk' target that simply calls through to the tcl/macosx/GNUMakefile. It
        requires a build of the 'Tcl' target of tcl/macosx/Tcl.pbproj.
     * Wish.xcode Xcode 2.4 on 10.4 and Xcode 2.5 on 10.4 and later, which
        additionally has native 'tktest' and 'tktest-X11' targets for
        debugging, these targets' 'Debug' build configuration has ZeroLink and
        Fix&Continue enabled, use the 'DebugNoFixZL' build configuration if you
        need a debug build without these features. The following build
        configurations are available:
        'DebugUnthreaded': debug build with threading turned off.
        'DebugNoCF': debug build with corefoundation turned off
                (for 'tktest-X11' only).
        'DebugNoCFUnthreaded': debug build with corefoundation turned off
                (for 'tktest-X11' only) and with threading turned off.
        'DebugMemCompile': debug build with memory and bytecode debugging on.
        'DebugLeaks': debug build with PURIFY defined.
        'DebugGCov': debug build with generation of gcov data files enabled.
        'ReleaseUniversal': builds the targets as universal binaries for the
                ppc and i386 architectures.
        'ReleaseUniversal10.4uSDK': same as 'ReleaseUniversal' but builds
                against the 10.4u SDK, required to build universal binaries on
                PowerPC Tiger (where the system libraries are not universal).
        'ReleasePPC10.3.9SDK': builds for PowerPC against the 10.3.9 SDK, useful
                for verifying on Tiger that building on Panther would succeed.
        'ReleasePPC10.2.8SDK': builds for PowerPC with gcc-3.3 against the
                10.2.8 SDK, useful to verify on Tiger that building on Jaguar
                would succeed.
     * Wish.xcodeproj for Xcode 3.1 on 10.5 and later, which has the
following
        additional build configurations:
        'ReleaseUniversal10.5SDK': same as 'ReleaseUniversal' but builds
                against the 10.5 SDK on Leopard (with 10.5 deployment target).
        'Debug gcc42':  same as 'Debug' but builds with gcc 4.2.
        'Debug llvmgcc42': same as 'Debug' but builds with llvm-gcc 4.2.
        'ReleaseUniversal gcc42': same as 'ReleaseUniversal' but builds with
                gcc 4.2.
        'ReleaseUniversal llvmgcc42': same as 'ReleaseUniversal' but builds
                with llvm-gcc 4.2.
        'Debug64bit': builds the 'tktest-X11' target as 64bit with debugging
                 enabled (requires a 64bit capable processor).
        Note that all non-SDK configurations have 10.5 deployment target and
                that all Universal configurations build the 'tktest-X11' target
                also for the ppc64 and x86_64 architectures.

Hope this helps,
Kevin

--
Kevin Walzer
Code by Kevin
http://www.codebykevin.com

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Tcl-mac mailing list
tcl-mac@...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

[Damon Courtney]

     I read through the README, but I'm building from the GNUmakefile,  
not the Xcode project.  I don't actually know that I have the 10.2 SDK  
installed though.  I suppose that's a good place to start checking.  
0-]  Thanks, Kevin.

Damon


On Jul 2, 2008, at 11:19 AM, Kevin Walzer wrote:

> Damon Courtney wrote:
>>     I mailed a while back but never got a response, so I'm trying  
>> again.  These are my CFLAGS:
>> CFLAGS=-arch ppc -arch i386 -mmacosx-version-min=10.2
>>     Am I doing something wrong to get my build to run on 10.2+?  I  
>> thought I had it right, but reports from users say that it's not  
>> working on earlier versions.  Any help (or even response) is  
>> appreciated.
>
> Do you have the 10.2 SDK installed? That's the first thing you need.
>
> Here is what the README in tk8.5.3/macosx says about building for  
> older platforms:
>
> - It is also possible to build with Apple's IDE via the projects in  
> tk/macosx,
> take care to only use the project matching your DevTools and OS  
> version:
>    * Wish.pbproj for Xcode or ProjectBuilder on 10.3 and earlier,  
> this has a
> 'Tk' target that simply calls through to the tcl/macosx/
> GNUMakefile. It
> requires a build of the 'Tcl' target of tcl/macosx/Tcl.pbproj.
>    * Wish.xcode Xcode 2.4 on 10.4 and Xcode 2.5 on 10.4 and later,  
> which
> additionally has native 'tktest' and 'tktest-X11' targets for
> debugging, these targets' 'Debug' build configuration has ZeroLink  
> and
> Fix&Continue enabled, use the 'DebugNoFixZL' build configuration if  
> you
> need a debug build without these features. The following build
> configurations are available:
> 'DebugUnthreaded': debug build with threading turned off.
> 'DebugNoCF': debug build with corefoundation turned off
> (for 'tktest-X11' only).
> 'DebugNoCFUnthreaded': debug build with corefoundation turned off
> (for 'tktest-X11' only) and with threading turned off.
> 'DebugMemCompile': debug build with memory and bytecode debugging on.
> 'DebugLeaks': debug build with PURIFY defined.
> 'DebugGCov': debug build with generation of gcov data files enabled.
> 'ReleaseUniversal': builds the targets as universal binaries for the
> ppc and i386 architectures.
> 'ReleaseUniversal10.4uSDK': same as 'ReleaseUniversal' but builds
> against the 10.4u SDK, required to build universal binaries on
> PowerPC Tiger (where the system libraries are not universal).
> 'ReleasePPC10.3.9SDK': builds for PowerPC against the 10.3.9 SDK,  
> useful
> for verifying on Tiger that building on Panther would succeed.
> 'ReleasePPC10.2.8SDK': builds for PowerPC with gcc-3.3 against the
> 10.2.8 SDK, useful to verify on Tiger that building on Jaguar
> would succeed.
>    * Wish.xcodeproj for Xcode 3.1 on 10.5 and later, which has the  
> following
> additional build configurations:
> 'ReleaseUniversal10.5SDK': same as 'ReleaseUniversal' but builds
> against the 10.5 SDK on Leopard (with 10.5 deployment target).
> 'Debug gcc42':  same as 'Debug' but builds with gcc 4.2.
> 'Debug llvmgcc42': same as 'Debug' but builds with llvm-gcc 4.2.
> 'ReleaseUniversal gcc42': same as 'ReleaseUniversal' but builds with
> gcc 4.2.
> 'ReleaseUniversal llvmgcc42': same as 'ReleaseUniversal' but builds
> with llvm-gcc 4.2.
> 'Debug64bit': builds the 'tktest-X11' target as 64bit with debugging
> enabled (requires a 64bit capable processor).
> Note that all non-SDK configurations have 10.5 deployment target and
> that all Universal configurations build the 'tktest-X11' target
> also for the ppc64 and x86_64 architectures.
>
> Hope this helps,
> Kevin
>
> --
> Kevin Walzer
> Code by Kevin
> http://www.codebykevin.com

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Tcl-mac mailing list
tcl-mac@...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

[Daniel A. Steffen]

Hi Damon,

On 02/07/2008, at 18:07, Damon Courtney wrote:

>     I mailed a while back but never got a response, so I'm trying
> again.  These are my CFLAGS:
>
> CFLAGS=-arch ppc -arch i386 -mmacosx-version-min=10.2
>
>     Am I doing something wrong to get my build to run on 10.2+?  I
> thought I had it right, but reports from users say that it's not
> working on earlier versions.

in theory this should be correct (it is exactly what I use to build my  
distros on Tiger with 10.3 compatibility), do you have details on what  
is not working?
there is an open bug about crashes in the macosx notifier on 10.2 with  
tcl built on Tiger or later, maybe that is what is biting you:
     https://sourceforge.net/tracker/?func=detail&aid=1792183&group_id=10894&atid=110894
I no longer have access to a 10.2 system so I cannot debug this myself  
and the reporter never responded to my requests for help with debugging.
My suspicion was that pthread_once() is not working correctly on 10.2,  
i.e. SpinLockLockInit() is never called and so any locking in the  
notifier crashes. If this can be confirmed, I can look into a  
workaround.

Honestly however, supporting 10.2 is not high on the list of  
priorities, indeed I am planning to remove support for 10.2 and 10.3  
from Tcl/Tk HEAD before 8.6.0, we simply have insufficient maintainer  
resources to maintain compatibility so far back.

>  Any help (or even response) is  appreciated.


I have the following magic in my notes about building for the 10.2.8  
SDK, note that you will need gcc-3.3 installed and that you can only  
build for ppc this way. Also, IIRC the 10.2.8 SDK is no longer  
supported with Xcode 3, you may need to install Xcode 2.5 if you're on  
Leopard (in fact I have no idea if this works on Leopard at all, I've  
only ever used it on Tiger).

     export CC='gcc-3.3'
     export MACOSX_DEPLOYMENT_TARGET=10.2
     export NEXT_ROOT="/Developer/SDKs/MacOSX10.2.8.sdk"
     export CPPFLAGS="-arch ppc -D__CONSTANT_CFSTRINGS__ -
DMAC_OS_X_VERSION_MIN_REQUIRED=1020 -nostdinc -isystem ${NEXT_ROOT}/
usr/include/gcc/darwin/3.3 -isystem ${NEXT_ROOT}/usr/include -F$
{NEXT_ROOT}/System/Library/Frameworks"
     export CFLAGS="-fconstant-cfstrings"
     export LDFLAGS="-L${NEXT_ROOT}/usr/lib/gcc/darwin/3.3 -Wl,-
syslibroot,${NEXT_ROOT}"

note well that the build obtained this way will be essentially  
equivalent to what you'd get when building on a 10.2 system, it will  
not use any of the APIs only available on later systems and so will  
not have all features & fixes for those systems that a build on  
Leopard with -mmacosx-version-min=10.2 would have (i.e. I'd not  
recommend using the 10.2.8 SDK build on anything later than 10.2..)

Cheers,

Daniel

--
** Daniel A. Steffen                   **
** <mailto:das@...>  **



-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Tcl-mac mailing list
tcl-mac@...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

[Damon Courtney]

     After some research, here's what I found.  Apple dropped 10.2  
support in Leopard with Xcode 3 and 2.5.  You can get 2.5 and build up  
to 10.3 from Leopard, but in order to build for 10.2, you have to go  
back to Tiger.  You can only install the 10.2 SDK on Tiger and below.

     So, that would seem to be my problem. 0-]  It's annoying that the  
build doesn't barf somehow when you tell it to use a min of 10.2 and  
there is no 10.2.  I still have a Tiger box around here if I really  
want to go and build for 10.2, but I'm starting to think it's too much  
of a pain.

     I know that we're using some of the newer stuff in the later  
builds.  Is 10.4 the best cut off?  Is 10.3 still a decent build?  
Personally, I would prefer 10.4+ only, but I'm trying to offer  
whatever support to the users that I can so long as it doesn't make my  
life suck. 0-]

D


On Jul 7, 2008, at 8:58 AM, Daniel A. Steffen wrote:

> in theory this should be correct (it is exactly what I use to build  
> my distros on Tiger with 10.3 compatibility), do you have details on  
> what is not working?
> there is an open bug about crashes in the macosx notifier on 10.2  
> with tcl built on Tiger or later, maybe that is what is biting you:
>    https://sourceforge.net/tracker/?func=detail&aid=1792183&group_id=10894&atid=110894
> I no longer have access to a 10.2 system so I cannot debug this  
> myself and the reporter never responded to my requests for help with  
> debugging.
> My suspicion was that pthread_once() is not working correctly on  
> 10.2, i.e. SpinLockLockInit() is never called and so any locking in  
> the notifier crashes. If this can be confirmed, I can look into a  
> workaround.
>
> Honestly however, supporting 10.2 is not high on the list of  
> priorities, indeed I am planning to remove support for 10.2 and 10.3  
> from Tcl/Tk HEAD before 8.6.0, we simply have insufficient  
> maintainer resources to maintain compatibility so far back.
>
>> Any help (or even response) is  appreciated.
>
>
> I have the following magic in my notes about building for the 10.2.8  
> SDK, note that you will need gcc-3.3 installed and that you can only  
> build for ppc this way. Also, IIRC the 10.2.8 SDK is no longer  
> supported with Xcode 3, you may need to install Xcode 2.5 if you're  
> on Leopard (in fact I have no idea if this works on Leopard at all,  
> I've only ever used it on Tiger).
>
>    export CC='gcc-3.3'
>    export MACOSX_DEPLOYMENT_TARGET=10.2
>    export NEXT_ROOT="/Developer/SDKs/MacOSX10.2.8.sdk"
>    export CPPFLAGS="-arch ppc -D__CONSTANT_CFSTRINGS__ -
> DMAC_OS_X_VERSION_MIN_REQUIRED=1020 -nostdinc -isystem ${NEXT_ROOT}/
> usr/include/gcc/darwin/3.3 -isystem ${NEXT_ROOT}/usr/include -F$
> {NEXT_ROOT}/System/Library/Frameworks"
>    export CFLAGS="-fconstant-cfstrings"
>    export LDFLAGS="-L${NEXT_ROOT}/usr/lib/gcc/darwin/3.3 -Wl,-
> syslibroot,${NEXT_ROOT}"
>
> note well that the build obtained this way will be essentially  
> equivalent to what you'd get when building on a 10.2 system, it will  
> not use any of the APIs only available on later systems and so will  
> not have all features & fixes for those systems that a build on  
> Leopard with -mmacosx-version-min=10.2 would have (i.e. I'd not  
> recommend using the 10.2.8 SDK build on anything later than 10.2..)
>
> Cheers,
>
> Daniel
>
> --
> ** Daniel A. Steffen                   **
> ** <mailto:das@...>  **
>
>

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Tcl-mac mailing list
tcl-mac@...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

[Daniel A. Steffen]

Hi Damon,

On 07/07/2008, at 18:16, Damon Courtney wrote:

> It's annoying that the build doesn't barf somehow when you tell it  
> to use a min of 10.2 and there is no 10.2.

not exactly, there may be no support for the 10.2.8 SDK on Leopard  
(i.e. you cannot build as if you were on a 10.2 system), but that does  
not mean that a binary built on Leopard does not run on 10.2...  
indeed, the goal of the -mmacosx-version-min support is that it does!
This works by weak-linking the symbols that do not exist on OS  
versions older than the one you are building on (the -mmacosx-version-
min flag indicating the oldest OS version you want to run on), and  
then checking those symbols against NULL at runtime before calling them.

The problem with 10.4+ builds not running on 10.2 is a bug, as  
mentioned I need help debugging it, once fixed, building with -mmacosx-
version-min=10.2 on Leopard should result in a binary that runs on 10.2.

You can test if the problem your users are seeing is indeed due to the  
notifier initialization bug: just disable the configure test for  
OSSpinLockLock support by setting
        export ac_cv_func_OSSpinLockLock=no
before running configure.

>     I know that we're using some of the newer stuff in the later
> builds.  Is 10.4 the best cut off?  Is 10.3 still a decent build?
> Personally, I would prefer 10.4+ only, but I'm trying to offer
> whatever support to the users that I can so long as it doesn't make my
> life suck. 0-]


I'd guess only a small part of the userbase are running systems older  
than 10.4 nowadays, but it all depends on your market (e.g. education  
is likely to have a higher proportion of old systems), certainly  
restricting to 10.4 and up will make your life easier...
FWIW I think AS still supports 10.3.9 with ActiveTcl.

Cheers,

Daniel

--
** Daniel A. Steffen                   **
** <mailto:das@...>  **



-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Tcl-mac mailing list
tcl-mac@...
https://lists.sourceforge.net/lists/listinfo/tcl-mac