Hi Travis, Thanks so much for your response. I do have the latest version of Xcode, I double checked to make sure. What other tools from the Apple developer website would help me here? I want to make sure I know how to proceed correctly. I realize that this will take me a lot of time and work, but I'm willing to put in the work it takes and put forth the effort to make sure that I do this correctly. If I have to learn how to get the source file and compile it myself, I will do it. :-) So, should I go in search of something else from the Apple developer site? Or should I begin figuring out how to compile this myself, if the later option, where can I find a good tutorial or a good resource to learn more about this. While I am not an expert, thankfully, if I can find good quality resources to learn with, this stuff makes sense to me so is easy for me to pick up and learn. Thanks so much for the help! Laurel
On 12/26/14, Travis Siegel <[email protected]> wrote: > What it's telling you is that although you have a makeinfo program, the one > you have isn't new enough. To solve this problem, you'll probably need to > go download the source to makeinfo, and compile your own version (or if > you're suicidal enough) install macports, and use that to try to find it. > Macports works fine for some folks, but it caused me nothing but trouble, so > I don't recommend use of it for any reason. Often times, the macports > version of a program isn't significantly different from a native osx > version, it's just a matter of someone going into the code, and (usually) > only modifying the includes that are used and changing some of the > definitions of macros used during the compile process. Often times, it's > even simpler than that, so to be honest, I see no value in the macports > collection myself, but that's just me. > > But, to get back to your original question, you will need to make sure you > have the development tools installed that apple has for download on their > web site. Make sure you have the latest xtools development environment, and > you're likely to do just fine with the make issue you're experiencing. If > not, then you are going to need to learn quite a bit more about compiling > software on your mac in terminal mode before you are likely to be successful > with this project. > > <--- Mac Access At Mac Access Dot Net ---> > > To reply to this post, please address your message to > [email protected] > > You can find an archive of all messages posted to the Mac-Access forum at > the list's public Mail Archive: > <http://www.mail-archive.com/[email protected]/>. > Subscribe to the list's RSS feed from: > <http://www.mail-archive.com/[email protected]/maillist.xml> > > As the Mac Access Dot Net administrators, we always strive to ensure that > the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and > worm-free. However, this should in no way replace your own security > strategy. We assume neither liability nor responsibility should something > unpredictable happen. > > Please remember to update your membership preferences periodically by > visiting the list website at: > <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/> > <--- Mac Access At Mac Access Dot Net ---> To reply to this post, please address your message to [email protected] You can find an archive of all messages posted to the Mac-Access forum at the list's public Mail Archive: <http://www.mail-archive.com/[email protected]/>. Subscribe to the list's RSS feed from: <http://www.mail-archive.com/[email protected]/maillist.xml> As the Mac Access Dot Net administrators, we always strive to ensure that the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and worm-free. However, this should in no way replace your own security strategy. We assume neither liability nor responsibility should something unpredictable happen. Please remember to update your membership preferences periodically by visiting the list website at: <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
