This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Where can I get the documentation?


Please remove crossgcc-owner from your headers.  This is the mail address
for reporting problems with the crossgcc mailing list.  It is not
intended for general discussion.

On Wed, Sep 18, 2002 at 12:04:22PM +0300, Kai Ruottu wrote:
>"William A. Gatliff" <bgat@billgatliff.com> wrote:
>
>> Yilang:
>> 
>> On Wed, Sep 18, 2002 at 10:39:54AM +0800, Qiang YiLiang wrote:
>> > I just got a cross compiler which is "mips_mips_elf_gcc", its linker is 
>> > "mips_mips_elf_ld".
>> > 
>> > But I don't know how to operate them, does anyone know anywhere that I 
>> > can get the documentation of that?
>> 
>> Try: http://sources.redhat.com/binutils/docs-2.12
>> and: http://gcc.gnu.org/onlinedocs/
>
> Let's assume that someone built the binaries for the toolchain
>oneself, but for some very weird reason 'forgot' to build the
>docs coming with it...  Could this ever happen?  I think this
>being very, very common. Very little noise about these things
>(besides me usually ;-)...
>
> My point is that 'building the GNU docs' is surprisingly easy.
>When being curious and looking how on earth those PDF-docs were
>produced, I saw the 'pdftex' mentioned in some prebuilt docs and
>then found my RedHat Linux having it in the basic installation...
>Of course the Windoze-users are missing this, but they can just
>be happy with the WinHelp-format and use 'makertf' plus the MS
>free 'Help Compiler' or 'Help Toolkit', the method I used earlier
>(but running 'makertf' on Linux and then copying the '.hpj' and
>'.rtf' to Windoze for final processing).  Probably there are
>other preferences and the rich Windoze-users may have 'Adobe
>Distillers' etc. expensive tools for document-production...
>
> If talking about released binaries, it would be some kind of
>shame if these wouldn't include prebuilt docs in the 'usual'
>PDF (for Unix'es and Windoze) or WinHelp (Windoze only?) format.
>We cannot sue RedHat for this, their 'www.redhat.com/support/manuals'
>(or something else now), is well-known about the 'GNUPro' manuals
>in PDF-format... Motorola and Intel will earn thanks too, their
>MCORE and XScale distributions have included nice manuals. Also the
>ESA (European Space Association) with its 'erc32' has provided PS-
>format manuals...
>
> But as told, a GCC-builder should take care about building the
>GNU docs too, not only the binaries. The docs coming with the
>tool sources are always more up-to-date (or old enough) than the
>docs at 'gnu.org' for some other older or newer releases...
>
> Ok, with the 'mips-mips-elf' case the Algorithmics:
>  http://www.algor.co.uk
>'SDE'-toolkit docs could be a nice addition to the collection, just
>as the "SVR4 ABI, MIPS Supplement" (for MIPS 32-bit ELF etc.) at:
>  http://www.caldera.com/developers/devspecs/
>or the MIPS-document stuff at 'http://www.sgi.com'...
>
>Cheers, Kai

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]