In message <[email protected]> alan buckley <[email protected]> wrote:
> > On Fri, 17 Apr 2009 11:25:40 +0100 John Tytgat wrote: > > > In message > > alan buckley wrote: > > > >> On Sat, 11 Apr 2009 12:50:04 +0100 John Tytgat wrote: > >>> This confuses me. Yes, c++filt is an executable build from sources in > >>> binutils. But why say "needs to be shipped there" ? We don't have a > >>> separate binutils kit. And as this tool is only useful for C++ users, > >>> it is currently in the C++ compiler kit. > >> > >> Sorry, badly worded. I meant it looks as if it should be shipped as > >> part of the gcc kit (which includes the other binutils) rather than > >> the C++ kit. As you say it's probably useful only for c++ users, but > >> it appears in the binutils documentation which is why I thought it > >> may belong there. > > > > Yes, you've a point. I agree. You want me to change this, or will you > > do it ? > > > > Please can you make the change. Done: <URL:http://www.riscos.info/websvn/listing.php?repname=gccsdk&path=%2Ftrunk%2Fgcc4%2F&rev=3804&sc=1> It will also no longer trigger your "mv: cannot stat `man/man1/c++filt.1`: No such file or directory" problem as create-gcckit will no longer make an exception for that file. But still it is puzzling why you don't have that file made during your build. John. -- John Tytgat, in his comfy chair at home BASS [email protected] ARM powered, RISC OS driven _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
