Databases
StackOverflow2013
Postsdbo
PODistro provided cross compiler vs custom built gcc
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODistro provided cross compiler vs custom built gcc
    primarykey
    data
    text
    <p>I intend to cross compile for Raspberry Pi, basically a small ARM computer. The host will be an i686 box running Arch Linux.</p> <p>My first instinct is to use cross compiler provided by Arch Linux, arm-elf-gcc-base and arm-elf-binutils. However, every wiki and post I read seems to use some version of custom gcc build. They seem to spend significant time on cooking their own gcc. Problem is that they never say WHY it is important to use their gcc over another.</p> <ol> <li><p>Can stock distro provided cross compilers be used for building Raspberry Pi or ARM in general kernels and apps?</p></li> <li><p>Is it necessary to have multiple compilers for ARM architecture? If so, why, since single gcc can support all x86 variants?</p></li> <li><p>If 2), then how can I deduce what target subset is supported by a particular version of gcc?</p></li> <li><p>More general question, what general use cases call for custom gcc build?</p></li> </ol> <p>Please be as technical as you can, I'd like to know WHY as well as how.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNullUserException
    1. USmikijov
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODistro provided cross compiler vs custom built gcc
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COyes you can use a pre-built. download gcc or binutils sources then ./configure --help and look at the choices, if nothing else those are choices that can and do vary for a custom vs pre-built. the pre-built is just a custom using one persons preferences. also with a custom you can use specific versions of gcc, perhaps newer. also the pre-builts like codesourcery (now mentor) have improvements or changes to the source for various reasons (Addding or fixing support for a target core or operating system not in the stable source)
      singulars
      1. PODistro provided cross compiler vs custom built gcc
      1. USold_timer
    2. COa sigle gcc can support all x68 variants is too vague of a statement, gcc 2.95 cannot support the features of a 2012 released x86 can it? Nope. For the same reason you can and will see custom gcc builds with various distros or applications within x86. If gcc were perfect, no bugs at all, and finished (all features supported, completed, bug free) then there wouldnt be any updates to gcc other than adding new processors right? I dont see development on gcc demonstrating that it is finished and bug free.
      singulars
      1. PODistro provided cross compiler vs custom built gcc
      1. USold_timer
    3. COsuccessfully building a gnu based cross compiler may give you something you can do some work with but not necessarily build all of the applications or drivers needed for a distro. If you dig inside gcc you will find an ugly beast held together with duct tape and bailing wire. It takes a fair amount of time to learn to tame that beast (only to have to start learning again each release).
      singulars
      1. PODistro provided cross compiler vs custom built gcc
      1. USold_timer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload