Ok, I've got things back on track now. PSPP compiled and created and executable this time around. Two things I did: 1. I used fink to update all packages on the system. Only 4 were updated, but one was the m4 package, which is used in building pspp. 2. After updating the m4 packages, I did a complete, from scratch, fresh install from the CVS tree.
The compile went just fine. My suspicion is that something went wrong with the merge of new files from the CVS repository with the older files I had in my original pspp directory when I did the CVS update. Its possible having the newer m4 update may have helped, but I have feeling that it was the CVS update that went awry somehow. I'll play around some more with this version later and see how it goes. Marshall -----Original Message----- From: John Darrington [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 9:37 PM To: Ben Pfaff Cc: Marshall DeBerry; [email protected] Subject: Re: Latest CVS compile on Mac OS X On Mon, Feb 28, 2005 at 12:39:55PM -0800, Ben Pfaff wrote: "Marshall DeBerry" <[EMAIL PROTECTED]> writes: > Just got around to getting the latest CVS and going through the compile on > my Mac--which is now running OS X 10.3.8. I'm now getting the following set > of error messages regarding a "en_GB.po" module: Hmm. That's bizarre. At least here, the second line of en_GB.po (where the error is reported) is a comment. I thought that "en_GB.po:10:2" means the second column of the tenth line. But it is indeed strange. Perhaps en_GB.po and/or pspp.pot has become corrupt somehow. Maybe the msgmerge that comes with OS X is doing something nasty. Try having a look at en_GB.po both before and after you try building. Maybe it'll give an idea of what's going wrong. -- PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://wwwkeys.pgp.net or any PGP keyserver for public key. _______________________________________________ pspp-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/pspp-dev
