On Mon, Apr 10, 2006 at 12:45:18AM +0200, Martin Costabel wrote:
David Bacher wrote:
If I hear any demand for this package, I'm happy to try to build and
submit a more recent version -- and I'll find a solution for the
problem discussed above.
I see now that I have it installed on one of
Dear Fink developers,
We agreed some time ago to allow Application bundle packages in Fink,
and we now have a few of them. There is an AppBundles declaration
available in .info files (although I understand from some previous
email traffic that it does not really serve people's needs --
On Apr 10, 2006, at 9:32 AM, Jack Howarth wrote:
What exactly is the preferred method of handling the -mcpu and
-mtune compiler flags for dual use fink info files? For example, I
have a sparky-py.info packaging that currently optimizes for the
G5 with the -mtune flag. I would like to
Dave,
For the sparky-py fink packages, I have a sparky-py.patch which
patches the Makefile to have ...
-CXX= g++
-CXXFLAGS =
+CXX= g++-3.3
+CXXFLAGS = -O3 -ffast-math -mtune=970 -fPIC -fno-common -Wno-long-double
CC = gcc
-CFLAGS =
On Apr 10, 2006, at 11:10 AM, Jack Howarth wrote:
Dave,
For the sparky-py fink packages, I have a sparky-py.patch which
patches the Makefile to have ...
-CXX= g++
-CXXFLAGS =
+CXX= g++-3.3
By the way, g++-3.3 is not available on intel, so unless you can make
David R. Morrison wrote:
[]
By the way, g++-3.3 is not available on intel, so unless you can make
this package work with g++-4, the discussion is moot.
I have kept hearing this, but now that I have access to an iMac/Intel, I
am somewhat confused:
pws37163:~ costabel$ uname -a
Darwin
On Apr 10, 2006, at 16:47, Martin Costabel wrote:
pws37163:~ costabel$ /usr/bin/g++-3.3 -v
gcc-3.3 and g++-3.3 on Mac OS X can generate code for PowerPC, but
not for Intel. The compiler itself is a universal binary, so you
have a compiler which runs as a native application on either
Hi All,
I have added a note in the DescUsage of trac and let
Jeremy know. Installing pysqlite2 to a fink tree with
an existing sqlite database will cause trac to fail
with a message like this:
Available Projects
* tracfoo: Error
(file is encrypted or is not a database)
According to
