RFE configure script report
Can the ./configure script be made to report at the end what modules it found it can build. The ./configure output does have this information but it's not easy to follow. -- damjan | дамјан This is my jabber ID --> damjan@bagra.net.mk -- not my mail address, it's a Jabber ID --^ :)
What about redirecting the output to a file that you can hunt through?For those of us that forget to set our terminals to infinite lines! $./configure 2>&1 | tee ~/configure.log Glen On Mon, May 18, 2009 at 16:30, Damjan <gdamjan@mail.net.mk> wrote:
Can the ./configure script be made to report at the end what modules it found it can build. The ./configure output does have this information but it's not easy to follow.
-- damjan | дамјан This is my jabber ID --> damjan@bagra.net.mk -- not my mail address, it's a Jabber ID --^ :) - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Can the ./configure script be made to report at the end what modules it found it can build. The ./configure output does have this information but it's not easy to follow.
i guess you are asking this after seeing similar feature in other software?
yes, net-snmp, xine-lib and conky are the first that comes to my mind -- damjan | дамјан This is my jabber ID --> damjan@bagra.net.mk -- not my mail address, it's a Jabber ID --^ :)
Damjan wrote:
Can the ./configure script be made to report at the end what modules it found it can build. The ./configure output does have this information but it's not easy to follow.
Sure. Send a patch to configure.in. Or, look at Make.inc after configure is done. It will have a list of 20-30 modules. There is really few good solutions here. If the list of modules is printed all on one line, it will wrap across 4-5 lines, and be unreadable. If it's listed one module per line, it will likely fill the terminal window, and cause the earlier modules to scroll off of the top. I would suggest simple re-directing the output of "configure" to a file, and then grep'ing that for what you need. Alan DeKok.
participants (4)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Damjan -
Glen Millard