This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


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: build status for cross builds?


>>>>> "dewar" == dewar  <dewar@gnat.com> writes:

 dewar> Well maybe the reason that it does not get a whole lot of
 dewar> attention is that it is not clear that it is a significant
 dewar> problem. Certainly we build lots and lots of cross-GCC
 dewar> configurations to lots of targets, including MIPS, without any
 dewar> difficulties. Now to be fair, this is done by people with lots
 dewar> of GCC build experience, and no doubt it may well be fair to
 dewar> note that there is knowledge that is not being documented. The
 dewar> trouble is that people who can do task X without any
 dewar> difficulty have difficulty finding it a priority to work on
 dewar> documenting procedures that they think are already adequately
 dewar> documented (because they have no trouble).

That makes perfect sense.  Perhaps this discussion will make it more
visible that this black art is not at all well understood beyond the
small circle of magicians you describe.  In particular, it would be
very helpful if those of you who are such magicians would take a look
at the CrossFAQ and try to merge your knowledge into it, because it is
clear to me that that document, while better than nothing, only
contains a small fraction of the necessary information.

It also seems that embedded targets may be comparatively
straightforward.  As I said, it's the NetBSD target that particularly
baffles me still, and I continue to invite any helpful comments that
might be available.

      paul


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