RE: [sqlite] Sqlite 3.4.0 - problem with prompt
OK, got it solved. Just changed the generated Makefile manually, and bypassed the configure script. Thanks for the help. Nir. -Original Message- From: Rachmel, Nir (Nir) [mailto:[EMAIL PROTECTED] Sent: Sunday, August 19, 2007 11:01 AM To: sqlite-users@sqlite.org Subject: RE: [sqlite] Sqlite 3.4.0 - problem with prompt Yes, I do. That's how it worked for sqlite 3.2.8. I am cross compiling from i686 to a ppc based system, and I tried pointing the directories where these libs reside via the configure: --with-readline-lib="..." --with-readline-inc="..." But to no avail. I get an error message from the Makefile: /home/rachmel/build/target/root/usr/local/include: file not recognized: Is a directory Thanks, Nir. -Original Message- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Friday, August 17, 2007 12:46 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Sqlite 3.4.0 - problem with prompt Do you have readline? Rachmel, Nir (Nir) wrote: > Hi, > > I recently upgraded from sqlite 3.2.8 to sqlite 3.4.0. > I have only made minor changes in my system to get the new version up > and running, however I encountered a problem: > when I run sqlite with a database and try to use the 'history' feature > of the command-line (pressing the 'up' arrow key to browse through the > latest commands executed) the result is some special characters > printed to the screen instead of the expected behaviour. > > I am cross compiling sqlite from an i686 machine to ppc running linux. > > here are my configure options: > > ./configure '--build=i686-linux' \ > --host=$(CONFIGURE_HOST) \ > --prefix=$(PREFIX) \ > '--disable-tcl' \ > '--disable-debug' \ > '--with-gnu-ld' \ > '--enable-threadsafe' \ > '--enable-releasemode' \ > '--enable-static' > > and I also set this environment variable which I suspect is related: > export READLINE_FLAGS='-DHAVE_READLINE=0'; export LIBREADLINE='' > > (however this worked just find with 3.2.8!!) > > I would appreciate your help, > > Thanks, Nir. > - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Sqlite 3.4.0 - problem with prompt
Yes, I do. That's how it worked for sqlite 3.2.8. I am cross compiling from i686 to a ppc based system, and I tried pointing the directories where these libs reside via the configure: --with-readline-lib="..." --with-readline-inc="..." But to no avail. I get an error message from the Makefile: /home/rachmel/build/target/root/usr/local/include: file not recognized: Is a directory Thanks, Nir. -Original Message- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Friday, August 17, 2007 12:46 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Sqlite 3.4.0 - problem with prompt Do you have readline? Rachmel, Nir (Nir) wrote: > Hi, > > I recently upgraded from sqlite 3.2.8 to sqlite 3.4.0. > I have only made minor changes in my system to get the new version up > and running, however I encountered a problem: > when I run sqlite with a database and try to use the 'history' feature > of the command-line (pressing the 'up' arrow key to browse through the > latest commands executed) the result is some special characters > printed to the screen instead of the expected behaviour. > > I am cross compiling sqlite from an i686 machine to ppc running linux. > > here are my configure options: > > ./configure '--build=i686-linux' \ > --host=$(CONFIGURE_HOST) \ > --prefix=$(PREFIX) \ > '--disable-tcl' \ > '--disable-debug' \ > '--with-gnu-ld' \ > '--enable-threadsafe' \ > '--enable-releasemode' \ > '--enable-static' > > and I also set this environment variable which I suspect is related: > export READLINE_FLAGS='-DHAVE_READLINE=0'; export LIBREADLINE='' > > (however this worked just find with 3.2.8!!) > > I would appreciate your help, > > Thanks, Nir. > - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Sqlite 3.4.0 - problem with prompt
Do you have readline? Rachmel, Nir (Nir) wrote: Hi, I recently upgraded from sqlite 3.2.8 to sqlite 3.4.0. I have only made minor changes in my system to get the new version up and running, however I encountered a problem: when I run sqlite with a database and try to use the 'history' feature of the command-line (pressing the 'up' arrow key to browse through the latest commands executed) the result is some special characters printed to the screen instead of the expected behaviour. I am cross compiling sqlite from an i686 machine to ppc running linux. here are my configure options: ./configure '--build=i686-linux' \ --host=$(CONFIGURE_HOST) \ --prefix=$(PREFIX) \ '--disable-tcl' \ '--disable-debug' \ '--with-gnu-ld' \ '--enable-threadsafe' \ '--enable-releasemode' \ '--enable-static' and I also set this environment variable which I suspect is related: export READLINE_FLAGS='-DHAVE_READLINE=0'; export LIBREADLINE='' (however this worked just find with 3.2.8!!) I would appreciate your help, Thanks, Nir. - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Sqlite 3.4.0 - problem with prompt
http://www.google.com/ --- "Rachmel, Nir (Nir)" <[EMAIL PROTECTED]> wrote: > Tried without this line - it still doesn't work. > Any ideas? > > Thanks, Nir. > > -Original Message- > From: Joe Wilson [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 16, 2007 4:16 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Sqlite 3.4.0 - problem with prompt > > You want to enable readline to allow command history editting, not > disable it. > > --- "Rachmel, Nir (Nir)" <[EMAIL PROTECTED]> wrote: > > I recently upgraded from sqlite 3.2.8 to sqlite 3.4.0. > > I have only made minor changes in my system to get the new version up > > and running, however I encountered a problem: > > when I run sqlite with a database and try to use the 'history' feature > > > of the command-line (pressing the 'up' arrow key to browse through the > > > latest commands executed) the result is some special characters > > printed to the screen instead of the expected behaviour. > > > > I am cross compiling sqlite from an i686 machine to ppc running linux. > > > > here are my configure options: > > > > ./configure '--build=i686-linux' \ > > --host=$(CONFIGURE_HOST) \ > > --prefix=$(PREFIX) \ > > '--disable-tcl' \ > > '--disable-debug' \ > > '--with-gnu-ld' \ > > '--enable-threadsafe' \ > > '--enable-releasemode' \ > > '--enable-static' > > > > and I also set this environment variable which I suspect is related: > > export READLINE_FLAGS='-DHAVE_READLINE=0'; export LIBREADLINE='' > > > > (however this worked just find with 3.2.8!!) Got a little couch potato? Check out fun summer activities for kids. http://search.yahoo.com/search?fr=oni_on_mail=summer+activities+for+kids=bz - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Sqlite 3.4.0 - problem with prompt
Tried without this line - it still doesn't work. Any ideas? Thanks, Nir. -Original Message- From: Joe Wilson [mailto:[EMAIL PROTECTED] Sent: Thursday, August 16, 2007 4:16 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Sqlite 3.4.0 - problem with prompt You want to enable readline to allow command history editting, not disable it. --- "Rachmel, Nir (Nir)" <[EMAIL PROTECTED]> wrote: > I recently upgraded from sqlite 3.2.8 to sqlite 3.4.0. > I have only made minor changes in my system to get the new version up > and running, however I encountered a problem: > when I run sqlite with a database and try to use the 'history' feature > of the command-line (pressing the 'up' arrow key to browse through the > latest commands executed) the result is some special characters > printed to the screen instead of the expected behaviour. > > I am cross compiling sqlite from an i686 machine to ppc running linux. > > here are my configure options: > > ./configure '--build=i686-linux' \ > --host=$(CONFIGURE_HOST) \ > --prefix=$(PREFIX) \ > '--disable-tcl' \ > '--disable-debug' \ > '--with-gnu-ld' \ > '--enable-threadsafe' \ > '--enable-releasemode' \ > '--enable-static' > > and I also set this environment variable which I suspect is related: > export READLINE_FLAGS='-DHAVE_READLINE=0'; export LIBREADLINE='' > > (however this worked just find with 3.2.8!!) Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mail=graduation+gifts=bz - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Sqlite 3.4.0 - problem with prompt
You want to enable readline to allow command history editting, not disable it. --- "Rachmel, Nir (Nir)" <[EMAIL PROTECTED]> wrote: > I recently upgraded from sqlite 3.2.8 to sqlite 3.4.0. > I have only made minor changes in my system to get the new version up > and running, however I encountered a problem: > when I run sqlite with a database and try to use the 'history' feature > of the command-line (pressing the 'up' arrow key to browse through the > latest commands executed) the result is some special characters printed > to the screen instead of the expected behaviour. > > I am cross compiling sqlite from an i686 machine to ppc running linux. > > here are my configure options: > > ./configure '--build=i686-linux' \ > --host=$(CONFIGURE_HOST) \ > --prefix=$(PREFIX) \ > '--disable-tcl' \ > '--disable-debug' \ > '--with-gnu-ld' \ > '--enable-threadsafe' \ > '--enable-releasemode' \ > '--enable-static' > > and I also set this environment variable which I suspect is related: > export READLINE_FLAGS='-DHAVE_READLINE=0'; export LIBREADLINE='' > > (however this worked just find with 3.2.8!!) Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mail=graduation+gifts=bz - To unsubscribe, send email to [EMAIL PROTECTED] -
