[BitPim-devel] Mac osx 10.4.9 ppc build from svn source, APSW issues

Discussion:

David A. Ritter

2007-04-10 15:28:19 UTC

Hello,
I've followed the archives of this list in hopes of running Bitpim
from svn source. I would like to try adding some new phones, but
haven't been able to get past the APSW Sqlite3 link puzzle.
If someone has APSW with Sqlite3 compiled in for osx 10.4.9 ppc, I'd
like to either get a copy or get new instructions on how to
successfully get it built to avoid "Symbol not found:
_sqlite3_declare_vtab" issues.
Thanks,
Dave

Larry Meadors

2007-04-10 15:43:57 UTC

Permalink

I had similar issues trying to build from source last night - the
version of sqlite on the Mac is 3.0.8, and apsw wants 3.0.10 or
greater, but even after updating, I was getting a message that the
version I had was too old (even if I put sqlite under the apsw
directory this hapens):

===
larry-meadors-computer:~/downloads/python/apsw-3.3.13-r1 lmeadors$
sqlite3 -version
3.3.12
larry-meadors-computer:~/downloads/python/apsw-3.3.13-r1 lmeadors$
python setup.py install
running install
running build
running build_ext
building 'apsw' extension
gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk
-fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd
-fno-common -dynamic -DNDEBUG -g -O3 -DNDEBUG=1 -DEXPERIMENTAL=1
-DSQLITE_OMIT_LOAD_EXTENSION=1
-I/Library/Frameworks/Python.framework/Versions/2.4/include/python2.4
-c apsw.c -o build/temp.macosx-10.3-fat-2.4/apsw.o
apsw.c:60:2: apsw.c:60:2:error: #error Your SQLite version is too old.
It must be at least 3.3.10
error: #error Your SQLite version is too old. It must be at least 3.3.10
===

I noticed that the instructions are saying to use python 2.3, too - is
that the issue, maybe? I think more likely that the header files are
coming from elsewhere, and confusing things, but I'm not sure either.
:-/

I'd really like to get this working, because the current binaries are
not working on my machine, and my phone is not supported, so I'd like
to add support for it if I can.

If anyone needs more info to help, just ask. :-D

Larry

Post by David A. Ritter
Hello,
I've followed the archives of this list in hopes of running Bitpim
from svn source. I would like to try adding some new phones, but
haven't been able to get past the APSW Sqlite3 link puzzle.
If someone has APSW with Sqlite3 compiled in for osx 10.4.9 ppc, I'd
like to either get a copy or get new instructions on how to
_sqlite3_declare_vtab" issues.
Thanks,
Dave
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BitPim-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

T Gallagher

2007-04-10 16:48:14 UTC

Permalink

David,

I had the same errors before and they were resolved when I followed along
with the
procedure shown below. Seems the trick was to add the shared library path.

Tim

Quote =================================================
Ok, I finally got BitPim running on Intel 10.4.9 with Python 2.5 and
wxPython 2.8.1.1.

Here's what I did:

First as Sean suggested, I rebuilt sqlite3. Now part of that is
actually installing it (via sudo make install), not only using it as
part of the shared library when compiling apsw. This will place a
copy of sqlite 3.3.13 into /usr/local/lib.

I also installed apsw by following the directions in its documentation.

Since I am using tcsh as my shell, I use setenv to export my
environment variables like:

setenv DYLD_LIBRARY_PATH /usr/local/lib

For bash it would be:

export DYLD_LIBRARY_PATH=/usr/local/lib

After setting the variable, BitPim would run successfully. However,
that only works as long as the variable is present, so if you kill
your terminal session, you'll have to export it again.

When I ran BitPim months ago with a previous version of apsw, I
thought that sqlite3 was bundled into the .so file once it was
compiled. Am I incorrect in assuming that is the case now? Why would
it have to link against a version at run time now? Maybe the version
of apsw at that time was compatible with the version of sqlite3
installed on Tiger by default so I never saw that error.

These are where I got the versions of Python and wxPython from:

- Python 2.5 from python.org
- wxPython 2.8.11 from http://www.wxpython.org/download.php and used
the wxpython osx-unicode-py2.5 link.

I have yet to try making a build, but that will be the next step. I
also checked my version of apsw.so and it is universal.

Hope this helps anyone out needing to run from source.

END QUOTE ==========================================

Post by David A. Ritter
Hello,
I've followed the archives of this list in hopes of running Bitpim
from svn source. I would like to try adding some new phones, but
haven't been able to get past the APSW Sqlite3 link puzzle.
If someone has APSW with Sqlite3 compiled in for osx 10.4.9 ppc, I'd
like to either get a copy or get new instructions on how to
_sqlite3_declare_vtab" issues.
Thanks,
Dave
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BitPim-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

David A. Ritter

2007-04-10 18:02:42 UTC

Permalink

Tim,
Thanks to you, I finally have Bitpim running from svn source. My
Python is 2.5, wxPython 2.8.3-unicode, sqlite-3.3.15 from a new
source package, and APSW from svn sources version 396.
I followed your instruction for the sqlite3 build, and I also used
the APSW instructions from:
http://initd.org/pub/software/pysqlite/apsw/3.3.13-r1/apsw.html
I followed their guidance for adding a sqlite3 subdir in APSW, I
think that this is supposed to include sqlite3 in APSW. That still
didn't work so I used your "export DYLD_LIBRARY_PATH=/usr/local/lib"
line.
The APSW install with the sqlite3 subdir probably does nothing, like
you said library path seems to be the key here.
Now I can finally look into those new phone files.

Dave

Post by T Gallagher
David,
I had the same errors before and they were resolved when I followed
along with the
procedure shown below. Seems the trick was to add the shared
library path.
Tim
Quote ==============================
===================
Ok, I finally got BitPim running on Intel 10.4.9 with Python 2.5 and
wxPython 2.8.1.1.
First as Sean suggested, I rebuilt sqlite3. Now part of that is
actually installing it (via sudo make install), not only using it as
part of the shared library when compiling apsw. This will place a
copy of sqlite 3.3.13 into /usr/local/lib.
I also installed apsw by following the directions in its
documentation.
Since I am using tcsh as my shell, I use setenv to export my
setenv DYLD_LIBRARY_PATH /usr/local/lib
export DYLD_LIBRARY_PATH=/usr/local
/lib
After setting the variable, BitPim would run successfully. However,
that only works as long as the variable is present, so if you kill
your terminal session, you'll have to export it again.
When I ran BitPim months ago with a previous version of apsw, I
thought that sqlite3 was bundled into the .so file once it was
compiled. Am I incorrect in assuming that is the case now? Why would
it have to link against a version at run time now? Maybe the version
of apsw at that time was compatible with the version of sqlite3
installed on Tiger by default so I never saw that error.
- Python 2.5 from python.org
- wxPython 2.8.11 from http://www.wxpython.org/download.php and used
the wxpython osx-unicode-py2.5 link.
I have yet to try making a build, but that will be the next step. I
also checked my version of apsw.so and it is universal.
Hope this helps anyone out needing to run from source.

Larry Meadors

2007-04-10 19:14:16 UTC

Permalink

That was not my problem. Darn. :(

However, I got it working, and am posting this in case others have the
same problem

This was on my Intel Mac (a shiny new MacBook Pro):

Sean Burke

2007-04-10 19:32:13 UTC

Permalink

Larry,
Check out the documentation for apsw. The "out of the box" 10.4.9
python distribution does not build modules against static libraries when
dynamic ones are available. While building it against the dynamic
library is ok, the result is not portable. If you are interested in
building against the static sqlite library, add "-search_paths_first" to
the LDFLAGS section of your config/Makefile. (Mine is located at:
/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/config/Makefile
).

Best,

Sean

Post by Larry Meadors
That was not my problem. Darn. :(
However, I got it working, and am posting this in case others have the
same problem

a***@bastula.org

2007-04-10 19:03:32 UTC

Permalink

Hi Tim,

I'm curious why I was not given credit for the quote you posted? I don't
really mind, but was there a reason you took out my name? I am happy that
I was able to help out though.

Thanks,

Adit

Post by T Gallagher
David,
I had the same errors before and they were resolved when I followed along
with the procedure shown below. Seems the trick was to add the shared
library path.
Tim
Quote =================================================
Ok, I finally got BitPim running on Intel 10.4.9 with Python 2.5 and
wxPython 2.8.1.1.
First as Sean suggested, I rebuilt sqlite3. Now part of that is
actually installing it (via sudo make install), not only using it as part
of the shared library when compiling apsw. This will place a copy of
sqlite 3.3.13 into /usr/local/lib.
I also installed apsw by following the directions in its documentation.
Since I am using tcsh as my shell, I use setenv to export my
setenv DYLD_LIBRARY_PATH /usr/local/lib
export DYLD_LIBRARY_PATH=/usr/local/lib
After setting the variable, BitPim would run successfully. However,
that only works as long as the variable is present, so if you kill your
terminal session, you'll have to export it again.
When I ran BitPim months ago with a previous version of apsw, I
thought that sqlite3 was bundled into the .so file once it was compiled. Am
I incorrect in assuming that is the case now? Why would
it have to link against a version at run time now? Maybe the version of
apsw at that time was compatible with the version of sqlite3 installed on
Tiger by default so I never saw that error.
- Python 2.5 from python.org
- wxPython 2.8.11 from http://www.wxpython.org/download.php and used
the wxpython osx-unicode-py2.5 link.
I have yet to try making a build, but that will be the next step. I
also checked my version of apsw.so and it is universal.
Hope this helps anyone out needing to run from source.
END QUOTE ==========================================

Post by David A. Ritter
Hello,
I've followed the archives of this list in hopes of running Bitpim
from svn source. I would like to try adding some new phones, but haven't
been able to get past the APSW Sqlite3 link puzzle. If someone has APSW
with Sqlite3 compiled in for osx 10.4.9 ppc, I'd like to either get a
copy or get new instructions on how to successfully get it built to
avoid "Symbol not found: _sqlite3_declare_vtab" issues.
Thanks,
Dave
-----------------------------------------------------------------------
--
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD
EV
_______________________________________________
BitPim-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BitPim-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

T Gallagher

2007-04-10 20:48:16 UTC

Permalink

Adit,

I couldn't find the original mail where you detailed the procedure, but I
had
cut out the section I included into a text file and saved that. Wasn't
expecting it would be for anything other than my reference later.

Tim

Post by a***@bastula.org
Hi Tim,
I'm curious why I was not given credit for the quote you posted? I don't
really mind, but was there a reason you took out my name? I am happy that
I was able to help out though.
Thanks,
Adit

Post by T Gallagher
David,
I had the same errors before and they were resolved when I followed

along

Post by T Gallagher
with the procedure shown below. Seems the trick was to add the shared
library path.
Tim
Quote =================================================
Ok, I finally got BitPim running on Intel 10.4.9 with Python 2.5 and
wxPython 2.8.1.1.
First as Sean suggested, I rebuilt sqlite3. Now part of that is
actually installing it (via sudo make install), not only using it as

part

Post by T Gallagher
of the shared library when compiling apsw. This will place a copy of
sqlite 3.3.13 into /usr/local/lib.
I also installed apsw by following the directions in its documentation.
Since I am using tcsh as my shell, I use setenv to export my
setenv DYLD_LIBRARY_PATH /usr/local/lib
export DYLD_LIBRARY_PATH=/usr/local/lib
After setting the variable, BitPim would run successfully. However,
that only works as long as the variable is present, so if you kill your
terminal session, you'll have to export it again.
When I ran BitPim months ago with a previous version of apsw, I
thought that sqlite3 was bundled into the .so file once it was compiled.

Post by T Gallagher
I incorrect in assuming that is the case now? Why would
it have to link against a version at run time now? Maybe the version of
apsw at that time was compatible with the version of sqlite3 installed

Post by T Gallagher
Tiger by default so I never saw that error.
- Python 2.5 from python.org
- wxPython 2.8.11 from http://www.wxpython.org/download.php and used
the wxpython osx-unicode-py2.5 link.
I have yet to try making a build, but that will be the next step. I
also checked my version of apsw.so and it is universal.
Hope this helps anyone out needing to run from source.
END QUOTE ==========================================

Post by David A. Ritter
Hello,
I've followed the archives of this list in hopes of running Bitpim
from svn source. I would like to try adding some new phones, but

haven't

Post by T Gallagher

Post by David A. Ritter
been able to get past the APSW Sqlite3 link puzzle. If someone has APSW
with Sqlite3 compiled in for osx 10.4.9 ppc, I'd like to either get a
copy or get new instructions on how to successfully get it built to
avoid "Symbol not found: _sqlite3_declare_vtab" issues.
Thanks,
Dave
-----------------------------------------------------------------------
--
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys-and earn

cash

Post by T Gallagher

Post by David A. Ritter
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD
EV
_______________________________________________
BitPim-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

-------------------------------------------------------------------------

Post by T Gallagher
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys-and earn

cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

Post by T Gallagher
_______________________________________________
BitPim-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BitPim-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

a***@bastula.org

2007-04-10 22:31:01 UTC

Permalink

No problem at all. Hope I didn't offend you. I've still been trying to get
a universal build to work, but I am having issues making a universal
libusb. I'm sure we'll get it hammered out soon.

Thanks,

Adit

Post by T Gallagher
Adit,
I couldn't find the original mail where you detailed the procedure, but I
had cut out the section I included into a text file and saved that.
Wasn't
expecting it would be for anything other than my reference later.
Tim

Post by a***@bastula.org
Hi Tim,
I'm curious why I was not given credit for the quote you posted? I
don't really mind, but was there a reason you took out my name? I am
happy that I was able to help out though.
Thanks,
Adit

Post by T Gallagher
David,
I had the same errors before and they were resolved when I followed

along

Post by T Gallagher
with the procedure shown below. Seems the trick was to add the
shared library path.
Tim

Sean Burke

2007-04-11 01:15:28 UTC

Permalink

The documentation is for building APSW against a static sqlite
library. OS X defualts to the dynamic verison of a library if it sees
both. Why? It is a mystery for the ages, but the end result is that
unless you "make install" your sqlite build over the Apple default, it
will link against the old sqlite version. If you are just looking to
get it to work on your machine you can use Tim's suggestion, if you
want it portable then use the documentation.

sean

--
Sean Burke
Imaging Analysis Specialist
Albert Einstein College of Medicine
Yeshiva University
Bronx, NY 10461