libdbi-devel — Discussion about development of the core library and DBD interface

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Duncan M. <dwm...@gm...>]

On 8/28/07, Markus Hoenicka <mar...@mh...> wrote:
> Quoting Duncan McQueen <dwm...@gm...>:
>
> > Part of the problem may be I am compiling using GCC 4.2.1 - and
> > excessive warning messages seem to be the norm there.  My dbd.h is
> > from CVS as of two days ago.
> >
>
> In that case it might help to manually cast the int variable to const
> int, like this:
>
> _dbd_internal_error_handler(conn, "could not open database", (const
> int) sqlite3_errcode);
>
> Does your GCC like this better?
>
>

I will check tonight on both of these.

> > I will look on the POSIX_PATH_MATH and try to add it.  I know I have
> > seen other source where it was defined as you mentioned.
> >
> >> ifndef _POSIX_PATH_MAX
> >> #define _POSIX_PATH_MAX 512
> >> endif
> >>
>
> This should of course read:
>
> #ifndef _POSIX_PATH_MAX
> #define _POSIX_PATH_MAX 512
> #endif
>
> regards,
> Markus
>
> --
> Markus Hoenicka
> mar...@ca...
> (Spam-protected email: replace the quadrupeds with "mhoenicka")
> http://www.mhoenicka.de
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> libdbi-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libdbi-devel
>

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Markus H. <mar...@mh...>]

Quoting Duncan McQueen <dwm...@gm...>:

> Part of the problem may be I am compiling using GCC 4.2.1 - and
> excessive warning messages seem to be the norm there.  My dbd.h is
> from CVS as of two days ago.
>

In that case it might help to manually cast the int variable to const  
int, like this:

_dbd_internal_error_handler(conn, "could not open database", (const  
int) sqlite3_errcode);

Does your GCC like this better?

> I will look on the POSIX_PATH_MATH and try to add it.  I know I have
> seen other source where it was defined as you mentioned.
>
>> ifndef _POSIX_PATH_MAX
>> #define _POSIX_PATH_MAX 512
>> endif
>>

This should of course read:

#ifndef _POSIX_PATH_MAX
#define _POSIX_PATH_MAX 512
#endif

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Duncan M. <dwm...@gm...>]

Part of the problem may be I am compiling using GCC 4.2.1 - and
excessive warning messages seem to be the norm there.  My dbd.h is
from CVS as of two days ago.

I will look on the POSIX_PATH_MATH and try to add it.  I know I have
seen other source where it was defined as you mentioned.

On 8/28/07, Markus Hoenicka <mar...@mh...> wrote:
> Quoting Duncan McQueen <dwm...@gm...>:
>
> > Well,  I still get an error when compiling the sqlite3 driver under MinGW:
> >
> > dbd_sqlite3.c: In function '_real_dbd_connect':
> > dbd_sqlite3.c:207: warning: passing argument 3 of
> > '_dbd_internal_error_handler' makes pointer from integer without a
> > cast
>
> I don't know what to make of these warnings. On my system I see the following:
>
> $ grep _dbd_internal_error_handler /usr/local/include/dbi/*
> /usr/local/include/dbi/dbd.h:void
> _dbd_internal_error_handler(dbi_conn_t *conn,
> const char *errmsg, const int errno);
>
> argument 3 is declared as
>
> int sqlite3_errcode;
>
> so I don't see what's wrong here. Do you have an old version of dbd.h
> in your include path somewhere (/usr/include/dbi/)?
>
>
> > dbd_sqlite3.c:331: error: '_POSIX_PATH_MAX' undeclared (first use in
> > this function)
>
> Apparently the MinGW version of limits.h does not define this
> constant. Could you please check whether any other include file does?
> You'd have to include that in addition to limits.h then.
>
> If not, try adding something like this to the top of dbd_sqlite.c:
>
> ifndef _POSIX_PATH_MAX
> #define _POSIX_PATH_MAX 512
> endif
>
> If you get it to work, please send me a diff so I can fix these
> problems in the CVS code.
>
> regards,
> Markus
>
>
>
> --
> Markus Hoenicka
> mar...@ca...
> (Spam-protected email: replace the quadrupeds with "mhoenicka")
> http://www.mhoenicka.de
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> libdbi-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libdbi-devel
>

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Markus H. <mar...@mh...>]

Quoting Duncan McQueen <dwm...@gm...>:

> Well,  I still get an error when compiling the sqlite3 driver under MinGW:
>
> dbd_sqlite3.c: In function '_real_dbd_connect':
> dbd_sqlite3.c:207: warning: passing argument 3 of
> '_dbd_internal_error_handler' makes pointer from integer without a
> cast

I don't know what to make of these warnings. On my system I see the followin=
g:

$ grep _dbd_internal_error_handler /usr/local/include/dbi/*
/usr/local/include/dbi/dbd.h:void =20
_dbd_internal_error_handler(dbi_conn_t *conn,
const char *errmsg, const int errno);

argument 3 is declared as

int sqlite3_errcode;

so I don't see what's wrong here. Do you have an old version of dbd.h =20
in your include path somewhere (/usr/include/dbi/)?

> dbd_sqlite3.c:331: error: '_POSIX_PATH_MAX' undeclared (first use in
> this function)

Apparently the MinGW version of limits.h does not define this =20
constant. Could you please check whether any other include file does? =20
You'd have to include that in addition to limits.h then.

If not, try adding something like this to the top of dbd_sqlite.c:

ifndef _POSIX_PATH_MAX
#define _POSIX_PATH_MAX 512
endif

If you get it to work, please send me a diff so I can fix these =20
problems in the CVS code.

regards,
Markus



--=20
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Duncan M. <dwm...@gm...>]

Well,  I still get an error when compiling the sqlite3 driver under MinGW:

dbd_sqlite3.c: In function '_real_dbd_connect':
dbd_sqlite3.c:207: warning: passing argument 3 of
'_dbd_internal_error_handler' makes pointer from integer without a
cast
dbd_sqlite3.c:211: warning: passing argument 3 of
'_dbd_internal_error_handler' makes pointer from integer without a
cast
dbd_sqlite3.c: In function 'dbd_list_dbs':
dbd_sqlite3.c:331: error: '_POSIX_PATH_MAX' undeclared (first use in
this function)
dbd_sqlite3.c:331: error: (Each undeclared identifier is reported only once
dbd_sqlite3.c:331: error: for each function it appears in.)
dbd_sqlite3.c:411: warning: passing argument 3 of
'_dbd_internal_error_handler' makes pointer from integer without a
cast
make[3]: *** [dbd_sqlite3.lo] Error 1
make[3]: Leaving directory `/home/Test/libdbi-drivers/drivers/sqlite3'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/Test/libdbi-drivers/drivers'
make[1]:

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Markus H. <mar...@mh...>]

Quoting Duncan McQueen <dwm...@gm...>:

> Is there a way to tell libdbi-drivers to use sqlite3.h - I get an
> error on compilation because it can't find it (even though sqlite3.h
> exists).
>

What is the exact ./configure command line you are using? In fact, if  
sqlite3.h is not where it should be, configure should issue an error  
saying it can't find the include file. configure has various options  
to make libraries and headers available to the build system (all of  
these of course translate to appropriate -I and -L gcc arguments). If  
your build system can't find the header, try fiddling with  
--with-sqlite3-incdir first. If that does not help, I'd need more info  
about your system, like directory layout and the exact error messages  
you're getting.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Markus H. <mar...@mh...>]

Quoting Duncan McQueen <dwm...@gm...>:

> On sqlite - I am trying to find a source package that includes
> sqlite.h.  The package I donloaded and compiled only had sqlite3.h
>
> The libdbi driver fails to compile because it can't find sqlite.h
>
>

There are two series of sqlite and hence two different drivers. SQLite  
2.8.x uses sqlite.h (and the command line app sqlite), whereas SQLite  
3.x uses sqlite3.h (and sqlite3). Unless you have specific reasons to  
support legacy apps you should go for sqlite3 and build the sqlite3  
driver only.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Markus H. <mar...@mh...>]

Quoting Duncan McQueen <dwm...@gm...>:

> Are there any good examples showing proper use of catching an error
> from the database driver?  As I mentioned - my MinGW compiled program
> really blows up when the database doesn't exist - I am just looking
> for a basic example as to catching the error.
>

These are probably not "good" examples, but still:

1) look at the libdbi-drivers/tests/test_dbi.c test program which  
handles a couple of errors gracefully

2) this is what my other pet project uses to connect to a database  
(look for connect_to_db()):
http://refdb.svn.sourceforge.net/viewvc/refdb/refdb/trunk/src/refdbda.c?revision=461&view=markup

hth

Markus


-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Markus H. <mar...@mh...>]

Quoting Duncan McQueen <dwm...@gm...>:

> Has OPenJade always been required for a compile?  I get errors related
> to it on my MinGW platform - is there a way to ignore it?
>

A hard dependency on OpenJade is not intended, but this seems to fail  
on some platforms. OpenJade is required to build the documentation  
from the SGML sources. However, the built docs are included in the  
source tarball, so there should be no need to build them again. If  
that fails, pass "--disable-docs" to ./configure. Then make should not  
attempt to build the docs.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Duncan M. <dwm...@gm...>]

On sqlite - I am trying to find a source package that includes
sqlite.h.  The package I donloaded and compiled only had sqlite3.h

The libdbi driver fails to compile because it can't find sqlite.h


On 7/16/07, Markus Hoenicka <mar...@mh...> wrote:
> Hi Duncan,
>
> Duncan McQueen writes:
>  > #ifdef __MINGW32__
>  > #include <winsock.h>
>  > #endif
>  >
>  > However, could a similar change be committed to the code?  This will
>  > allow the MinGW platform to compile this driver.
>  >
>
> I've committed the fix you suggested. It can't do any harm on other
> systems, so if that's all it takes to make the driver work on MinGW
> we're all done.
>
> I wasn't quite sure where to put the above lines though. According to
> your compiler log the file must be included before mysql.h, but does
> winsock.h itself have any dependencies? I've put the conditional in
> front of all includes, hoping that there are no such
> dependencies. Could you please check the version from the CVS
> repository to make sure it works?
>
> BTW I recall you compiled the PostgreSQL driver without a hitch. Is
> there any chance to test the sqlite/sqlite3 drivers as well? I reckon this
> should not be too hard as sqlite/sqlite3 also compile as Win32
> apps. With these drivers being ok we could claim full MinGW support
> for the core drivers.
>
> regards,
> Markus
>
> --
> Markus Hoenicka
> mar...@ca...
> (Spam-protected email: replace the quadrupeds with "mhoenicka")
> http://www.mhoenicka.de
>
>

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Duncan M. <dwm...@gm...>]

Are there any good examples showing proper use of catching an error
from the database driver?  As I mentioned - my MinGW compiled program
really blows up when the database doesn't exist - I am just looking
for a basic example as to catching the error.

Thanks!

On 8/26/07, Duncan McQueen <dwm...@gm...> wrote:
> Has OPenJade always been required for a compile?  I get errors related
> to it on my MinGW platform - is there a way to ignore it?
>
> On 7/13/07, Duncan McQueen <dwm...@gm...> wrote:
> > I was able to successfully compile the MySQL driver under MinGW.
> >
> > All that is needed is an include of winsock.h in the dbd_mysql.c file
> > at the top.
> >
> > I did it like this:
> >
> > #ifdef __MINGW32__
> > #include <winsock.h>
> > #endif
> >
> > However, could a similar change be committed to the code?  This will
> > allow the MinGW platform to compile this driver.
> >
> > Thanks,
> >
> > Duncan McQueen
> >
>

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Duncan M. <dwm...@gm...>]

Has OPenJade always been required for a compile?  I get errors related
to it on my MinGW platform - is there a way to ignore it?

On 7/13/07, Duncan McQueen <dwm...@gm...> wrote:
> I was able to successfully compile the MySQL driver under MinGW.
>
> All that is needed is an include of winsock.h in the dbd_mysql.c file
> at the top.
>
> I did it like this:
>
> #ifdef __MINGW32__
> #include <winsock.h>
> #endif
>
> However, could a similar change be committed to the code?  This will
> allow the MinGW platform to compile this driver.
>
> Thanks,
>
> Duncan McQueen
>

[libdbi-devel] Consequences of binding reserved words list after connection.

[Markus H. <mar...@mh...>]

Hi,

I'm not sure whether I really grasp what you're doing here, but I
don't think this would cause problems. To the best of my knowledge the
list of reserved words is not used internally anyway, it is only there
to be queried by the application using libdbi.

regards,
Markus

jp...@un... writes:
 > Hi,
 > 
 > I'm currently working on a dbi abstraction layer (dbd driver that talks to
 > custom server that talks to another dbd driver that talks to db -- all
 > this for replication :).
 > 
 > Problem is, my dbd driver will not know exactly which words are reserved
 > until after a connection (when the custom server will query the mapped dbd
 > driver for the information). I have already decided that custom functions
 > are out of the question.
 > 
 > I am thinking of editing libdbi to add a helper function to update the
 > reserved words after connect. I would document the need to connect before
 > checking if a word is reserved. Would this cause any problems?
 > 
 > Thanks,
 > Jesse
 > 

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[libdbi-devel] Consequences of binding reserved words list after connection.

[<jp...@un...>]

Hi,

I'm currently working on a dbi abstraction layer (dbd driver that talks to
custom server that talks to another dbd driver that talks to db -- all
this for replication :).

Problem is, my dbd driver will not know exactly which words are reserved
until after a connection (when the custom server will query the mapped dbd
driver for the information). I have already decided that custom functions
are out of the question.

I am thinking of editing libdbi to add a helper function to update the
reserved words after connect. I would document the need to connect before
checking if a word is reserved. Would this cause any problems?

Thanks,
Jesse

Re: [libdbi-devel] Compilation of MySQL driver under MingW

[Duncan M. <dwm...@gm...>]

As mentioned off list, I will test out sqlite.

At the current time, I still haven't gotten the freetds driver to
work.  I have been able to successfully compile the driver by doing
the following:

- Changed call of bzero() function to ZeroMemory
- Uncommented calls of fprintf in dbd_connect() function.

However, as I understand it, FreeTDS will not connect to SQL Server
2005 Express (the version I have).

Anyone have SQL Server 2000 and could test it out?

Thanks,

Duncan

On 7/16/07, Markus Hoenicka <mar...@mh...> wrote:
> Hi Duncan,
>
> Duncan McQueen writes:
>  > #ifdef __MINGW32__
>  > #include <winsock.h>
>  > #endif
>  >
>  > However, could a similar change be committed to the code?  This will
>  > allow the MinGW platform to compile this driver.
>  >
>
> I've committed the fix you suggested. It can't do any harm on other
> systems, so if that's all it takes to make the driver work on MinGW
> we're all done.
>
> I wasn't quite sure where to put the above lines though. According to
> your compiler log the file must be included before mysql.h, but does
> winsock.h itself have any dependencies? I've put the conditional in
> front of all includes, hoping that there are no such
> dependencies. Could you please check the version from the CVS
> repository to make sure it works?
>
> BTW I recall you compiled the PostgreSQL driver without a hitch. Is
> there any chance to test the sqlite/sqlite3 drivers as well? I reckon this
> should not be too hard as sqlite/sqlite3 also compile as Win32
> apps. With these drivers being ok we could claim full MinGW support
> for the core drivers.
>
> regards,
> Markus
>
> --
> Markus Hoenicka
> mar...@ca...
> (Spam-protected email: replace the quadrupeds with "mhoenicka")
> http://www.mhoenicka.de
>
>

[libdbi-devel] Compilation of MySQL driver under MingW

[Markus H. <mar...@mh...>]

Hi Duncan,

Duncan McQueen writes:
 > #ifdef __MINGW32__
 > #include <winsock.h>
 > #endif
 > 
 > However, could a similar change be committed to the code?  This will
 > allow the MinGW platform to compile this driver.
 > 

I've committed the fix you suggested. It can't do any harm on other
systems, so if that's all it takes to make the driver work on MinGW
we're all done.

I wasn't quite sure where to put the above lines though. According to
your compiler log the file must be included before mysql.h, but does
winsock.h itself have any dependencies? I've put the conditional in
front of all includes, hoping that there are no such
dependencies. Could you please check the version from the CVS
repository to make sure it works?

BTW I recall you compiled the PostgreSQL driver without a hitch. Is
there any chance to test the sqlite/sqlite3 drivers as well? I reckon this
should not be too hard as sqlite/sqlite3 also compile as Win32
apps. With these drivers being ok we could claim full MinGW support
for the core drivers.

regards,
Markus
 
-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[libdbi-devel] Compilation of MySQL driver under MingW

[Duncan M. <dwm...@gm...>]

I was able to successfully compile the MySQL driver under MinGW.

All that is needed is an include of winsock.h in the dbd_mysql.c file
at the top.

I did it like this:

#ifdef __MINGW32__
#include <winsock.h>
#endif

However, could a similar change be committed to the code?  This will
allow the MinGW platform to compile this driver.

Thanks,

Duncan McQueen

[libdbi-devel] Debian Packages

[Jack B. <ms...@fr...>]

Has any work been done recently on getting libdbi 0.8 into the official
Debian repositories? What are the current obstacles to getting libdbi
0.8 packages (http://libdbi.sourceforge.net/debian/) into the official
repositories? I notice that the packages in Debian are still 0.7 and
that bug #326748, describing the new upstream version, has been open for
almost two years.

I'm installing the Evergreen ILS for three small student run libraries
here at Simon Fraser University, and tinkering with an Evergreen Debian
Package, so I'm quite interested in getting libdbi 0.8 into Debian.

Much thanks! Jack

Re: [libdbi-devel] OS X build

[Toby T. <to...@sm...>]

On 30-Apr-07, at 5:26 PM, Markus Hoenicka wrote:

> Toby Thain writes:
>> Hi,
>>
>> While poking around in the source tree today I noticed the OS X build
>> notes include the following recipe:
>>
>> LIBTOOLIZE=glibtoolize ./autogen.sh

Just for the record, the LIBTOOLIZE setting is still needed.

>> ./configure CFLAGS="-I/sw/include" LDFLAGS="-L/sw/lib"
>> make CFLAGS="-I/sw/include" LDFLAGS="-L/sw/lib"
>> sudo make install
>>
>> I believe the /sw/* directories are Fink's, ...
>>
>
> I believe this is a leftover from the days of yore when the libdbi
> project contained the MySQL and PostgreSQL drivers. ...

Speaking of PgSQL on OS X, it looks like Fink is still a recommended  
way to install it:
- http://developer.apple.com/internet/opensource/postgres.html

The other option is a package such as Marc Liyanage's:
- http://www.entropy.ch/software/macosx/postgresql/
(he mentions other possibilities on that page)
Or Druware's:
- http://postgresqlformac.com/

>
>> Is it worth changing the README.osx?
>>
>
> Yes. Please go ahead and use your simpler recipe.

Change is committed.

I'm retesting the whole lot under OS X and plan to update the  
README.osx in libdbi-drivers too.

--Toby

>
> thanks,
> Markus
>
> -- 
> Markus Hoenicka
> mar...@ca...
> (Spam-protected email: replace the quadrupeds with "mhoenicka")
> http://www.mhoenicka.de
>

[libdbi-devel] OS X build

[Markus H. <mar...@mh...>]

Toby Thain writes:
 > Hi,
 > 
 > While poking around in the source tree today I noticed the OS X build  
 > notes include the following recipe:
 > 
 > LIBTOOLIZE=glibtoolize ./autogen.sh
 > ./configure CFLAGS="-I/sw/include" LDFLAGS="-L/sw/lib"
 > make CFLAGS="-I/sw/include" LDFLAGS="-L/sw/lib"
 > sudo make install
 > 
 > I believe the /sw/* directories are Fink's, perhaps of use if the  
 > configure script is supposed to find specific preinstalled Fink  
 > packages there (openjade?). However, /sw is not a standard part of OS  
 > X, and the simpler recipe:
 > 

I believe this is a leftover from the days of yore when the libdbi
project contained the MySQL and PostgreSQL drivers. I suppose these
databases are most conveniently installed as Fink packages, and the
configure script had to be advised to find the installed headers and
libraries to build the drivers. Now that the drivers are part of a
separate package, there is no need to modify the environment
variables.

 > Is it worth changing the README.osx?
 > 

Yes. Please go ahead and use your simpler recipe.

thanks,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [libdbi-devel] OS X build

[Peter O'G. <pe...@po...>]

On Apr 30, 2007, at 10:06 AM, Toby Thain wrote:

> Hi,
>
> While poking around in the source tree today I noticed the OS X build
> notes include the following recipe:
>
> LIBTOOLIZE=glibtoolize ./autogen.sh
> ./configure CFLAGS="-I/sw/include" LDFLAGS="-L/sw/lib"
> make CFLAGS="-I/sw/include" LDFLAGS="-L/sw/lib"
> sudo make install
>
> I believe the /sw/* directories are Fink's, perhaps of use if the
> configure script is supposed to find specific preinstalled Fink
> packages there (openjade?). However, /sw is not a standard part of OS
> X, and the simpler recipe:
>
> LIBTOOLIZE=glibtoolize ./autogen.sh
> ./configure --disable-docs
> make
> sudo make install
>
> ...works fine on my (10.4.9 PowerPC) system (there's no openjade,
> hence --disable-docs).
>
> Is it worth changing the README.osx?

Looks like a good change to me.

Peter
--
Peter O'Gorman
http://pogma.com

[libdbi-devel] OS X build

[Toby T. <to...@sm...>]

Hi,

While poking around in the source tree today I noticed the OS X build  
notes include the following recipe:

LIBTOOLIZE=glibtoolize ./autogen.sh
./configure CFLAGS="-I/sw/include" LDFLAGS="-L/sw/lib"
make CFLAGS="-I/sw/include" LDFLAGS="-L/sw/lib"
sudo make install

I believe the /sw/* directories are Fink's, perhaps of use if the  
configure script is supposed to find specific preinstalled Fink  
packages there (openjade?). However, /sw is not a standard part of OS  
X, and the simpler recipe:

LIBTOOLIZE=glibtoolize ./autogen.sh
./configure --disable-docs
make
sudo make install

...works fine on my (10.4.9 PowerPC) system (there's no openjade,  
hence --disable-docs).

Is it worth changing the README.osx?

--Toby

Re: [libdbi-devel] [Libdbi-drivers-devel] licensing inconsistency

[Christian M. S. <chr...@st...>]

Hi,

Atleast for the drivers that I have created (mSQL, Oracle, Firebird/ 
Interbase), the intended license is LGPL as that is
what I need myself in the commercial products I use them for ;)

If they are not LGPL today, they will be changes to LGPL ASAP.


regards,


//Christian







On 8 Mar 2007, at 11:18, Balazs Scheidler wrote:

> On Thu, 2007-03-08 at 11:13 +0100, Kjell Irgens wrote:
>> Markus Hoenicka wrote:
>>> Hi Balasz,
>>>
>>> I'm actually surprised to learn that all drivers except sqlite/ 
>>> sqlite3
>>> are LGPL'ed. I wasn't aware that we distribute software with
>>> inconsistent licensing. I'd like to hear what the other developers
>>> think about this problem. Can we simply change the license of the
>>> sqlite/sqlite3 drivers to LGPL to make the whole thing consistent?
>>>
>> That would be good, I have assumed LGPL as long as I use the  
>> PostgreSQL
>> driver only.  I had not noticed that libdb-drivers was not  
>> documented as
>> LPGL in all files.
>>
>> By the way, thanks for the new release!
>
> Does this mean that the intention is LGPL? That'd clear up things for
> me, of course a release with consistent license notations would be  
> more
> than appreciated :)
>
> -- 
> Bazsi
>
>
> ---------------------------------------------------------------------- 
> ---
> 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
> _______________________________________________
> Libdbi-drivers-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel

Re: [libdbi-devel] [libdbi-users] libdbi-0.8.2, libdbi-drivers 0.8.2: ready for prime time?

[Markus H. <mar...@mh...>]

Mike Rylander <mry...@gm...> was heard to say:


> I'm very happy to report that everything builds and works fine on
> Linux (as far as I've tested).  Specs for the setup:
>

Thanks for the feedback. Did you, by any chance, test whether my
libdbi-driver/configure.in massage solved the build problem with the pgsql
driver that you reported previously (doc was built in spite of the
--disable-docs switch)? This is one of these things that always seem to work ok
on my FreeBSD box but rarely anywhere else.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [libdbi-devel] [libdbi-users] libdbi-0.8.2, libdbi-drivers 0.8.2: ready for prime time?

[Mike R. <mry...@gm...>]

On 2/19/07, Markus Hoenicka <mar...@mh...> wrote:
> Hi all,
>
> as previously announced here I've checked in a couple of minor changes that make
> the CVS versions of both libdbi and libdbi-drivers ready for release. All I need
> to move on is some feedback from platforms that I can't test. I ran a few tests
> on FreeBSD and on Windows XP/Cygwin which showed no regressions. Could anyone
> else please confirm that the current CVS versions work ok on major platforms
> (Linux, OSX, Solaris, other *BSDs)? I'd like to get this release off my desk.

I'm very happy to report that everything builds and works fine on
Linux (as far as I've tested).  Specs for the setup:

Debian Etch w/ custom kernel (2.6.16 SMP)
Postgres 8.1.[14] and 8.2
Evergreen CVS HEAD (our project)

Obviously, this is no surprise since it's basically the code that
we've been using all along.  Let me know if there's any other detail
you'd like.  Everything is working well, thanks all!

-miker

>
> regards,
> Markus
>
> --
> Markus Hoenicka
> mar...@ca...
> (Spam-protected email: replace the quadrupeds with "mhoenicka")
> http://www.mhoenicka.de
>
>
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> libdbi-users mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libdbi-users
>


-- 
Mike Rylander
mry...@gm...
GPLS -- PINES Development
Database Developer
http://open-ils.org