On Apr 19, 2004, at 4:12 am, Jerry Krinock wrote: > I want to compile an open-source project called tclspice (an electronic > circuit simulator). I downloaded the "source" file, opened a Terminal > window in its folder and typed "./configure". Result: Many lines of > text > reporting progress in finding stuff, mostly OK, until: > > Checking for readline: > checking for readline/readline.h... no > configure: error: Couldn't find GNU readline headers. > > After this, I found another open-source project called readline4-4.2a > which > seems to be what the above notification says I'm missing. > > Should I configure, make and make install this readline package first? That is certainly what I'd try. The problem with compiling stuff from source is that there's no handling of dependencies - the packages upon which the source code you're installing depends. Beware, tho', that tclspice seems to use the tk widget set; whilst I know applications using this will compile on OS X, I think it may be a little bit of a chore to do so. My Linux box lists the following packages as dependencies for tclspice: $ emerge -p tclspice These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] x11-misc/ttmkfdir-3.0.9-r1 [ebuild N ] media-libs/fontconfig-2.2.1 [ebuild N ] x11-base/opengl-update-1.5 [ebuild N ] x11-base/xfree-4.3.0-r5 [ebuild N ] dev-lang/tk-8.3.4-r1 [ebuild N ] media-libs/glide-v3-3.10-r3 [ebuild N ] dev-tcltk/tclreadline-2.1.0 [ebuild N ] dev-tcltk/blt-2.4z [ebuild N ] app-sci/tclspice-0.2.15 If a binary package is available for OS X, I would certainly be inclined to use it. Stroller.