Dmalloc Error Cannot Run Test Program While Cross Compiling
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn
Configure: Error: Cannot Run Test Program While Cross Compiling Glib
more about Stack Overflow the company Business Learn more about hiring developers or gnu screen cross compile posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Cannot run test program while cross compiling - cross compiling Firebird up vote 0 down vote favorite I've tried to compile firebird server for arm linux, with cross-compiler (it's choosen - it's working properly). When using: ./autogen.sh --host=arm-linux-gnu I get this error: checking for working sem_init()... configure: error: in `/compile/code/firebird/trunk': configure: error: cannot run test program while cross compiling I know I'm cross-compiling, but maybe Firebird developers dissalow this (but i've read Firebird is ready to compilation for another architectures). linux arm cross-compilation sql sqlserver share|improve this question asked Dec 8 '15 at 11:49 SÅ‚awomir Kozok 12 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote Configure determines the answer to certain questions by compiling and running programs on the fly ... which it can (usually) do when the build host is the same as the target host. When you are cross-compiling, (usually) your build machine can't run the binaries produced by the cross-compiler. To overcome this, locate where the test is in the configure script and if you are lucky, the configure script will allow for the caching of the result of the test ... you can use this to fool the configure script into thinking that it already knows the answer to the question, and therefore it will not try to compile and run the binary. For example, if you were trying to cross-compile openldap 2.3.11 (an old version, I know), you may need to pass in the environment the variable ac_cv_func_memcmp_working=yes (or I think you can call configure with this setting on the command line e.g. ./configur
03:21 UTC Votes:1 Avg. Score:5.0 ± 0.0 Reproduced:0 of 1 (0.0%) From: chris at hallgren dot net Assigned: Status: Closed Package: Compile Failure PHP Version: 4.1.1 OS: RedHat 7.1 Private report: No CVE-ID: View Add Comment Developer Edit [2002-02-02 00:11 UTC] chris at hallgren dot net [root@dcprac php-4.1.1]# LIBS="-lmcrypt -lltdl" ./configure \ > --with-curl \ > --with-apache=../apache_1.3.23 \ > --enable-wddx \ > --enable-dbx \ > --enable-track-vars \ > --with-mcrypt \ > --with-mysql \ > --with-xml \ > --with-OpenSSL=/usr \ > --enable-bcmath \ http://unix.stackexchange.com/questions/248088/cannot-run-test-program-while-cross-compiling-cross-compiling-firebird > --enable-calendar \ > --enable-ftp \ > --enable-sockets loading cache ./config.cache checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal... found checking for working autoconf... found checking for working automake... found checking for working autoheader... found checking for working makeinfo... found checking whether to https://bugs.php.net/15339 enable maintainer-specific portions of Makefiles... no checking host system type... i686-pc-linux-gnu checking for gawk... gawk checking for bison... bison -y checking bison version... 1.28 (ok) checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... yes checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking how to run the C preprocessor... gcc -E checking for AIX... no checking for gcc option to accept ANSI C... none needed checking for ranlib... ranlib checking whether gcc and cc understand -c and -o together... yes checking whether ln -s works... yes checking for flex... flex checking for yywrap in -lfl... yes checking lex output file root... lex.yy checking whether yytext is a pointer... yes checking for working const... yes checking for pthreads_cflags... checking for pthreads_lib... Configuring SAPI modules checking for AOLserver support... no checking for Apache module support via DSO through APXS... no checking for Apache module support... yes - Apache 1.3.x checking for mod_charset compatibility option... no checking whet
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the http://stackoverflow.com/questions/23888063/why-cross-compiling-for-arm-fails-in-configure workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; cannot run it only takes a minute: Sign up Why cross-compiling for ARM fails in ./configure? up vote 3 down vote favorite I know the question is vague, but I didn't quite know how to express what I'm facing here: I'm trying to cross-compile an implementation of Prolog (particularly SWI-Prolog) from the sources. They use the GNU-Autoconf tools (to which I'm cannot run test a complete beginner) to build the sources, so I supposed I could set the --host and --build triplets to allow for ARM cross-compilation, but it didn't work. This is the command I issued: $ ./configure --build=i686-pc-linux-gnu --host=arm-linux-gnueabi (... lots of checks ...) checking for clock_gettime in -lrt... yes checking for clock_gettime... yes checking for pthread support for cpu clocks... configure: error: in `(...)/pl-6.6.5/src': configure: error: cannot run test program while cross compiling See `config.log' for more details (The complete output is pasted here) I've checked the config.log file, but I am unable to understand what's exactly missing. I understand that at this stage, there might be several missing libraries or errors, but I'm unable to understand where to start from. gcc arm cross-compiling autoconf swi-prolog share|improve this question asked May 27 '14 at 11:19 Carles Araguz 377219 add a comment| 1 Answer 1 active oldest votes up vote 4 down vote accepted The output of configure says: checking for pthread support for cpu clocks... configure: error: in `(...)/pl-6.6.5/src': configure: error: cannot run test program while cross comp