amrecover issue when I run ./configure that I believe causeing another issue down the line
Hi I installed Using Yast2 readline and readline-devel # locate readline as below /usr/include/guile-readline /usr/include/guile-readline/readline.h /usr/include/readline /usr/include/readline/chardefs.h /usr/include/readline/history.h /usr/include/readline/keymaps.h /usr/include/readline/readline.h /usr/include/readline/rlconf.h /usr/include/readline/rlstdc.h /usr/include/readline/rltypedefs.h /usr/include/readline/tilde.h But when I run ./configure I still get a warning about amrecover configure: WARNING: *** No terminal library, no history and command line editing in amrecover! configure: WARNING: *** vtblc headers not found - no QIC volume table support! Any ideas Cheers Chuck
Re: amrecover issue when I run ./configure that I believe causeing another issue down the line
Chuck Amadi Systems Administrator wrote: But when I run ./configure I still get a warning about amrecover Because configure still uses the old settings. Get rid of them by make distclean And then followed by a new ./config --with-user=... ... -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amrecover issue when I run ./configure that I believe causeing another issue down the line
Hi Paul I have done make distclean every time I re run ./configure I am going to pursue using the rpm's as I assume I want have an issue with readline and readline-devel. Cheers On Wed, 2005-05-18 at 11:05 +0200, Paul Bijnens wrote: Chuck Amadi Systems Administrator wrote: But when I run ./configure I still get a warning about amrecover Because configure still uses the old settings. Get rid of them by make distclean And then followed by a new ./config --with-user=... ...
Re: amrecover issue when I run ./configure that I believe causeing another issue down the line
Chuck Amadi Systems Administrator wrote: I have done make distclean every time I re run ./configure I am going to pursue using the rpm's as I assume I want have an issue with readline and readline-devel. Fine with me. But is there a file /usr/lib/libreadline.so.* installed? If yes, in the file config.status (the result of ./configure) is there a line saying: s,@READLINE_LIBS@,-lreadline,;t t (a sed command used to change the needed files) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amrecover issue when I run ./configure that I believe causeing another issue down the line
Chuck Amadi Systems Administrator wrote: configure: WARNING: *** No terminal library, no history and command line editing in amrecover! A look into config.log is normally most appropriate in a case like this. It gives you a precise indication of what it checked for, and why it failed. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
