[haiku-development] Re: Extra cross-compiler binaries created?
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 29 May 2008 23:31:26 +0200
On 2008-05-29 at 23:16:54 [+0200], Urias McCullough <umccullough@xxxxxxxxx>
wrote:
> 2008/5/29 Ingo Weinhold <ingo_weinhold@xxxxxx>:
> > My guess would be that the bin/<target>-* executables are used preferrably
> > in build systems supporting cross-compilation to avoid name clashes with
> > the host tools, while <target>/bin/* are the "normally" named executables.
> > Note that save for "gcc" (don't know why the exception) both sets of
> > executables hard link to the same files; in FSs that support hard links
> > that is.
>
> Ah, so you're saying this is not something that has been explicitly
> done for Haiku, but rather the configure script for gcc has made this
> decision for us? Interesting.
Exactly, that's what gcc's/binutils' "make install" produce.
> FWIW, I'm currently using Xubuntu 8.04 x86 (32-bit) for my haiku build
> environment.
>
> I didn't realize they were hardlinked - I'll have to double-check that
> again.
>
> In any case, I will assume that either compiler may end up being used
> for the compilation of Haiku targets during the Coverity scans.
Haiku's build system uses the bin/<target>-* executables directly only. gcc
invokes subprocesses (pre-processor, assembler, linker), for which it might
use the other paths. Not sure how relevant this is for Coverity. If
configuring Coverity to consider both paths is no problem, you're definitely
on the safe side doing it.
CU, Ingo
Other related posts:
