On 8/9/12 12:30 PM, Patterson, James wrote: > OK...what do I do with that? > > I guess I am saying it did stop the build in my case...
Ultimately, yes. What I meant was that it didn't immediately cause the build to end. > > If I try to edit AuUnlock.c it just gets changed back to the original. > > It may be helpful to interject here that I am fairly resourceful at compiling > things that are not broken, but have never fixed things that wouldn't compile > at this level of difficulty... > fink doesn't support editing in the source tree--when you issue a new "fink" command, the original source gets used. To have changes persist, you'd need to append them to the tightvnc.patch file as diffs from the original source Older gcc compilers, like those from 10.6 and earlier, apparently just ignored this error. We're working on it at this end, too. -- Alexander Hansen, Ph.D. Fink User Liaison My package updates: http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fink-beginners mailing list Fink-beginners@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.beginners Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-beginners
