Anybody else having problems compiling DBD-SQLite-1.03?
 
On Fri, 2004-08-20 at 11:22, Scott T. Hildreth wrote:
> Hello Matt, 
>  
>    I've been trying to compile DBD-SQLite-1.03 and I get the error,
> 
> dbdimp.c:24:4: warning: #warning "No vararg macros - using trace without
> line numbers"
> dbdimp.c: In function `sqlite_st_execute':
> dbdimp.c:323: parse error before `*'
> dbdimp.c:327: `sql_type' undeclared (first use in this function)
> dbdimp.c:327: (Each undeclared identifier is reported only once
> dbdimp.c:327: for each function it appears in.)
> 
> lared (first use in this function)
> make: *** [dbdimp.o] Error 1
> 
> ..should this be declared in dbdimp.h ?   Is this a gcc version 
> issue?  My gcc's are 2.95.4 & 2.96.
> 
> ...okay just got another error with gcc 3.3.1 on a suse box,
> 
> dbdimp.c:231: error: conflicting types for `sqlite_db_last_insert_id'
> /usr/local/lib/perl5/site_perl/5.8.3/i686-linux/auto/DBI/dbd_xsh.h:36:
> error: previous declaration of `sqlite_db_last_insert_id'
> make: *** [dbdimp.o] Error 1
> 
> 
>                      Thanks,
>                          STH
> 
> 
> On Sat, 2004-07-17 at 04:51, Matt Sergeant wrote:
> > Hi guys,
> > 
> > Anyone who has read my journal will know that I now have DBD::SQLite 
> > ported to SQLite 3.0, which provides better datatypes, better 
> > concurrency, proper blob support, etc.
> > 
> > Now the big problem is that sqlite 3.0 is incompatible with sqlite 2.x 
> > (which the current CPAN version of DBD::SQLite is based on), and if you 
> > try and open an old database it will fail horribly. So we have an 
> > upgrade problem.
> > 
> > Potential solutions:
> > 
> >   - Rename it DBD::SQLite3. I don't like this solution because the API 
> > remains the same, and so anyone who wants to upgrade will have to 
> > change their code. This is specially relevant for CPAN modules which 
> > use DBD::SQLite.
> > 
> >   - Provide some sort of porting tool. Not sure the best way to do this 
> > - the sqlite docs recommend just doing a dump from the old format and 
> > an import into the new, but that will require both versions installed.
> > 
> >   - Ignore the problem - it might be painful for the few people who use 
> > DBD::SQLite, but it's a one-time pain.
> > 
> >   - Provide lots of warnings if Makefile.PL detects an old version 
> > installed. This is my favoured solution, not least because it means 
> > minimal work for me (if you suggest an alternate solution do bear this 
> > in mind - I do this stuff for free).
> > 
> > What are your thoughts?
> > 
> > Make sure you CC me in all replies as I don't subscribe, but keep posts 
> > on-list so they are archived.
> > 
> > Matt.

Reply via email to