Bug 5301 - Cross-compiler docs problems
Summary: Cross-compiler docs problems
Status: NEW
Alias: None
Product: gcc
Classification: Unclassified
Component: bootstrap (show other bugs)
Version: 3.1
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL: http://crosstool-ng.github.io/
Keywords: documentation
Depends on:
Blocks:
 
Reported: 2002-01-07 10:06 UTC by Joseph S. Myers
Modified: 2021-03-31 20:50 UTC (History)
3 users (show)

See Also:
Host: i686-pc-linux-gnu
Target: i686-pc-linux-gnu
Build: i686-pc-linux-gnu
Known to work:
Known to fail:
Last reconfirmed: 2006-03-05 03:56:45


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph S. Myers 2002-01-07 10:06:00 UTC
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

Release:
3.1 20020107 (experimental)

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

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.
Comment 1 Joseph S. Myers 2002-01-07 10:06:00 UTC
Fix:
Document cross-compilers properly.
Comment 2 Joseph S. Myers 2002-01-07 10:08:41 UTC
State-Changed-From-To: open->analyzed
State-Changed-Why: Confirmed as a bug, marking priority "high" at request of
    Gerald.
Comment 3 dank 2003-06-19 04:32:38 UTC
On the theory that a working build script is a good adjunct to
the documentation, I am assembling a script that can build and
test gcc/glibc/linux cross toolchains from scratch for all architectures
supported by glibc.  I am initially focusing on building from
release tarballs in a nonunified tree.  I am also documenting
how to set up dejagnu to do remote testing of gcc/glibc.
Eventually I may add gdb building/testing to the script.
The script and documentation is online at http://kegel.com/crosstool
while I work on it.
Comment 4 dank 2003-07-19 21:14:17 UTC
http://kegel.com/crosstool has come a ways since I last posted.
It's now quite easy to build and test crosscompilers.  
My script still doesn't run the glibc regression test, but at
least it runs the gcc/g++/stdlibc++ tests.  Anyone who's having
trouble building or testing crosscompilers should have a look
at that page.  In fact, it'd be nice if http://gcc.gnu.org/install/
or a related page linked to http://kegel.com/crosstool.
Comment 5 Eric Gallager 2018-07-04 04:35:09 UTC
(In reply to dank from comment #4)
> http://kegel.com/crosstool has come a ways since I last posted.
> It's now quite easy to build and test crosscompilers.  
> My script still doesn't run the glibc regression test, but at
> least it runs the gcc/g++/stdlibc++ tests.  Anyone who's having
> trouble building or testing crosscompilers should have a look
> at that page.  In fact, it'd be nice if http://gcc.gnu.org/install/
> or a related page linked to http://kegel.com/crosstool.

Link says that documentation is out of date and to see
http://crosstool-ng.github.io/
instead.