Date: Tue, 4 May 1999 10:18:13 -0400 (EDT) From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: marko@uk.radan.com (Mark Ovens) Cc: cjclark@home.com, druid@eoe-magical.org, ben@scientia.demon.co.uk, freebsd-questions@FreeBSD.ORG Subject: Re: gcc compiler Message-ID: <199905041418.KAA03408@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <372E9AA9.40E638EE@uk.radan.com> from Mark Ovens at "May 4, 99 07:58:50 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Ovens wrote, > "Crist J. Clark" wrote: > > > > Donald wrote, > > > no its a unix, and their is not actualy a call to an ltoa. > > > > There must be a call somewhere. Make sure you use the '-Wall' option > > on the gcc command line too. Go to every directory that has some of > > the code you are using and try, > > > > % grep ltoa * > > > > To see if you can find it (that could spam you out if there are > > binaries around). > > > > ``grep -a ltoa *'' should deal with the binaries. I was not clear. I think he _should_ search the binaries too. He might find the stray '_ltoa' in the .o file. Of course, a better way to do that would be to, % strings file.o | grep ltoa But I did not want to get to complicated. 'grep ltoa *' will do it all, even if not pretty. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905041418.KAA03408>