View Single Post
Old 11-23-2015, 12:23 PM   #4
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 910
Karma: 3000002
Join Date: Jun 2010
Device: K3W, PW4
If you would not mind a suggestion, at least one other package I have built from source on my linux system included a "cvslvlck" script in its util directory that when run reports any required libraries that are either missing or too old to build the package with. Perhaps a similar script could be added here to allow the user to confirm they are ready to attempt a build without the need of making sense of the error messages issued during a failed build attempt.

Dave
dhdurgee is online now   Reply With Quote