On 21:21 Fri 04 Feb , Enrico Weigelt wrote: > * Nils Holland <[email protected]> wrote: > > > 1) So a package using the GNU build system determines or is passed > > (via --host aka. CHOST) a target triplet specifying the system on > > which the resulting compiled code is supposed to run. What does the > > package do with that information? Does it only use it to determine > > what it has to compile (different / special code for different systems > > / architectures), or does this already have an influence on the > > optimization of the resulting code for a certain (sub-)architecture? > > Exactly. Some packages have arch- and subarch-specific optimizations. > Those things IMHO should be primarily taken from the target triplet > (instead of other ./configure options), as it quite exactly defines > what cputype, platform and toolchain type you're using. It's very > important for crosscompiling (even some toolchains, eg. gcc., could, > and should, be explicitly asked for their target triplet).
Hi Enrico, thanks very much for your in-depth explanation in this and also your other mail you've sent in response to my question. That was really helpful, as it cleared up some things I could previously only guess about but was by no means certain about. I've learnt something new (which was my highest priority here), and can even use this knowlede to deduce what makes sense in my current experiments with building my own stage3's and install boot discs via catalyst. So, thanks again for your insightful replies! Greetings, Nils -- Nils Holland * Ti Systems, Wunstorf-Luthe (Germany) Powered by GNU/Linux since 1998
