[haiku-development] Re: Building Haiku and tools: configure script bugs

  • From: Oliver Tappe <zooey@xxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Sat, 26 Jul 2014 11:51:21 +0200

Hi Tom,

[please do not cc gcc@xxxxxxxxxxxxxxx, I'm subscribed to the Haiku mailing 
lists, so I'm getting your mails twice]

On 2014-07-26 at 07:59:37 [+0200], Thomas Mueller <mueller6723@xxxxxxx> wrote:
> I first had the problem that, when I typed "./configure --help", it 
> wouldn't help: "gcc: not found"
>
> Now I get, from FreeBSD in an xterm
> 
> [arlene1164@amelia2 ~/haiku/haiku/generated.473-nodl]$ ../configure 
> HAIKU_CC_x86_gcc2=gcc47 --build-crosstools x86_gcc2 ../../buildtools 
> --build-crosstools x86 --use-xattr-ref --include-gpl-addons --include 
> 3rdparty
> ../configure: gcc: not found

Thanks for the hint - this has been fixed now. Starting with hrev47574, 
configure supports overriding the name of the host compiler via the CC 
environment variable. Additionally, invoking 'configure --help' (or just 
'configure') will show the help text without requiring gcc.

> Command line is
> 
> ../configure HAIKU_CC_x86_gcc2=gcc47 --build-crosstools x86_gcc2 
> ../../buildtools --build-crosstools x86 --use-xattr-ref 
> --include-gpl-addons --include 3rdparty
> 
> I thought it would be sufficient to tell configure where the gcc was.  What 
> if I use clang and there is no gcc?
> 
> Does HAIKU_CC_x86_gcc2 have no meaning?  I can't set it to 
> /usr/local/bin/gcc47?  I tried

Of course it has meaning, just not the one you hoped it would have. With 
HAIKU_CC_x86_gcc2 you can override the cross-compiler to be used for building 
Haiku for the x86_gcc2 architecture. That won't help in any way with the host 
compiler, though.

[ ... ]
> I finally got configure to run by cd to 
> /home/arlene1164/haiku/haiku/generated.473-nodl and
> ln -s /usr/local/bin/gcc47 gcc
> 
> I was expecting only a configure, not a compile, so didn't add anything 
> like "2>&1 | tee build.log", but it tried to compile, but unsuccessfully, 
> ending with

Passing --build-cross-tools to configure will cause it to build cross tools 
(not such a surprising concept, if you think about it).

cheers,
        Oliver

Other related posts: