Fred, I gave this another shot over the weekend. I could not get sqlite to compile with readline support no matter which combination of configure options I provided. I will get this working at some point, but it may require updating readline or applying a whole series of patches to readline. It looked like the readline.h file that is used with Astlinux right now has some incompatibilities with sqlite3.
So the way sqlite3 is built right now, it does not have readline support. Darrick Fred wrote: > Hello > > At 23:31 07/02/2008 -0600, Darrick Hartman (lists) wrote: >> I really don't know why you're bothering with rpm stuff. What's installed >> on your host OS has little to do with what's inside Astlinux. STAGING_DIR >> is a directory inside the build_i586 directory in your build >> environment. Several things are put there that are not needed in the >> final build (such as header files etc). > > Sorry, I didn't know "make" would only look for libraries in this > directory, hence my installing RPMs needlesslesly :-/ > > As for some applications like nano or SQLite sometimes not supporting "dead > keys" like the cursor keys, CTRL-C, Home/End when working over SSH from > Windows, here's what I was told: > > "The Linux kernel does not support command history for tty input. Many > shells and other applications that read commands interactively thus > implement that on their own, reading characters from the kernel instead of > complete lines, and recognizing control sequences based on termcap or > terminfo. Some of those programs delegate the task to a library such a > readline or editline. > > The sqlite3 program apparently can be linked with the readline library. > Does your sqlite3 binary recognize the UP and DEL keys if you run it on the > Linux console, rather than via SSH? If not, perhaps readline support was > just disabled when sqlite3 was built. In that case, you could either > rebuild it, or install rlwrap and run sqlite3 via that." > > If sqlite3 recognizes the keys at the console but not via SSH, the problem > is probably in your TERM environment variable. Run the infocmp program to > check whether the appropriate terminal definition has been installed and > whether it contains the correct strings. I see though that you have already > tried different values for TERM." > > Here's the result of my experiments: http://pastebin.ca/909815 > > Does someone know more about this "readline" library that apparently > applications use to convert non-visible keys from remote SSH clients, and > would know what to do to rebuild SQLite so it supports them? It seems like > Linux users have no problem when connecting to AstLinux through SSH, but > I'm working from a Windows client, and apparently, this lack of support for > dead keys is a common issue. > > Thank you. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Astlinux-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to [EMAIL > PROTECTED] -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com Small Business IT Specialists Office: 920.547.4535 Cell: 920.901.3113 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
