XCode version on Mac OS X.

[Graham Dumpleton <gr...@dscpl.com.au>]

Ron, can you do me a favour and tell me which version of XCode you
are using, the one that came with the box or whether you might have
access to the version of XCode that was released at Mac WWDC in
August or the one released just recently to ADC members.

The easiest way is to look at the build number output from gcc with
the -v option.

graham-dumpletons-powerbook-g4-15:~ grahamd$ gcc -v
Using built-in specs.
Target: powerpc-apple-darwin8
Configured with: /private/var/tmp/gcc/gcc-5341.obj~1/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8
Thread model: posix
gcc version 4.0.1 (Apple Computer, Inc. build 5341)

I have the version of XCode from before WWDC installed. We are still
renewing our ADC membership so haven't got access to more recent
version yet.

I ask, as there was a potential issue with gcc from XCode released at
WWDC not being able to link mod_python. Details of this issue can be
seen at:

  https://issues.apache.org/jira/browse/MODPYTHON-186

I want to see if this was something specific to that one person or there
is actually an issue.

Thanks.

Graham

Ron Reisor wrote ..
> +1 MacOSX 10.4.8 (Intel), Apache 2.0.59 (mpm-prefork), Python 2.5
> 
> cheers,
> 
> Ron
> 
> 
> On Thu, 9 Nov 2006, Jim Gallacher wrote:
> 
> > The mod_python 3.3-0-dev-20061109 tarball is available for testing.
> >
> > We are almost ready for a 3.3.0 release. It's been a while since we've
> had 
> > extensive testing of trunk and I think it would be wise to have a preliminary
> > testing round. Unless there are huge problems we'll do an official beta
> next 
> > week. If it looks *really* good we might even jump right to the release.
> >
> > At this point svn trunk should be considered frozen execpt to fix issues
> that 
> > testing exposes or minor documentation changes.
> >
> > Here are the rules:
> >
> > In order for a file to be officially announced, it has to be tested by
> > developers on the dev list. Anyone subscribed to this list can (and
> > should feel obligated to  :-)  ) test it, and provide feedback *to _this_
> > list*! (Not the mod_python@modpython.org list, and preferably not me
> > personally).
> >
> > The files are (temporarily) available here:
> >
> > http://people.apache.org/~jgallacher/mod_python/dist/
> > http://people.apache.org/~jgallacher/mod_python/dist/mod_python-3.3.0-dev-20061109.tgz
> > http://people.apache.org/~jgallacher/mod_python/dist/mod_python-3.3.0-dev-20061109.tgz.md5
> >
> > Please download it, then do the usual
> >
> > $ ./configure --with-apxs=/wherever/it/is
> > $ make
> > $ (su)
> > # make install
> >
> > Then (as non-root user!)
> >
> > $ make check
> >
> > Or for you Windows folks
> >
> > $ cd test
> > $ python test.py
> >
> > And see if any tests fail. If they pass, send a +1 to the list, if they
> > fail, send the details (the versions of OS, Apache, Apache-mpm, Python,
> > the test output, and suggestions, if any).
> >
> > Please present your test results in the following format:
> > +1 OS version, Apache version (apache mpm), Python Version
> >
> > For example:
> > +1 Linux Debian Sid, Apache 2.0.55 (mpm-worker), Python 2.3.5
> >
> > Presenting your information in a consistent format will help in
> > tabulating the results. You can include additional information in each
> > section, just don't use extra commas. There is no need to include the
> > mod_python version in this string as that information is available in
> > the email subject. Who knows, one day I may actually write a script to
> > extract this information automatically.  :)
> >
> > Thank you for your assistance,
> > Jim Gallacher
> >
> 
> Ron Reisor <ro...@udel.edu> (RWR3)
> University of Delaware Information Technologies/Network and Systems Services
> Computing Center/192 South Chapel Street/Newark DE, 19716
> pgp finger print: 0D 73 06 6F D3 6A 99 D3  F5 D5 6E FF 3B B9 7C 2C

Re: XCode version on Mac OS X.

[Ron Reisor <ro...@udel.edu>]

Hi Graham,

    Apple called it Xcode 2.4.1 and it was released maybe a month ago. I 
didn't try building mod_python-3.3 with Xcode 2.4.

    Here's what gcc says:

[zim:~] ron% gcc -v
Using built-in specs.
Target: i686-apple-darwin8
Configured with: /private/var/tmp/gcc/gcc-5367.obj~1/src/configure 
--disable-checking -enable-werror --prefix=/usr --mandir=/share/man 
--enable-languages=c,objc,c++,obj-c++ 
--program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ 
--with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib 
--build=powerpc-apple-darwin8 --with-arch=nocona --with-tune=generic 
--program-prefix= --host=i686-apple-darwin8 --target=i686-apple-darwin8
Thread model: posix
gcc version 4.0.1 (Apple Computer, Inc. build 5367)
[zim:~] ron%

cheers,

Ron


On Thu, 9 Nov 2006, Graham Dumpleton wrote:

> Ron, can you do me a favour and tell me which version of XCode you
> are using, the one that came with the box or whether you might have
> access to the version of XCode that was released at Mac WWDC in
> August or the one released just recently to ADC members.
>
> The easiest way is to look at the build number output from gcc with
> the -v option.
>
> graham-dumpletons-powerbook-g4-15:~ grahamd$ gcc -v
> Using built-in specs.
> Target: powerpc-apple-darwin8
> Configured with: /private/var/tmp/gcc/gcc-5341.obj~1/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8
> Thread model: posix
> gcc version 4.0.1 (Apple Computer, Inc. build 5341)
>
> I have the version of XCode from before WWDC installed. We are still
> renewing our ADC membership so haven't got access to more recent
> version yet.
>
> I ask, as there was a potential issue with gcc from XCode released at
> WWDC not being able to link mod_python. Details of this issue can be
> seen at:
>
>  https://issues.apache.org/jira/browse/MODPYTHON-186
>
> I want to see if this was something specific to that one person or there
> is actually an issue.
>
> Thanks.
>
> Graham
>
> Ron Reisor wrote ..
>> +1 MacOSX 10.4.8 (Intel), Apache 2.0.59 (mpm-prefork), Python 2.5
>>
>> cheers,
>>
>> Ron
>>
>>
>> On Thu, 9 Nov 2006, Jim Gallacher wrote:
>>
>>> The mod_python 3.3-0-dev-20061109 tarball is available for testing.
>>>
>>> We are almost ready for a 3.3.0 release. It's been a while since we've
>> had
>>> extensive testing of trunk and I think it would be wise to have a preliminary
>>> testing round. Unless there are huge problems we'll do an official beta
>> next
>>> week. If it looks *really* good we might even jump right to the release.
>>>
>>> At this point svn trunk should be considered frozen execpt to fix issues
>> that
>>> testing exposes or minor documentation changes.
>>>
>>> Here are the rules:
>>>
>>> In order for a file to be officially announced, it has to be tested by
>>> developers on the dev list. Anyone subscribed to this list can (and
>>> should feel obligated to  :-)  ) test it, and provide feedback *to _this_
>>> list*! (Not the mod_python@modpython.org list, and preferably not me
>>> personally).
>>>
>>> The files are (temporarily) available here:
>>>
>>> http://people.apache.org/~jgallacher/mod_python/dist/
>>> http://people.apache.org/~jgallacher/mod_python/dist/mod_python-3.3.0-dev-20061109.tgz
>>> http://people.apache.org/~jgallacher/mod_python/dist/mod_python-3.3.0-dev-20061109.tgz.md5
>>>
>>> Please download it, then do the usual
>>>
>>> $ ./configure --with-apxs=/wherever/it/is
>>> $ make
>>> $ (su)
>>> # make install
>>>
>>> Then (as non-root user!)
>>>
>>> $ make check
>>>
>>> Or for you Windows folks
>>>
>>> $ cd test
>>> $ python test.py
>>>
>>> And see if any tests fail. If they pass, send a +1 to the list, if they
>>> fail, send the details (the versions of OS, Apache, Apache-mpm, Python,
>>> the test output, and suggestions, if any).
>>>
>>> Please present your test results in the following format:
>>> +1 OS version, Apache version (apache mpm), Python Version
>>>
>>> For example:
>>> +1 Linux Debian Sid, Apache 2.0.55 (mpm-worker), Python 2.3.5
>>>
>>> Presenting your information in a consistent format will help in
>>> tabulating the results. You can include additional information in each
>>> section, just don't use extra commas. There is no need to include the
>>> mod_python version in this string as that information is available in
>>> the email subject. Who knows, one day I may actually write a script to
>>> extract this information automatically.  :)
>>>
>>> Thank you for your assistance,
>>> Jim Gallacher
>>>
>>
>> Ron Reisor <ro...@udel.edu> (RWR3)
>> University of Delaware Information Technologies/Network and Systems Services
>> Computing Center/192 South Chapel Street/Newark DE, 19716
>> pgp finger print: 0D 73 06 6F D3 6A 99 D3  F5 D5 6E FF 3B B9 7C 2C
>

Ron Reisor <ro...@udel.edu> (RWR3)
University of Delaware Information Technologies/Network and Systems Services
Computing Center/192 South Chapel Street/Newark DE, 19716
pgp finger print: 0D 73 06 6F D3 6A 99 D3  F5 D5 6E FF 3B B9 7C 2C