-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 10, 2007, at 8:25 AM, Yves de Champlain wrote:
I just installed gnome and tried :
import gtk : OK
import gnome : bus error
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0004
Thread 0 Crashed:
0
Le 07-03-07 à 22:44, Paul Beard a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 6:37 PM, Yves de Champlain wrote:
the conftest stuff is not a file, the code is in configure. If
you look around, in configure or config.log, you should find how
the check for py-g
Le 07-03-08 à 01:22, Paul Beard a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 10:18 PM, Richard Taylor wrote:
The problem here is the "Bus error". It is not a gramps issue. I
believe that
the "Bus error" is caused by a problem with gtk2/pygtk2 not gramps.
Yea
Le 07-03-08 à 01:18, Richard Taylor a écrit :
On Thursday 08 March 2007 02:37, Yves de Champlain wrote:
Le 07-03-07 à 16:52, Paul Beard a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2007, at 12:10 PM, Richard Taylor wrote:
I had exactly the same problem. I eventually cam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 10:18 PM, Richard Taylor wrote:
The problem here is the "Bus error". It is not a gramps issue. I
believe that
the "Bus error" is caused by a problem with gtk2/pygtk2 not gramps.
Yeah, I figured that out. Frustrating that no ot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 6:37 PM, Yves de Champlain wrote:
the conftest stuff is not a file, the code is in configure. If you
look around, in configure or config.log, you should find how the
check for py-gnome is done.
Well, sort of. there's code i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 6:37 PM, Yves de Champlain wrote:
the conftest stuff is not a file, the code is in configure. If you
look around, in configure or config.log, you should find how the
check for py-gnome is done.
yeah, I looked into it: pret
Le 07-03-07 à 16:52, Paul Beard a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2007, at 12:10 PM, Richard Taylor wrote:
I had exactly the same problem. I eventually came to the
conclusion that the
pygtk build on Mac OSX is broken. I don't believe that it is
anything to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2007, at 12:10 PM, Richard Taylor wrote:
I had exactly the same problem. I eventually came to the conclusion
that the
pygtk build on Mac OSX is broken. I don't believe that it is
anything to do
with gramps. I think that it is a combina
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2007, at 12:10 PM, Richard Taylor wrote:
I think that it is a combination of the gcc/gtk/pygtk versions
but I was unable to verify the exact problem.
I guess this is still true for the 2.2.x versions?
- --
Paul Beard
contact info: www.p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2007, at 9:09 AM, Mark Duling wrote:
The current Gramps port is broken. There is a newer version of
Gramps now
but I've been unable to get it working. So until someone solves
whatever
problem there is with building Gramps from sourc
Paul Beard <[ mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]> on Sunday,
March 4, 2007 at 1:18 PM wrote:
I can't install gramps: i was trying to run it before and hitting some
errors so I decided to rebuild python and gramps. Now gramps won't
complete the configure stage.
The current Gramps port is
I can't install gramps: i was trying to run it before and hitting
some errors so I decided to rebuild python and gramps. Now gramps
won't complete the configure stage.
checking for python platform... darwin
checking for python script directory... ${prefix}/lib/python2.4/site-
packages
checki
13 matches
Mail list logo
