Hi Mark. As soon as you said ".spec file"....ahhh...wait a minute. I've been thinking that GPG 2.0 (source level install) would be simular to a RPM install for a specific platform. Binaries should have defaults that are good for that platform! Of course! In this GUI world, who would have defaults for a command line interface?
I used the ./configure with no parms (and most likely got the wrong defaults). Also, I do have the gtk-devel files installed. I already threw away my notes on why I thought I needed it. My documentation now just says I do need it. But I think it was something about the gtk-config file being needed. Anyway, I think the problem is due to wrong defaults. Thanks Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 2/20/2007 5:38 PM >>> Did you at least look at the .spec file for the 1.4.6 version from SUSE? If not, what did you use for parameters to ./configure? (Or even if you did.) Did you happen to have the gtk-devel files installed during the build of gpg 2.0.2? If so, you probably don't want to do that. I note that even openSUSE 10.2 only includes gpg2-1.9.22-20. Heck, even Fedora Core testing is only up to 1.4.6. That may be a warning that all is not well with the 2.0 version yet. If I think of anything else to check, I'll reply again. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
