search for: ac_link

...GS is not in ac_cpp because -g, -O, etc. are not valid cpp options. @@ -712,12 +714,12 @@ cat > conftest.$ac_ext << EOF -#line 716 "configure" +#line 718 "configure" #include "confdefs.h" main(){return(0);} EOF -if { (eval echo configure:721: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then +if { (eval echo configure:723: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then ac_cv_prog_cc_works=yes # If we can't run a t...

...GS is not in ac_cpp because -g, -O, etc. are not valid cpp options. @@ -712,12 +714,12 @@ cat > conftest.$ac_ext << EOF -#line 716 "configure" +#line 718 "configure" #include "confdefs.h" main(){return(0);} EOF -if { (eval echo configure:721: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then +if { (eval echo configure:723: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then ac_cv_prog_cc_works=yes # If we can't run a t...

...h" >#include "./tests/summarry.c" And the line 9472 (and around) in the file "configure": >#line 9472 "configure" >#include "confdefs.h" >#include "${srcdir-.}/tests/summary.c" >EOF >if { (eval echo configure:9476: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest && (./conftest; exit) 2>/dev/null >then > echo "configure OK"; >else > echo "configure: failed program was:" >&5 > cat conftest.$ac_ext >&5 > rm -fr con...

Hi, I have asked this question earlier, but did not receive an answer.... I'm trying to build 3.2.3a on a RedHat 7.2, but during configuring I get an error: #### ./configure .... .... .... checking for test rutines... configure: error: cant find test code. Aborting config #### Does any one have any clue about what is going wrong???? Regards/Casper

...a RH 72 machine and if I do a ./configure everthings work fine. If I understand the code of the configure-script right, then they write a message into a file (I think it's config.log) which program fails. Here is this part of the configure script: ... if { (eval echo configure:10396: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null then echo "$ac_t""yes" 1>&6 else echo "configure: failed program was:" >&5 cat conftest.$ac_ext >&5...

...internal prototype to avoid an error. */ + /* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ + char SOCKSconnect(); + + int main() { + SOCKSconnect() + ; return 0; } + EOF + if { (eval echo configure:6861: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then + rm -rf conftest* + eval "ac_cv_lib_$ac_lib_var=yes" + else + echo "configure: failed program was:" >&5 + cat conftest.$ac_ext >&5 + rm -rf conftest* + eval "ac_...

The following patches shave some rough edges off the tools build system to allow cross compiling for at least arm32 and arm64 based on the Debian/Ubuntu multiarch infrastructure. They also add the necessary fixes to build for arm64 (which I have only tried cross, not native). I have posted some instructions on how to compile with these patches on the wiki:

...because int might match the return type of a gcc2 > > builtin and then its argument prototype would still apply. */ > > char dn_expand(); > > > > int main() { > > dn_expand() > > ; return 0; } > > EOF > > if { (eval echo configure:10744: \"$ac_link\") 1>&5; (eval $ac_link) > 2>&5; } && > > test -s conftest${ac_exeext}; then > > rm -rf conftest* > > eval "ac_cv_lib_$ac_lib_var=yes" > > else > > echo "configure: failed program was:" >&5 > > cat...

> From: Peter Dalgaard BSA <p.dalgaard@biostat.ku.dk> > > Martin Maechler <maechler@stat.math.ethz.ch> writes: > > > Reading the long output of ``cc -flags'', > > I see that more than average optimization is done using > > cc -xO[1-4] > > # And -O is -xO2. If you do want higher speed, you need to use other flags too, and -fast is a

...execstack -fstack-protector-strong -pie -lssh -lopenbsd-compat -lutil -lz -lcrypt -lresolv > /usr/bin/ld: unrecognized option '-Wl,-z,relro' That's a slightly different problem: -Wl is a gcc flag that means "pass the following flag through to the linker". Since AC_LINK_IFLESE uses $CC and not $LD, this works in configure, but apparently bare ld does not understand -Wl. The only way I can think of right now to fix that is to manually invoke $LD inside the test macro. Lemme have a bit more of a think. -- Darren Tucker (dtucker at dtucker.net) GPG key 11EAA6FA /...

Morten Ofstad wrote: >> Hi, >> >> There's no HAVE_RAND48 symbol provided by autoconf. You'll have to >> add the appropriate check to autoconf/configure.ac before we can take >> this patch. I installed autoconf with cygwin now and I think I've managed to do this right now -- there are some strange problems with running the AutoRegen.sh script, so I

> Hi, > > There's no HAVE_RAND48 symbol provided by autoconf. You'll have to add > the appropriate check to autoconf/configure.ac before we can take this > patch. Sorry I forgot to mention I didn't make any changes to the configure script. The problem is that I can't test these things since I'm not on a Unix platform, and I'm not even using the

...! extern "C" ! #endif + int loginfailed (); + int (*f) (); + int main () { ! f=loginfailed ! ; ! return 0; } _ACEOF ! rm -f conftest.$ac_objext conftest$ac_exeext ! if { (eval echo "$as_me:3193: \"$ac_link\"") >&5 ! (eval $ac_link) 2>&5 ! ac_status=$? ! echo "$as_me:3196: \$? = $ac_status" >&5 ! (exit $ac_status); } && ! { ac_try='test -s conftest$ac_exeext' ! { (eval echo &quot...

Aloha. The current CVS snapshot and 1.0-test14 will not build on Solaris 8 because it does not provide a sendfile() funtion. It just has sendfilev(). Solaris 9 has sendfile(), though. Using the old sendfile-util.c from 1.0-test1 and setting HAVE_SOLARIS_SENDFILEV instead of HAVE_LINUX_SENDFILE in config.h works. Greetings, Andy.

...ipt tests that f77 is running by attempting to compile and link a dummy program - the link step seems broken on the alpha (it doesn't like the command f77 -o conftest conftest.f -L/usr/local/lib The command works fine without the -L switch. ) my workaround was to remove $LIBS from the line ac_link='${F77-f77} -o conftest${ac_exeext} $FFLAGS $LDFLAGS conftest.$ac_ext $L IBS 1>&5' but a better alternative may be to just use the fortran compiler to produce an object file rather than an executable. R configured using the following options passes "make test" R is now c...

Well, as Andrew shouted at me again this weekend it's getting to be about that time.... :-) :-). Yep, we're thinking we should do an official 2.2 Samba release early next week, so if you have anything you can't live with, now would be a good time to tell us.... :-). It's been gestating longer than an elephant, so it's really time to let it out into the world and do its own

...-pie -lssh -lopenbsd-compat -lutil -lz -lcrypt -lresolv >>> /usr/bin/ld: unrecognized option '-Wl,-z,relro' >> >> That's a slightly different problem: -Wl is a gcc flag that means >> "pass the following flag through to the linker". Since AC_LINK_IFLESE >> uses $CC and not $LD, this works in configure, but apparently bare ld >> does not understand -Wl. The only way I can think of right now to fix >> that is to manually invoke $LD inside the test macro. Lemme have a >> bit more of a think. > > Looking into au...

...project/llvm/trunk/configure?rev=139934&r1=139933&r2=139934&view=diff > > ============================================================================== > --- llvm/trunk/configure (original) > +++ llvm/trunk/configure Fri Sep 16 15:36:16 2011 > @@ -5817,7 +5817,7 @@ > ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS > conftest.$ac_ext $LIBS >&5' > ac_compiler_gnu=$ac_cv_c_compiler_gnu > if test -n "$ac_tool_prefix"; then > - for ac_prog in gcc > + for ac_prog in clang llvm-gcc gcc > do > # Extract the...