Failure to build cone-0.69 on Mac OS X: 'mvaddwstr' was not declared in this scope
Boey Maun Suang <[email protected]> Sun, 15 Apr 2007 21:53:15 +1000
| Newsgroups | gmane.mail.cone |
|---|---|
| Message-ID | <[email protected]> |
Hi there, I'm trying to write a MacPorts port for cone, but I haven't yet been able to get it to build. I managed to fix one error with the attached patch file (though you might find a better way of fixing it); I unfortunately didn't keep the log of what that error was (it was so long ago that I did that patch), but I assume that it was for an undefined symbol. (If you'd like, I'll rebuild it again without the patch to get the error log for you, but not tonight; I should have been asleep ages ago.) However, even with that patch in place, it terminates with the following output: OS: Mac OS X 10.4.9 Architecture: Intel Core Duo <snip> Making all in curses make all-am Compiling curses.C Compiling cursesbutton.C Compiling curseschoicebutton.C Compiling cursescontainer.C Compiling cursesdialog.C Compiling cursesfield.C Compiling cursesfilereq.C Compiling curseskeyhandler.C Compiling curseslabel.C Compiling cursesmainscreen.C Compiling cursesmultilinelabel.C Compiling cursesmoronize.C Compiling cursesobject.C Compiling cursesscreen.C cursesscreen.C: In member function 'virtual bool CursesScreen::writeText(const wchar_t*, int, int, const Curses::CursesAttr&) const': cursesscreen.C:276: error: 'mvaddwstr' was not declared in this scope make[3]: *** [cursesscreen.o] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 </snip> I can provide a full output log of the configure and build steps if anyone thinks it would be useful. Any suggestions that you might have as to how I might get this to work would be most appreciated; I'm really out of my depth with this error. Kind regards, Maun Suang P.S. Incidentally, is there a reason for running configure separately in each subdirectory, and is there a way of caching results from one subdirectory to be used in another? For me, the configure stage seems to take at least as long as the build stage (up to the failure point). P.P.S. I just noticed that configure is not finding aspell, despite the aspell binary being installed at /opt/local/bin just like the perl binary, which it does find. Any ideas on this as well? -- Boey Maun Suang (Boey is my surname) Mobile: +61 403 855 677 Email: [email protected] ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Courier-cone mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-cone
patch-rfc1035_rfc1035_res.h
(application/octet-stream, 299 B)
--- rfc1035/rfc1035_res.h 2002-07-01 03:17:05.000000000 +0000 +++ rfc1035/rfc1035_res.h.new 2007-03-12 20:44:24.000000000 +0000 @@ -40,7 +40,7 @@ unsigned randptr; } ; -extern struct rfc1035_res rfc1035_default_resolver; +struct rfc1035_res rfc1035_default_resolver; #ifdef __cplusplus }