gtksql-users Mailing List for GtkSQL
Brought to you by:
djluff
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(10) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2004 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Darryl L. <da...@sn...> - 2006-06-06 12:58:46
|
Alan Briolat wrote: > I had tried 'gtksql' first i think, and had the same problem. > > Just checked out the 'gtksql' module now, and there seems to be an error in the > 'configure' (i am guessing, because ./configure generates Makefile, yes?). > Causes the following error when trying to 'make': > > make[2]: *** No rule to make target `all-@USE_INCLUDED_LIBINTL@', needed by > `all'. Stop. make[2]: Leaving directory `/home/alan/tmp/gtksql/gtksql/intl' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/alan/tmp/gtksql/gtksql' > make: *** [all] Error 2 > > Any ideas? > > I'm getting that now too. Strange, I haven't seen it before. It does look like a 'configure' problem. I'll have a look tonight and see what's happening. Thanks, Darryl. |
From: Alan B. <al...@do...> - 2006-06-01 23:51:06
|
I had tried 'gtksql' first i think, and had the same problem. Just checked out the 'gtksql' module now, and there seems to be an error in the 'configure' (i am guessing, because ./configure generates Makefile, yes?). Causes the following error when trying to 'make': make[2]: *** No rule to make target `all-@USE_INCLUDED_LIBINTL@', needed by `all'. Stop. make[2]: Leaving directory `/home/alan/tmp/gtksql/gtksql/intl' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/alan/tmp/gtksql/gtksql' make: *** [all] Error 2 Any ideas? On Fri, 02 Jun 2006 02:34:38 +1000, Darryl Luff <da...@sn...> wrote: > Alan Briolat wrote: > > Hi, come across your app today when looking for an SQLite GTK frontend, > > did a CVS checkout. When I tried to build, got the following error: > > > > forms.c:204: error: conflicting types for 'fld_get_type' > > forms.h:85: error: previous declaration of 'fld_get_type' was here > > > > Had a quick look at the source - In forms.c fld_get_type is defined as const > > FieldType, in forms.c just FieldType. I changed line 204 in forms.c to > > match the declaration in forms.h and it builds fine now. > > > > Just thought I would let you know ^_^ > > > > > Thanks Alan. You might want to try checking out 'gtksql' rather than > 'experimental'. The experimental one tends to be a bit incomplete, as I > only use it to try things that I'm not sure about! But it still should > compile. I'll check and make sure this is fixed in both. > > Darryl. > > -- Alan Briolat <al...@do...> "Anyone who is capable of getting themselves made President should on no account be allowed to do the job." --Douglas Adams |
From: Darryl L. <da...@sn...> - 2006-06-01 16:38:43
|
Alan Briolat wrote: > Hi, come across your app today when looking for an SQLite GTK frontend, > did a CVS checkout. When I tried to build, got the following error: > > forms.c:204: error: conflicting types for 'fld_get_type' > forms.h:85: error: previous declaration of 'fld_get_type' was here > > Had a quick look at the source - In forms.c fld_get_type is defined as const > FieldType, in forms.c just FieldType. I changed line 204 in forms.c to match > the declaration in forms.h and it builds fine now. > > Just thought I would let you know ^_^ > > Thanks Alan. You might want to try checking out 'gtksql' rather than 'experimental'. The experimental one tends to be a bit incomplete, as I only use it to try things that I'm not sure about! But it still should compile. I'll check and make sure this is fixed in both. Darryl. |
From: Alan B. <al...@do...> - 2006-05-29 19:20:02
|
Hi, come across your app today when looking for an SQLite GTK frontend, did a CVS checkout. When I tried to build, got the following error: forms.c:204: error: conflicting types for 'fld_get_type' forms.h:85: error: previous declaration of 'fld_get_type' was here Had a quick look at the source - In forms.c fld_get_type is defined as const FieldType, in forms.c just FieldType. I changed line 204 in forms.c to match the declaration in forms.h and it builds fine now. Just thought I would let you know ^_^ -- Alan Briolat <al...@do...> "Anyone who is capable of getting themselves made President should on no account be allowed to do the job." --Douglas Adams |
From: <ma...@lo...> - 2004-03-23 19:26:07
|
In 03/23/2004 11:42 AM, Darryl Luff wrote: >>> The "gtksql" module is not much different than the one you have, but=20 >>> from memory I have fixed the keyword completion=20 >> >> nice feature ;-))) >=20 >=20 > I was using the new version at work today and the keyword completion wa= s=20 > playing up. It works fine at home. I'll have to have another look at it= . Functionality such as intellisense or completion like in shells is a very required feature when users have to write in a lot. I'm looking forward some news about that ;-))) >>> and added colour syntax >>> highlighting in the query window, and probably fixed a few bugs. >> >> Yeah, that was one of my ideas I wanted to suggest or may be develop >> it myself. Great job.=20 >=20 > The colours aren't configurable at the moment and look pretty ugly. I=20 > picked them so I could tell them apart while fiddling with it. I need t= o=20 > add a config dialog for these things. I see. It will be great. I have to more dig into your code then I will be able to implement something and help you in the development. I'm not a very reach of time ;-))) but I like coding ;-))) >>> The current table view would be >>> removed, so the query pane would be the same width as the result wind= ow.=20 >> >> Yes, it may be good for writting long SQL statements. >=20 >=20 > I decided to leave the current view in, and add the tree view, and make= =20 > them selectable from the View menu, so you can use either (or both) at=20 > least until we can figure out the best way to do it. I should have this= =20 > version ready to check in probably tomorrow night, although it may not=20 > be fully working. OK, there is no problem with that. I may promise I'll test it whenever this functionality is included. Greets --=20 Mateusz =A3oskot, mateusz at loskot dot net GNU/Linux (Slackware 9.1) http://counter.li.org #220771 |
From: Darryl L. <da...@sn...> - 2004-03-23 10:42:55
|
Mateusz Łoskot schrieb: > In 03/22/2004 07:13 PM, Darryl Luff wrote: > >> Hi Mateusz. Glad you find it useful. > > > I'm glad to have such useful tool. > >> First off, the 'gtksql2' module in CVS is very badly named. It would >> be better called "gtksql-tmp". It is a temporary module I use >> occasionally when making big changes. > > > [...] > > Apologies for this inconvenience. > >> I should remove or rename the gtksql2 module. > > > Oh, I understand it now. > OK, so I'm updating my sandbox with the CVS repo and I'll > compile it again. > >> The "gtksql" module is not much different than the one you have, but >> from memory I have fixed the keyword completion > > > nice feature ;-))) I was using the new version at work today and the keyword completion was playing up. It works fine at home. I'll have to have another look at it. > > > and added colour syntax > >> highlighting in the query window, and probably fixed a few bugs. > > > Yeah, that was one of my ideas I wanted to suggest or may be develop > it myself. Great job. The colours aren't configurable at the moment and look pretty ugly. I picked them so I could tell them apart while fiddling with it. I need to add a config dialog for these things. ... > > The current table view would be > >> removed, so the query pane would be the same width as the result window. > > > Yes, it may be good for writting long SQL statements. I decided to leave the current view in, and add the tree view, and make them selectable from the View menu, so you can use either (or both) at least until we can figure out the best way to do it. I should have this version ready to check in probably tomorrow night, although it may not be fully working. ... > OK, I understand. > Hm, it may be some limitation. I usually work with large databases ;-)) > As I said, I have some ideas ;-))) and > I try to implement it if I can. > If I will not manage to implement it, I'll send you some description > and may be Glade project file(s). All help gratefully accepted! Thanks, Darryl. |
From: <ma...@lo...> - 2004-03-22 20:44:07
|
In 03/22/2004 07:13 PM, Darryl Luff wrote: > Hi Mateusz. Glad you find it useful. I'm glad to have such useful tool. > First off, the 'gtksql2' module in CVS is very badly named. It would be= =20 > better called "gtksql-tmp". It is a temporary module I use occasionally= =20 > when making big changes.=20 > [...] > Apologies for this inconvenience. > I should remove or rename the gtksql2 module. Oh, I understand it now. OK, so I'm updating my sandbox with the CVS repo and I'll compile it again. > The "gtksql" module is not much different than the one you have, but=20 > from memory I have fixed the keyword completion=20 nice feature ;-))) > and added colour syntax > highlighting in the query window, and probably fixed a few bugs. Yeah, that was one of my ideas I wanted to suggest or may be develop it myself. Great job. I'm not a GTK guru, but I'm still learning GTK and I'm going to contribute some interesting projects and GtkSql too. > I see your point with many tables. I did try a tree view down the left=20 > hand side once. It displayed the database name at the top level, the=20 > tables at the second level, and the fields at the third level. Somethin= g=20 > like: > [...] > Do you think this would be useable ? Yes, may be it is one of usable solution. I'll check it. As I understand it is available currently on the CVS ? May be I will make some improvements if I find some. > The current table view would be > removed, so the query pane would be the same width as the result window= .=20 Yes, it may be good for writting long SQL statements. > With 100 tables it may still be awkward, but at least if you collapsed=20 > all the tables it would only take up 100 lines. This is the best way I=20 > can think of? > If you think it would be OK I'll try it and see how it goes. OK, I understand. Hm, it may be some limitation. I usually work with large databases ;-)) As I said, I have some ideas ;-))) and I try to implement it if I can. If I will not manage to implement it, I'll send you some description and may be Glade project file(s). Regards --=20 Mateusz =A3oskot, mateusz at loskot dot net GNU/Linux (Slackware 9.1) http://counter.li.org #220771 |
From: Darryl L. <dj...@us...> - 2004-03-22 15:18:11
|
Hi Mateusz. Glad you find it useful. First off, the 'gtksql2' module in CVS is very badly named. It would be better called "gtksql-tmp". It is a temporary module I use occasionally when making big changes. I last used it for the conversion to GTK2. I have now moved the GTK2 code back to the main "gtksql" module, so this is the one with the most current code. Apologies for this inconvenience. I should remove or rename the gtksql2 module. The "gtksql" module is not much different than the one you have, but from memory I have fixed the keyword completion and added colour syntax highlighting in the query window, and probably fixed a few bugs. I see your point with many tables. I did try a tree view down the left hand side once. It displayed the database name at the top level, the tables at the second level, and the fields at the third level. Something like: databasename -table1 --field1 --field2 -table2 --field1 --field2 Do you think this would be useable? The current table view would be removed, so the query pane would be the same width as the result window. With 100 tables it may still be awkward, but at least if you collapsed all the tables it would only take up 100 lines. This is the best way I can think of? If you think it would be OK I'll try it and see how it goes. Thanks for your suggestions, Darryl. Mateusz Łoskot wrote: > Hi, > > I'm a new user of GtkSql and I've just compiled last CVS version of > gtksql2. It's the tool I'm looking for, especially for SQLite > database querying. > > I have only one (for now) comment or question: > Why you decided to list dtabase tables as tabs ? > > In my opinion it is not user-friendly and user has to > make a lot of actions (click on tabs) working > with many-tables-databases. > > I have some databases with about 100 tables and in that case > it is almost not possible to work with such a huge amount of tabs ;-))) > > So, don't you thing that tabs should be > replaced with other UI widget i.e. combo or list ? > > Generaly thanks for such a nice tool. > > Regards > |
From: <ma...@lo...> - 2004-03-20 22:31:51
|
Hi, I'm a new user of GtkSql and I've just compiled last CVS version of gtksql2. It's the tool I'm looking for, especially for SQLite database querying. I have only one (for now) comment or question: Why you decided to list dtabase tables as tabs ? In my opinion it is not user-friendly and user has to make a lot of actions (click on tabs) working with many-tables-databases. I have some databases with about 100 tables and in that case it is almost not possible to work with such a huge amount of tabs ;-))) So, don't you thing that tabs should be replaced with other UI widget i.e. combo or list ? Generaly thanks for such a nice tool. Regards --=20 Mateusz =A3oskot, mateusz at loskot dot net GNU/Linux (Slackware 9.1) http://counter.li.org #220771 |
From: Darryl L. <dj...@us...> - 2003-09-06 15:12:44
|
The next development version of gtksql has been released. I believe that this version is fairly stable. If no problems are found with it, it will become version 0.4. There is not much that has changed externally, except for some menu changes. The main visible change is the addition of scripting support. This is fairly basic at the moment. It lets you run a script to connect to a database and setup queries. You can also save a workspace (ie. the database connection and the open queries) to a script file and restore the workspace by running the script. The script engine used is LUA (www.lua.org). This is a very powerful scripting engine. As GtkSQL's script support is beefed up in the next version, I think the scripting will be a very useful addition. If you are building GtkSQL from source, you will need to download the LUA package. For convenience I have included source and RPM's for LUA on the site. NOTE: You do NOT need the LUA package to run GtkSQL, you only need it if you are going to be rebuilding GtkSQL from source. Source code and RPMS are available on the Sourceforge site at https://sourceforge.net/project/showfiles.php?group_id=533. Please let me know if there are any problems. Immediate Future Plans: - New stable version 0.4 will be released as soon as any problems with 0.3.3 are fixed. - GtkSQL will be converted to GTK2. - Scripting support will be improved to allow input and query forms. Thanks for trying GtkSQL. If you have any suggestions or bug reports, please mail them or enter them on the Sourceforge site at https://sourceforge.net/projects/gtksql/. Darryl Luff dj...@us... |
From: Miernik <mi...@ct...> - 2003-08-12 10:26:00
|
On Tue, Aug 12, 2003 at 07:51:58PM +1000, Darryl Luff wrote: > Thats odd. I downloaded the current postgresql source and it's the same > as mine above (except for my typo putting '""''s instead of '<>'s). > Anyway. I've updated the CVS version of configure.in to add both > /usr/include/postgresql/server and /usr/include/postgresql to the search > path. I think that should do it. To get the 0.3.2 version working, you > could try replacing the configure.in from the package with the one > attached, and run 'autoconf' then configure. Just done rm -Rf gtksql/ and checked out the latest CVS code with cvs -z3 -d:pserver:ano...@cv...:/cvsroot/gtksql co gtksql Doesn't work: miernik@tarnica:~/debpkg/gtksql$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking for strerror in -lcposix... no checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for gcc option to accept ANSI C... none needed checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking build system type... i586-pc-linux-gnu checking host system type... i586-pc-linux-gnu checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking for a sed that does not truncate output... /bin/sed checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking command to parse /usr/bin/nm -B output... ok checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for ranlib... ranlib checking for strip... strip checking for objdir... .libs checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... GNU/Linux ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether -lc should be explicitly linked in... no creating libtool checking for gtk-config... /usr/bin/gtk-config checking for GTK - version >= 1.2.0... yes checking for inflate in -lz... yes checking for mysql_store_result in -lmysqlclient... no checking for PQfinish in -lpq... yes checking for lua_open in -llua... no checking postgres.h usability... no checking postgres.h presence... no checking for postgres.h... no checking whether to include MySQL support... no checking whether to include PostgreSQL support... no checking whether to include Lua support... no checking whether to include XPath support... no checking whether to include experimental features... no configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating config.h config.status: executing depfiles commands miernik@tarnica:~/debpkg/gtksql$ config.log attached. -- Miernik ________________________ jabberid:mi...@hi... __ ICQ: 4004001 ___/__ tel: +48608233394 __/ mailto:mi...@ct... Sing a declaration against US invasion in Iraq: http://www.moveon.org/declaration/ |
From: Darryl L. <da...@sn...> - 2003-08-12 09:54:02
|
Miernik wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >On Mon, Aug 11, 2003 at 08:46:37PM +1000, Darryl Luff wrote: > > >>This seems to be a change in the postgresql headers. If you look at your >>postgres.h, does it have the same as mine above? Or does it have: >> >>#include "server/c.h" >>#include "server/utils/elog.h" >>#include "server/utils/palloc.h" >> >> > >Its: > >#include <server/c.h> >#include <server/utils/elog.h> >#include <server/utils/palloc.h> > > Thats odd. I downloaded the current postgresql source and it's the same as mine above (except for my typo putting '""''s instead of '<>'s). Anyway. I've updated the CVS version of configure.in to add both /usr/include/postgresql/server and /usr/include/postgresql to the search path. I think that should do it. To get the 0.3.2 version working, you could try replacing the configure.in from the package with the one attached, and run 'autoconf' then configure. Darryl. |
From: Miernik <mi...@ct...> - 2003-08-11 11:27:19
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Aug 11, 2003 at 08:46:37PM +1000, Darryl Luff wrote: > Ah, that's the problem I think. The configure script adds the > /usr/include/postgresql/server directory to the include search dir. On > my redhat (postgresql 7.3.2), and debian (postgresql 7.2.1) systems, at > the top of postgres.h it has these lines: > > #include "c.h" > #include "utils/elog.h" > #include "utils/palloc.h" > > So when it looks for c.h it finds it at > /usr/include/postgresql/server/c.h. But in your dump above, it's looking > for server/c.h. So it needs /usr/include/postgresql added to the search > path rather than /usr/include/postgresql/server. > > This seems to be a change in the postgresql headers. If you look at your > postgres.h, does it have the same as mine above? Or does it have: > > #include "server/c.h" > #include "server/utils/elog.h" > #include "server/utils/palloc.h" Its: #include <server/c.h> #include <server/utils/elog.h> #include <server/utils/palloc.h> > If it's different I'll have to update the configure script so it works > either way. regards, - -- Miernik ________________________ jabberid:mi...@hi... __ ICQ: 4004001 ___/__ tel: +48608233394 __/ mailto:mi...@ct... Sing a declaration against US invasion in Iraq: http://www.moveon.org/declaration/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/N30+ef2MJBeMWJ0RAsOCAJ4wt+wO1E0IcUllD5IISRpnq/RdOQCffTEN NZ2FhwsEuu5UKkLi3FN5f/M= =RRNr -----END PGP SIGNATURE----- |
From: Darryl L. <da...@sn...> - 2003-08-11 11:12:32
|
Miernik wrote: >So you have a 'stable' system. I tried it on an 'unstable' system. >I have a mixed 'stable'/'testing' system, and just now I have checked, >and (I tried the current CVS version): > > ... >I did a little test, and upgraded postgresql-dev on the 'stable' >system to 7.3.2r1-5 from 'testing'. And now it also does: > >checking /usr/include/postgresql/server/postgres.h usability... no >checking /usr/include/postgresql/server/postgres.h presence... no >checking for /usr/include/postgresql/server/postgres.h... no > > >And from config.log : > > >configure:9393: checking /usr/include/postgresql/server/postgres.h usability >configure:9402: gcc -c -g -O2 conftest.c >&5 >In file included from configure:9430: >/usr/include/postgresql/server/postgres.h:48: server/c.h: No such file or directory >/usr/include/postgresql/server/postgres.h:49: server/utils/elog.h: No such file or directory >/usr/include/postgresql/server/postgres.h:50: server/utils/palloc.h: No such file or directory >configure:9405: $? = 1 > Ah, that's the problem I think. The configure script adds the /usr/include/postgresql/server directory to the include search dir. On my redhat (postgresql 7.3.2), and debian (postgresql 7.2.1) systems, at the top of postgres.h it has these lines: #include "c.h" #include "utils/elog.h" #include "utils/palloc.h" So when it looks for c.h it finds it at /usr/include/postgresql/server/c.h. But in your dump above, it's looking for server/c.h. So it needs /usr/include/postgresql added to the search path rather than /usr/include/postgresql/server. This seems to be a change in the postgresql headers. If you look at your postgres.h, does it have the same as mine above? Or does it have: #include "server/c.h" #include "server/utils/elog.h" #include "server/utils/palloc.h" If it's different I'll have to update the configure script so it works either way. Darryl |
From: Miernik <mi...@ct...> - 2003-08-10 12:17:27
|
On Sun, Aug 10, 2003 at 08:38:22PM +1000, Darryl Luff wrote: > Hi again Jan. I have finally got a Debian system up and running. It's > debian 3.0. The 0.3.2 version of gtksql configured and built OK for me. > The postgresql header is found in /usr/include/postgresql/server/postgres.h. So you have a 'stable' system. I tried it on an 'unstable' system. I have a mixed 'stable'/'testing' system, and just now I have checked, and (I tried the current CVS version): checking /usr/include/postgresql/server/postgres.h usability... yes checking /usr/include/postgresql/server/postgres.h presence... yes checking for /usr/include/postgresql/server/postgres.h... yes But on three different computers, each with an unstable system, it says no to these checks. Here are the version ov revelant packages in these systems (unstable is the one on which it doesn't work): unstable stable postgresql-dev 7.3.3-1 7.2.1-2woody2 automake <none> 1:1.4-p4-1.1 automake1.7 1.7.6-1 <none> autoconf 2.57-6 2.53-2 autoconf2.13 <none> 2.13-47 I did a little test, and upgraded postgresql-dev on the 'stable' system to 7.3.2r1-5 from 'testing'. And now it also does: checking /usr/include/postgresql/server/postgres.h usability... no checking /usr/include/postgresql/server/postgres.h presence... no checking for /usr/include/postgresql/server/postgres.h... no And from config.log : configure:9393: checking /usr/include/postgresql/server/postgres.h usability configure:9402: gcc -c -g -O2 conftest.c >&5 In file included from configure:9430: /usr/include/postgresql/server/postgres.h:48: server/c.h: No such file or directory /usr/include/postgresql/server/postgres.h:49: server/utils/elog.h: No such file or directory /usr/include/postgresql/server/postgres.h:50: server/utils/palloc.h: No such file or directory configure:9405: $? = 1 configure: failed program was: #line 9395 "configure" #include "confdefs.h" #include <stdio.h> #if HAVE_SYS_TYPES_H # include <sys/types.h> #endif #if HAVE_SYS_STAT_H # include <sys/stat.h> #endif #if STDC_HEADERS # include <stdlib.h> # include <stddef.h> #else # if HAVE_STDLIB_H # include <stdlib.h> # endif #endif #if HAVE_STRING_H # if !STDC_HEADERS && HAVE_MEMORY_H # include <memory.h> # endif # include <string.h> #endif #if HAVE_STRINGS_H # include <strings.h> #endif #if HAVE_INTTYPES_H # include <inttypes.h> #else # if HAVE_STDINT_H # include <stdint.h> # endif #endif #if HAVE_UNISTD_H # include <unistd.h> #endif #include </usr/include/postgresql/server/postgres.h> configure:9420: result: no configure:9424: checking /usr/include/postgresql/server/postgres.h presence configure:9431: gcc -E conftest.c In file included from configure:9427: /usr/include/postgresql/server/postgres.h:48: server/c.h: No such file or directory /usr/include/postgresql/server/postgres.h:49: server/utils/elog.h: No such file or directory /usr/include/postgresql/server/postgres.h:50: server/utils/palloc.h: No such file or directory configure:9437: $? = 1 configure: failed program was: #line 9426 "configure" #include "confdefs.h" #include </usr/include/postgresql/server/postgres.h> configure:9455: result: no configure:9473: checking for /usr/include/postgresql/server/postgres.h configure:9480: result: no > The CVS version had a couple of problems with the older version of gcc. > I've fixed them so it now also builds OK. There are a couple of small > problems (like it doesn't find the bitmap for the 'About' box). These > should be fixed this week. BTW, you had a problem with a new version of gcc (3.3), and I've fixed it in my Debian patch, look at: http://www.miernik.ctnet.pl/debian/pool/gtksql_0.3.2-1.diff.gz In the file d_postgres.c See changelog in that patch: * Fix to compile with gcc-3.3: The preprocessor no longer accepts multi-line string literals: http://gcc.gnu.org/gcc-3.3/changes.html > Is it possible that the postgresql-dev package has a problem on your > system? The autoconf scripts do a test compile using the header, they > don't just check that it's there. Have you been able to compile other > postgresql related programs? > > If you look in the config.log file after it fails it should show you > what it tried to run, and what failed. Yeah, the offending part is: | #include </usr/include/postgresql/server/postgres.h> configure:9872: result: no configure:9876: checking /usr/include/postgresql/server/postgres.h presence configure:9887: gcc -E conftest.c In file included from configure:9900: /usr/include/postgresql/server/postgres.h:48:29: server/c.h: No such file or directory /usr/include/postgresql/server/postgres.h:49:38: server/utils/elog.h: No such file or directory /usr/include/postgresql/server/postgres.h:50:40: server/utils/palloc.h: No such file or directory configure:9893: $? = 1 configure: failed program was: | #line 9878 "configure" | /* confdefs.h. */ | I thought that running ./configure --includedir=/usr/include/postgresql/ would help, but it didn't. I'm attaching the full config.log files from my unstable system, when trying to configure both the 0.3.2 version, and CVS. > >My package is here: > >http://www.miernik.ctnet.pl/debian/pool/gtksql_0.3.2-1_i386.deb > > This fails some dependencies on my system, which is to be expected I guess. It was made for an unstable system, and you have a stable (woody) system. I'll try to make backports for woody and sarge systems later. regards, -- Miernik ________________________ jabber:mi...@ja... __ ICQ: 4004001 ___/__ tel: +48608233394 __/ mailto:mi...@ct... Do not use Paypal. They sometimes shut down accounts and steal users money! http://www.paypalwarning.com/ |
From: Darryl L. <da...@sn...> - 2003-08-10 10:40:07
|
Jan 'Miernik' Macek wrote: >I have a problem with compiling your package. > >I am using Debian sid, and I have the postgresql-dev package >installed. I have the /usr/include/postgresql/server/postgres.h file >on my system: > >szczeliniec:/usr/include/postgresql/server# l /usr/include/postgresql/server/postgres.h >- -rw-r--r-- 1 root root 14259 2003-06-02 00:45 /usr/include/postgresql/server/postgres.h > > >But ./configure says that it's not there: > >checking /usr/include/mysql/mysql.h usability... yes >checking /usr/include/mysql/mysql.h presence... yes >checking for /usr/include/mysql/mysql.h... yes >checking /usr/include/pgsql/server/postgres.h usability... no >checking /usr/include/pgsql/server/postgres.h presence... no >checking for /usr/include/pgsql/server/postgres.h... no >checking /usr/include/postgresql/server/postgres.h usability... no >checking /usr/include/postgresql/server/postgres.h presence... no >checking for /usr/include/postgresql/server/postgres.h... no >checking whether to include MySQL support... yes >checking whether to include PostgreSQL support... no > >What to do? > > Hi again Jan. I have finally got a Debian system up and running. It's debian 3.0. The 0.3.2 version of gtksql configured and built OK for me. The postgresql header is found in /usr/include/postgresql/server/postgres.h. The CVS version had a couple of problems with the older version of gcc. I've fixed them so it now also builds OK. There are a couple of small problems (like it doesn't find the bitmap for the 'About' box). These should be fixed this week. Is it possible that the postgresql-dev package has a problem on your system? The autoconf scripts do a test compile using the header, they don't just check that it's there. Have you been able to compile other postgresql related programs? If you look in the config.log file after it fails it should show you what it tried to run, and what failed. >My package is here: >http://www.miernik.ctnet.pl/debian/pool/gtksql_0.3.2-1_i386.deb > > This fails some dependencies on my system, which is to be expected I guess. Thanks again, Darryl. |
From: Darryl L. <da...@sn...> - 2003-08-03 12:58:49
|
This should be fixed in CVS now. If you could test that for me on Debian would be great. I'm just building in some scripting support. If this fault seems to be fixed, I'll put out another release as soon as the scripting is finished. There have been a lot of fixes since the 0.3 release, so I'm not surprised that it has problems. This next release should become the new 'stable' version all being well. Thanks, Darryl. Miernik wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >I downloaded >http://cesnet.dl.sourceforge.net/sourceforge/gtksql/gtksql-0.3.2-3.i386.rpm, >converted it to deb with alien, and installed it in a Debian/sid >system. > >I did Database->Connect, filled in all the fields for my PostgreSQL >database, and gtksql segfaulted: > >(gdb) bt >#0 0x4018abdb in g_strdup () from /usr/lib/libglib-1.2.so.0 >#1 0x0805543f in add_field_def () >#2 0x080555cd in DBget_table_def () >#3 0x08053f5c in TablesNewConnection () >#4 0x0804f362 in open_ok_callback () >#5 0x400aa3f3 in gtk_marshal_NONE__NONE () from /usr/lib/libgtk-1.2.so.0 >#6 0x400d9a9e in gtk_signal_remove_emission_hook () from /usr/lib/libgtk-1.2.so.0 >#7 0x400d8f1c in gtk_signal_set_funcs () from /usr/lib/libgtk-1.2.so.0 >#8 0x400d6ea8 in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0 >#9 0x40049e00 in gtk_button_clicked () from /usr/lib/libgtk-1.2.so.0 >#10 0x4004b36f in gtk_button_get_relief () from /usr/lib/libgtk-1.2.so.0 >#11 0x400aa3f3 in gtk_marshal_NONE__NONE () from /usr/lib/libgtk-1.2.so.0 >#12 0x400d8cce in gtk_signal_set_funcs () from /usr/lib/libgtk-1.2.so.0 >#13 0x400d6ea8 in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0 >#14 0x40049d44 in gtk_button_released () from /usr/lib/libgtk-1.2.so.0 >#15 0x4004ad0e in gtk_button_get_relief () from /usr/lib/libgtk-1.2.so.0 >#16 0x400aa1c9 in gtk_marshal_BOOL__POINTER () from /usr/lib/libgtk-1.2.so.0 >#17 0x400d8d77 in gtk_signal_set_funcs () from /usr/lib/libgtk-1.2.so.0 >#18 0x400d6ea8 in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0 >#19 0x4010ca5a in gtk_widget_event () from /usr/lib/libgtk-1.2.so.0 >#20 0x400aa05c in gtk_propagate_event () from /usr/lib/libgtk-1.2.so.0 >#21 0x400a917d in gtk_main_do_event () from /usr/lib/libgtk-1.2.so.0 >#22 0x40152e20 in gdk_wm_protocols_filter () from /usr/lib/libgdk-1.2.so.0 > > >BTW the Debian package in official Debian (0.3 version) also segfaults >when trying to connect to a PostgreSQL database. Always. > > > |
From: Darryl L. <da...@sn...> - 2003-08-03 02:52:40
|
Hi Jan, Jan 'Miernik' Macek wrote: >I have a problem with compiling your package. > >I am using Debian sid, and I have the postgresql-dev package >installed. I have the /usr/include/postgresql/server/postgres.h file >on my system: > > >szczeliniec:/usr/include/postgresql/server# l /usr/include/postgresql/server/postgres.h >- -rw-r--r-- 1 root root 14259 2003-06-02 00:45 /usr/include/postgresql/server/postgres.h > > >But ./configure says that it's not there: > I haven't tried a Debian build for a while. It used to work but they seem to have removed the mysql/psql devel packages from the sourceforge compile farm. And my home debian machine is temporarily dead. >BTW: What is gtksql2 in CVS? Is is a GTK2 version? I'd be very glad to >see that. > It's just a non-working GUI mockup. I was playing around with an interface built with glade. I should remove it. I will have to look at changing over to Gtk2. I was leaving it until most systems included it by default, which I think they all do now. >BTW2: I have successfully (excetp that PostreSQL support is not >included) updated the debian/ to the latest Debian Standards version >and generated a deb package. That's my first Debian package :) >gtksql is currently unmaintained in Debian, because the manitaner >stopped responding or doing anything. We should do something about it >(you become the mainatiner? I becaome the maintainer? we place an >unofficial updated Debian package on http://www.apt-get.org?) > > I had tried to contact the old maintainer to see if the debian directory in the package was still up to date, but with no luck. If you'd like to do it, that's fine. As soon as I can get my home machine working, I'll look into the configure problem. autoconf has changed a bit lately, I suspect the autoconf scripts need updating a bit. Darryl dj...@us... >My package is here: >http://www.miernik.ctnet.pl/debian/pool/gtksql_0.3.2-1_i386.deb > >regards, > >- -- > Miernik ________________________ jabber:mi...@ja... >__ ICQ: 4004001 ___/__ tel: +48608233394 __/ mailto:mi...@ct... >Do not use Paypal. They sometimes shut down accounts and steal users money! >http://www.paypalsucks.com/ > > |
From: Miernik <mi...@ct...> - 2003-08-02 21:43:13
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I downloaded http://cesnet.dl.sourceforge.net/sourceforge/gtksql/gtksql-0.3.2-3.i386.rpm, converted it to deb with alien, and installed it in a Debian/sid system. I did Database->Connect, filled in all the fields for my PostgreSQL database, and gtksql segfaulted: (gdb) bt #0 0x4018abdb in g_strdup () from /usr/lib/libglib-1.2.so.0 #1 0x0805543f in add_field_def () #2 0x080555cd in DBget_table_def () #3 0x08053f5c in TablesNewConnection () #4 0x0804f362 in open_ok_callback () #5 0x400aa3f3 in gtk_marshal_NONE__NONE () from /usr/lib/libgtk-1.2.so.0 #6 0x400d9a9e in gtk_signal_remove_emission_hook () from /usr/lib/libgtk-1.2.so.0 #7 0x400d8f1c in gtk_signal_set_funcs () from /usr/lib/libgtk-1.2.so.0 #8 0x400d6ea8 in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0 #9 0x40049e00 in gtk_button_clicked () from /usr/lib/libgtk-1.2.so.0 #10 0x4004b36f in gtk_button_get_relief () from /usr/lib/libgtk-1.2.so.0 #11 0x400aa3f3 in gtk_marshal_NONE__NONE () from /usr/lib/libgtk-1.2.so.0 #12 0x400d8cce in gtk_signal_set_funcs () from /usr/lib/libgtk-1.2.so.0 #13 0x400d6ea8 in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0 #14 0x40049d44 in gtk_button_released () from /usr/lib/libgtk-1.2.so.0 #15 0x4004ad0e in gtk_button_get_relief () from /usr/lib/libgtk-1.2.so.0 #16 0x400aa1c9 in gtk_marshal_BOOL__POINTER () from /usr/lib/libgtk-1.2.so.0 #17 0x400d8d77 in gtk_signal_set_funcs () from /usr/lib/libgtk-1.2.so.0 #18 0x400d6ea8 in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0 #19 0x4010ca5a in gtk_widget_event () from /usr/lib/libgtk-1.2.so.0 #20 0x400aa05c in gtk_propagate_event () from /usr/lib/libgtk-1.2.so.0 #21 0x400a917d in gtk_main_do_event () from /usr/lib/libgtk-1.2.so.0 #22 0x40152e20 in gdk_wm_protocols_filter () from /usr/lib/libgdk-1.2.so.0 BTW the Debian package in official Debian (0.3 version) also segfaults when trying to connect to a PostgreSQL database. Always. - -- Miernik ________________________ jabber:mi...@ja... __ ICQ: 4004001 ___/__ tel: +48608233394 __/ mailto:mi...@ct... Independent database of civilian deaths in Iraq in US military actions: http://www.iraqbodycount.net/bodycount.htm -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/LDADef2MJBeMWJ0RAoa3AKCLYQ3M/WB44njc9bkmgWEb8ZkVMQCdEY2m pIQdcCAyogPfcw1ChTv/WZ4= =PBnE -----END PGP SIGNATURE----- |
From: Jan 'M. M. <mi...@ct...> - 2003-08-02 17:27:03
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have a problem with compiling your package. I am using Debian sid, and I have the postgresql-dev package installed. I have the /usr/include/postgresql/server/postgres.h file on my system: szczeliniec:/usr/include/postgresql/server# l /usr/include/postgresql/server/postgres.h - -rw-r--r-- 1 root root 14259 2003-06-02 00:45 /usr/include/postgresql/server/postgres.h But ./configure says that it's not there: checking /usr/include/mysql/mysql.h usability... yes checking /usr/include/mysql/mysql.h presence... yes checking for /usr/include/mysql/mysql.h... yes checking /usr/include/pgsql/server/postgres.h usability... no checking /usr/include/pgsql/server/postgres.h presence... no checking for /usr/include/pgsql/server/postgres.h... no checking /usr/include/postgresql/server/postgres.h usability... no checking /usr/include/postgresql/server/postgres.h presence... no checking for /usr/include/postgresql/server/postgres.h... no checking whether to include MySQL support... yes checking whether to include PostgreSQL support... no What to do? I also tried by copying the whole /usr/include/postgresql/ directory to /usr/include/pgsql/server/ to see if configure would recognize it - it didn't, it also said /usr/include/pgsql/server/postgres.h presence... no I tried both with the 0.3.2 version, and the current CVS version - same effect. BTW: What is gtksql2 in CVS? Is is a GTK2 version? I'd be very glad to see that. BTW2: I have successfully (excetp that PostreSQL support is not included) updated the debian/ to the latest Debian Standards version and generated a deb package. That's my first Debian package :) gtksql is currently unmaintained in Debian, because the manitaner stopped responding or doing anything. We should do something about it (you become the mainatiner? I becaome the maintainer? we place an unofficial updated Debian package on http://www.apt-get.org?) My package is here: http://www.miernik.ctnet.pl/debian/pool/gtksql_0.3.2-1_i386.deb regards, - -- Miernik ________________________ jabber:mi...@ja... __ ICQ: 4004001 ___/__ tel: +48608233394 __/ mailto:mi...@ct... Do not use Paypal. They sometimes shut down accounts and steal users money! http://www.paypalsucks.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/K/Qhef2MJBeMWJ0RAuPoAJ4lTM/KNtcT5cefsYUEfejyMFHhFwCfXJMj VhZebrcceRB05/jelJO3qPs= =nPpn -----END PGP SIGNATURE----- |
From: Darryl L. <da...@sn...> - 2002-10-18 14:44:42
|
Hi all, I have created another couple of mailing lists for GtkSQL: gtk...@li... will have just release announcements, gtk...@li... will show CVS commits. This is not very useful unless you're a developer, or waiting for a specific feature to be committed. Both of these can be subscribed to from the mailing list page at https://sourceforge.net/mail/?group_id=533. Is anyone having any problems with the current version of GtkSQL? The list is so quiet it must be performing perfectly :). If not, please let me know either through the mailing list or using the support links on https://sourceforge.net/projects/gtksql/. Thanks, Darryl Luff dj...@us... |