Re: [leaf-user] ubering4

[Andrew <ni...@se...>]

  29.08.2010 23:32, Stefaan Van Dooren пишет:
> Andrew,
>
> This is the error I get when I leave the no-stack-protector flag in :
>
> creating cache ./config.cache
> checking host system type... i386-pc-linux-gnu
> checking target system type... i386-pc-linux-gnu
> checking build system type... i386-pc-linux-gnu
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether ln works... yes
> checking whether ln -s works... yes
> checking for gcc... gcc-3.3
> checking whether the C compiler (gcc-3.3 -fno-stack-protector ) works... no
> configure: error: installation or configuration problem: C compiler cannot create executables.
> make: *** [/home/stefaan/leaf2/src/bering-uclibc4/buildtool/source/buildenv/binutils-2.16.1-build/.configured] Fout 1
> make: Map '/home/stefaan/leaf2/src/bering-uclibc4/buildtool/source/buildenv' wordt verlaten
>
>
> and in this is config.log from the binutils-build directory :
>
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> configure:595: checking host system type
> configure:616: checking target system type
> configure:634: checking build system type
> configure:689: checking for a BSD compatible install
> configure:742: checking whether ln works
> configure:766: checking whether ln -s works
> configure:1809: checking for gcc
> configure:1922: checking whether the C compiler (gcc-3.3 -fno-stack-protector ) works
> configure:1938: gcc-3.3 -o conftest -fno-stack-protector   conftest.c  1>&5
> cc1: error: unrecognized option `-fno-stack-protector'
> configure: failed program was:
>
> #line 1933 "configure"
> #include "confdefs.h"
>
> main(){return(0);}
>
>
> Stefaan
>
> PS : I'm not a "real" programmer, so I'm not sure I can build a patch......
>
You have gcc v3.3 preinstalled on your system, and use it for building 
all? In that case, of course, -fno-stack-protector flag will cause an 
error - it's for 4.2.x & higher compilers, to disable stack protection 
(like in earlier GCC). Possible it'll be good to check version and then 
decide if this flag needed - but is it really actual now, when most 
systems have GCC 4.2.x or even 4.4.x ?