This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
other/5301: Cross-compiler docs problems
- From: Joseph Myers <jsm28 at cam dot ac dot uk>
- To: gcc-gnats at gcc dot gnu dot org
- Cc: jsm28 at cam dot ac dot uk
- Date: Mon, 07 Jan 2002 18:05:38 +0000
- Subject: other/5301: Cross-compiler docs problems
>Number: 5301
>Category: other
>Synopsis: Cross-compiler docs problems
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Mon Jan 07 10:06:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 3.1 20020107 (experimental)
>Organization:
none
>Environment:
System: Linux digraph 2.2.20 #2 Sat Nov 10 16:44:22 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/mainline --disable-shared --enable-threads=posix --with-system-zlib
>Description:
The documentation of how to build cross-compilers is inadequate, and
is split into two parts (current installation manual doc/install.texi,
and parts in doc/install-old.texi that have not been merged into the
main installation manual) plus an unofficial FAQ.
I have many times requested that people deal with this; no-one has
done so. List of requests in:
http://gcc.gnu.org/ml/gcc/2002-01/msg00370.html
>How-To-Repeat:
Attempt to build cross-compilers using just the current documentation,
without the old install manual or CrossGCC FAQ, especially in more
complicated cases such as:
* Canadian crosses.
* Crossing into a glibc-based target, without pre-existing GCC or
glibc libraries or headers for that target (where glibc and libgcc
interdepend).
* Not using a unified tree.
>Fix:
Document cross-compilers properly.
>Release-Note:
>Audit-Trail:
>Unformatted: