-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Schaffner wrote: > I did that and now octave-forge did indeed build. And it runs fine. I > think it would be ready for the stable tree.
list: Any objections to me adding the current octave-forge to stable? > The only thing weird i noticed were tons of warnings like: > > ld: warning multiple definitions of symbol __nc_infotocap > /usr/lib/libtermcap.dylib(captoinfo.o) definition of __nc_infotocap > /sw/lib/libncurses.dylib(captoinfo.o) definition of __nc_infotocap > > I have no idea if they mean anything serious. I'm not sure what those mean either. I'm trying to find out, but as long as octave-forge seems to run fine and it does for me, I'm not going to sweat about it too much. > That might be a good idea, although the fink developers were thinking > about giving a warning anyway if you try to build something with the > borked cc1plus. Yeah, I know. But in the mean time, I'd like to at least try to warn my users. If/when the warning gets added to fink proper, I'll remove the notice from octave-forge. crh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBZ/qHHttEfMmUResRAjzgAJ405m0CaK/V76i3iKMwqD6f9gZCmgCdGc+9 bVP8+/wjAWZpmb4u8WA6HAs= =D/01 -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
