On Wednesday 05 April 2006 22:54, Wesley Parish wrote:
> Quoting Christopher Sawtell <[EMAIL PROTECTED]>:
> > On Tuesday 04 April 2006 23:25, Wesley Parish wrote:
> > > This is an error I'm getting with gnusql when I try to compile it.
> >
> > The
> >
> > > lines gcc complains about read:
> > > FILE *STDERR =stderr;
> > > FILE *STDOUT =stdout;
> >
> > You'll need to give us a bit more info than that.
> > gcc --version please?
>
> gcc -v 3.3.1
>
> > File it's failing on, and the actual error message.
>
> gnusql-0.7b6.1/src/other/sql_decl.c
> --sql_decl
> sql_decl.c:45: error: initializer element is not constant
> sql_decl.c:46: error: initializer element is not constant
> gmake[3]: *** [sql_decl.o] Error 1
>
> I've done a google search on "initializer element not constant" and
> found it covers a whole lot of cases, and in a fair number of those it
> is a program maintenance issue, as gcc doesn't tolerate it any longer.
Correct. You might care to fix this one too:
/home/chris/gnusql-0.7b6.1/src/include/gsqltrn.h:188: warning:
type defaults to `int' in declaration of `gsql_trn_1_nproc'
> > > Hairy, I will admit. Does anyone have any idea/s how to go about
> >
> > fixing
> >
> > > this? Or alternatively, sidestepping it?
> >
> > Seeing as this software is no longer maintained I'd like to suggest
> > you use
> > one of the maintained sql engines such as PostgreSQL or whatever. Or
> > is
> >
> > there a particular reason that you have to use GNUSQL?
>
> I've tried to get in touch with all the programmers, but haven't had any
> success - the GNU.org webmaster thanked me for going to the trouble, as
> it saved them the trouble.
I took it from the site that gnusql was a Russian university project which
has been abandoned as soon as the authors' got their qualifications.
> Since it is no longer maintained, I thought I could do pretty much
> whatever I liked with it, consistent with the GPL, without worrying
> about forking issues, or anybody else complaining.
You can do that with any GPL software, it's one of the fundamental
freedoms.
> Besides, it is small
> and thus will fit in better with my ideas of a miniature office suite.
Is this going to be something for Barbie's PC, or are you aiming it at the
One-PC-per-Child thing which MIT's Negoponte is pushing? :-)
It's reported that both of them are going to run a cutdown Linux.
> I'm using sc for the spreadsheet component, so you might see just where
> I'm coming from there. I was also tempted to take the emacs that came
> with 4.2BSD (prob. v15 or thereabouts) - nobody with any sense is going
> to complain about me using the text management functions from an
> obsolete text editor version for a word processor.
There is a Micro-Emacs which might be a somewhat better choice.
http://www.microemacs.de/microemacs.html
Also the OPCPC machine is going to have Squeak Smalltalk built-in so you
might like to learn that. It has hooks into PostgreSQL already iirc.
> In other words, politics and size considerations.
I got the GNUSQL too, and go the same errors as you.
I am now completely out of touch with the details of the C syntax so can't
be a very effective helper.
I'd be very tempted to remove all re-declarations of the standard file
handles and just use the built-in stuff.
Remember that there are several other lightweight SQL engines around.
e.g. http://www.sqlite.org/
That one actually works, and there are Qt hooks for it.
--
CS
