On Sep 29, 2009, at 9:42 PM, monipol wrote:
On 29/09/2009, at 22:06, Ben Abbott wrote:
On Sep 29, 2009, at 8:56 PM, monipol wrote:
On 29/09/2009, at 08:56, Ben Abbott wrote:
On Sep 29, 2009, at 7:50 AM, monipol wrote:
On 29/09/2009, at 08:37, Ben Abbott wrote:
I'm running Mac OS 10.6
$
Ben Abbott wrote:
should be available in one hour at the latest.
It worked. For reference, a fink index -f was needed after the
selfupdate.
Ben
Do you have NoAutoIndex: true set in your fink.conf?
--
On 29 Sep 2009, at 23:21, Stefan Bruda wrote:
In any event, here is how the thing fails to build:
gcc -fno-strict-aliasing -mno-fused-madd -DNDEBUG -g -fwrapv -O3 -
Wall -Wstrict-prototypes -Ibuild/codegen/ -Ilibffi-src/include -I/
sw64/include/python2.5 -c libffi-src/src/types.c -o
On 30 Sep 2009, at 00:32, Gary K Olson wrote:
and I am sorry if I ruffled your feathers
Don't worry _ I've thick feathers, and a thick skin ! :)
JF
PS : My comment was with a smile _ I was happy to have
fixed my error before any error report _ but also I
knew I had beaten your msg only by
On Sep 30, 2009, at 7:43 AM, Alexander Hansen wrote:
Ben Abbott wrote:
should be available in one hour at the latest.
It worked. For reference, a fink index -f was needed after the
selfupdate.
Ben
Do you have NoAutoIndex: true set in your fink.conf?
Yes I do. If it is supposed to be
Ben Abbott wrote:
On Sep 30, 2009, at 7:43 AM, Alexander Hansen wrote:
Ben Abbott wrote:
should be available in one hour at the latest.
It worked. For reference, a fink index -f was needed after the
selfupdate.
Ben
Do you have NoAutoIndex: true set in your fink.conf?
Yes I do. If
Hello,
I am (and probably will be for some time) still on 10.5.8.
However, due to Snow Leopard, there's a lot of talk here about
64bit versions for 10.5.8 too.
Why would I want to have 64bit versions in 10.5.8? What are the
advantages, restrictions etc.?
Any pointers to some trustworthy docs
Hi,
At 01:42 +0200 on 2009-9-30 Jean-François Mertens wrote:
On 29 Sep 2009, at 23:21, Stefan Bruda wrote:
In any event, here is how the thing fails to build:
gcc -fno-strict-aliasing -mno-fused-madd -DNDEBUG -g -fwrapv -O3 -
Wall -Wstrict-prototypes -Ibuild/codegen/
Hi,
Sorry, I hit send prematurely, but I did not want to say much more
except that we apparently have the same build process and I am willing
to bet that your pyobjc does not work either.
In any event, thank you for your assistance.
Cheers,
Stefan
--
If it was so, it might be; and if it were
