On Fri, May 14, 2010 at 6:32 PM, <[email protected]> wrote: > John Porubek writes: >> I'm experiencing problems compiling version 0.7. This is the first new >> revision I've tried since version 0.4. When doing the make I get the >> error messages: >> >> cproc.c:27:31: error: readline/readline.h: No such file or directory >> cproc.c:28:30: error: readline/history.h: No such file or directory >> >> I see that I can invoke make without readline support, but I believe >> that this support gives me enhanced line editing and history, correct? >> I haven't tried much to solve this problem on my own, save for >> checking that I have "readline-common", "libreadline5" and >> "libreadline6" installed on my system. Certainly I'm not the only noob >> who would stumble on this issue, am I? ;^) > > Hi John, > > I'm guessing from the package names that you're using Debian or Ubuntu? > > Those packages you've named just provide files required by compiled > programs at runtime. You also need the header files, which are usually > provided by packages ending in -dev. I'm using Debian Etch and I need > to also install libreadline5-dev. > > This distinction between lib* and lib*-dev applies for all library > packages. You need lib* to run programs using the library, but you > need the extra lib*-dev package if you want to compile programs that > use the library. > > Cheers, > Daniel >
Rob and Daniel, Thanks for pointing me in the right direction. Daniel, you were right, I'm using Ubuntu 9.10. I installed libreadline-dev, that, in turn, installed libreadline6-dev. After that, "make" compiled MSPDebug without a hitch. Thanks also for the added explanation of the distinction between lib* and lib*-dev. That clears up a lot of confusion. I guess it's probably obvious that I don't compile a lot of programs! Now that I've had the chance to play with version 0.7, I can see that I've been missing out on a lot of features since version 0.4 (and now, version 0.8 is out. I can't keep up!). Admittedly, the two commands I use the most are "reset" and "run", but I can see I'll really appreciate some of the new features as I transition away from the debugger in IAR Kickstart. Incidentally, in case this helps others, I found that I could generate an ELF format file from IAR, then use "nm" from a Linux commandline like so: nm filename.elf > filename.nm to create a symbol-table file I can import with the "sym import" command. You can't import the ELF file directly, since apparently it's not a proper ELF32-format file. I'm now using MSPDebug properly as a user and not as root. I'll detail my udev rule information in a follow-up message. --John
