<div>
&gt;&gt; cannot execute binary file 
Are you sure the compiler has generated an executable that is compatible with the system you are trying to run it on? Try using the 'file' command to see what the system thinks it is. 
 
file mkkeywordhash
</div>

<div>
Hi, 
The result of [file mkkeywordhash]: 
mkkeywordhash: ELF 32-bit LSB MIPS-I executable, MIPS, version 1 (SYSV), dynamically linked (uses shared libs), not stripped 
I guess the mkkeywordhash isn't compatible with my system Red Hat Linux. &nbsp;How can I know if the executable file is compatible or not?
</div>

<div>
If the executable file isn't compatible with the system I am trying to run it on, how could I compile it with mipsel-uclibc-gcc? Thank you.
</div>

<div>
&gt;&gt; How can I know if the executable file is compatible or not? 
It'll run I guess :) 
 
&gt;&gt;&nbsp;how could I compile it with mipsel-uclibc-gcc? 
I'm sorry I don't know.
</div>

<div>
&gt;&gt; How can I know if the executable file is compatible or not? 
 
Since you are using a cross compiler, it most likely WON'T be compatible. The solution is to compile mkkeywordhash with the normal gcc compiler, since that binary is apparently only used as an intermediary stage (make sure to confirm that) in the compilation of sqlite.
</div>

<div>
Hi, 
I read the comment in Makefile, &nbsp;and modify the value of BCC as &quot;gcc -g -O2&quot;. I get another error message: 
------------------------------------------------------------------------------------------------------------------- 
gcc -g -O2 -o lemon ../tool/lemon.c 
cp ../tool/lempar.c . 
cp ../src/parse.y . 
./lemon &nbsp;parse.y 
mv parse.h parse.h.temp 
gawk -f ../addopcodes.awk parse.h.temp &gt;parse.h 
cat parse.h ../src/vdbe.c | gawk -f ../mkopcodeh.awk &gt;opcodes.h 
sort -n -b -k 3 opcodes.h | gawk -f ../mkopcodec.awk &gt;opcodes.c 
rm -rf tsrc 
mkdir -p tsrc 
cp ../src/alter.c ../src/analyze.c ../src/attach.c ../src/auth.c ../src/bitvec.c ../src/btmutex.c ../src/btree.c ../src/btree.h ../src/btreeInt.h ../src/build.c ../src/callback.c ../src/complete.c ../src/date.c ../src/delete.c ../src/expr.c ../src/fault.c ../src/func.c ../src/hash.c ../src/hash.h ../src/insert.c ../src/journal.c ../src/legacy.c ../src/loadext.c ../src/main.c ../src/malloc.c ../src/mem1.c ../src/mem2.c ../src/mem3.c ../src/mem4.c ../src/mem5.c ../src/mutex.c ../src/mutex.h ../src/mutex_os2.c ../src/mutex_unix.c ../src/mutex_w32.c ../src/os.c ../src/os.h ../src/os_common.h ../src/os_unix.c ../src/os_win.c ../src/os_os2.c ../src/pager.c ../src/pager.h ../src/parse.y ../src/pragma.c ../src/prepare.c ../src/printf.c ../src/random.c ../src/select.c ../src/shell.c ../src/sqlite.h.in ../src/sqlite3ext.h ../src/sqliteInt.h ../src/sqliteLimit.h ../src/table.c ../src/tclsqlite.c ../src/tokenize.c ../src/trigger.c ../src/utf.c ../src/update.c ../src/util.c ../src/vacuum.c ../src/vdbe.c ../src/vdbe.h ../src/vdbeapi.c ../src/vdbeaux.c ../src/vdbeblob.c ../src/vdbefifo.c ../src/vdbemem.c ../src/vdbeInt.h ../src/vtab.c ../src/where.c keywordhash.h opcodes.c opcodes.h parse.c parse.h config.h sqlite3.h ../ext/fts1/fts1.c ../ext/fts1/fts1.h ../ext/fts1/fts1_hash.c ../ext/fts1/fts1_hash.h ../ext/fts1/fts1_porter.c ../ext/fts1/fts1_tokenizer.h ../ext/fts1/fts1_tokenizer1.c ../ext/fts2/fts2.c ../ext/fts2/fts2.h ../ext/fts2/fts2_hash.c ../ext/fts2/fts2_hash.h ../ext/fts2/fts2_icu.c ../ext/fts2/fts2_porter.c ../ext/fts2/fts2_tokenizer.h ../ext/fts2/fts2_tokenizer.c ../ext/fts2/fts2_tokenizer1.c ../ext/fts3/fts3.c ../ext/fts3/fts3.h ../ext/fts3/fts3_hash.c ../ext/fts3/fts3_hash.h ../ext/fts3/fts3_icu.c ../ext/fts3/fts3_porter.c ../ext/fts3/fts3_tokenizer.h ../ext/fts3/fts3_tokenizer.c ../ext/fts3/fts3_tokenizer1.c ../ext/icu/icu.c tsrc 
rm tsrc/sqlite.h.in tsrc/parse.y 
touch .target_source 
tclsh ../tool/mksqlite3c.tcl 
./libtool --mode=compile --tag=CC mipsel-uclibc-gcc &nbsp;-g -O2 -DOS_UNIX=1 -I. -I../src -D_HAVE_SQLITE_CONFIG_H -DNDEBUG &nbsp;-I/usr/local/include -DSQLITE_THREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 &nbsp;-c sqlite3.c 
libtool: compile: &nbsp;mipsel-uclibc-gcc -g -O2 -DOS_UNIX=1 -I. -I../src -D_HAVE_SQLITE_CONFIG_H -DNDEBUG -I/usr/local/include -DSQLITE_THREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c sqlite3.c &nbsp;-fPIC -DPIC -o .libs/sqlite3.o 
sqlite3.c:9023: warning: `sqlite3KeywordCode' used but never defined 
libtool: compile: &nbsp;mipsel-uclibc-gcc -g -O2 -DOS_UNIX=1 -I. -I../src -D_HAVE_SQLITE_CONFIG_H -DNDEBUG -I/usr/local/include -DSQLITE_THREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c sqlite3.c -o sqlite3.o &gt;/dev/null 2&gt;&amp;1 
./libtool --mode=link mipsel-uclibc-gcc &nbsp;-g -O2 -DOS_UNIX=1 -I. -I../src -D_HAVE_SQLITE_CONFIG_H -DNDEBUG &nbsp;-I/usr/local/include -DSQLITE_THREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 &nbsp; -o libsqlite3.la sqlite3.lo -lpthread &nbsp;\ 
&nbsp;-rpath &quot;/usr/local/lib&quot; -version-info &quot;8:6:8&quot; 
libtool: link: gcc -shared &nbsp;.libs/sqlite3.o &nbsp; -lpthread &nbsp; &nbsp;-Wl,-soname -Wl,libsqlite3.so.0 -o .libs/libsqlite3.so.0.8.6 
.libs/sqlite3.o: file not recognized: Bad value 
collect2: ld returned 1 exit status 
make: *** [libsqlite3.la] Error 1 

<pre><code class="code-10 nolinks" id="code-121383"># C Compiler and options for use in building executables that
# will run on the platform that is doing the build.
#
BCC = gcc -g -O2
 
# C Compile and options for use in building executables that
# will run on the target platform. (BCC and TCC are usually the
# same unless your are cross-compiling.)
#
TCC = mipsel-uclibc-gcc -g -O2 -DOS_UNIX=1 -I. -I${TOP}/src
</code></pre>
</div>

<div>
Are you using the right libtool (ie. for the system you are cross compiling to) ?
</div>

<div>
How do I know the libtool is right?
</div>

<div>
Do you mean that I need to modify the libtool Bourne shell script or modify the ../configure Bourne shell script?
</div>

<div>
How do you know the tools used by libtool are the ones for the normal gcc in error message? 

<pre><code class="code-10 nolinks" id="code-122485">gcc -g -O2 -o lemon ../tool/lemon.c
cp ../tool/lempar.c .
cp ../src/parse.y .
./lemon parse.y
mv parse.h parse.h.temp
gawk -f ../addopcodes.awk parse.h.temp &gt;parse.h
cat parse.h ../src/vdbe.c | gawk -f ../mkopcodeh.awk &gt;opcodes.h
sort -n -b -k 3 opcodes.h | gawk -f ../mkopcodec.awk &gt;opcodes.c
rm -rf tsrc
mkdir -p tsrc
cp ../src/alter.c ../src/analyze.c ../src/attach.c ../src/auth.c ../src/bitvec.c ../src/btmutex.c ../src/btree.c ../src/btree.h ../src/btreeInt.h ../src/build.c ../src/callback.c ../src/complete.c ../src/date.c ../src/delete.c ../src/expr.c ../src/fault.c ../src/func.c ../src/hash.c ../src/hash.h ../src/insert.c ../src/journal.c ../src/legacy.c ../src/loadext.c ../src/main.c ../src/malloc.c ../src/mem1.c ../src/mem2.c ../src/mem3.c ../src/mem4.c ../src/mem5.c ../src/mutex.c ../src/mutex.h ../src/mutex_os2.c ../src/mutex_unix.c ../src/mutex_w32.c ../src/os.c ../src/os.h ../src/os_common.h ../src/os_unix.c ../src/os_win.c ../src/os_os2.c ../src/pager.c ../src/pager.h ../src/parse.y ../src/pragma.c ../src/prepare.c ../src/printf.c ../src/random.c ../src/select.c ../src/shell.c ../src/sqlite.h.in ../src/sqlite3ext.h ../src/sqliteInt.h ../src/sqliteLimit.h ../src/table.c ../src/tclsqlite.c ../src/tokenize.c ../src/trigger.c ../src/utf.c ../src/update.c ../src/util.c ../src/vacuum.c ../src/vdbe.c ../src/vdbe.h ../src/vdbeapi.c ../src/vdbeaux.c ../src/vdbeblob.c ../src/vdbefifo.c ../src/vdbemem.c ../src/vdbeInt.h ../src/vtab.c ../src/where.c keywordhash.h opcodes.c opcodes.h parse.c parse.h config.h sqlite3.h ../ext/fts1/fts1.c ../ext/fts1/fts1.h ../ext/fts1/fts1_hash.c ../ext/fts1/fts1_hash.h ../ext/fts1/fts1_porter.c ../ext/fts1/fts1_tokenizer.h ../ext/fts1/fts1_tokenizer1.c ../ext/fts2/fts2.c ../ext/fts2/fts2.h ../ext/fts2/fts2_hash.c ../ext/fts2/fts2_hash.h ../ext/fts2/fts2_icu.c ../ext/fts2/fts2_porter.c ../ext/fts2/fts2_tokenizer.h ../ext/fts2/fts2_tokenizer.c ../ext/fts2/fts2_tokenizer1.c ../ext/fts3/fts3.c ../ext/fts3/fts3.h ../ext/fts3/fts3_hash.c ../ext/fts3/fts3_hash.h ../ext/fts3/fts3_icu.c ../ext/fts3/fts3_porter.c ../ext/fts3/fts3_tokenizer.h ../ext/fts3/fts3_tokenizer.c ../ext/fts3/fts3_tokenizer1.c ../ext/icu/icu.c tsrc
rm tsrc/sqlite.h.in tsrc/parse.y
touch .target_source
tclsh ../tool/mksqlite3c.tcl
./libtool --mode=compile --tag=CC mipsel-uclibc-gcc -g -O2 -DOS_UNIX=1 -I. -I../src -D_HAVE_SQLITE_CONFIG_H -DNDEBUG -I/usr/local/include -DSQLITE_THREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c sqlite3.c
libtool: compile: mipsel-uclibc-gcc -g -O2 -DOS_UNIX=1 -I. -I../src -D_HAVE_SQLITE_CONFIG_H -DNDEBUG -I/usr/local/include -DSQLITE_THREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c sqlite3.c -fPIC -DPIC -o .libs/sqlite3.o
sqlite3.c:9023: warning: `sqlite3KeywordCode' used but never defined
libtool: compile: mipsel-uclibc-gcc -g -O2 -DOS_UNIX=1 -I. -I../src -D_HAVE_SQLITE_CONFIG_H -DNDEBUG -I/usr/local/include -DSQLITE_THREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c sqlite3.c -o sqlite3.o &gt;/dev/null 2&gt;&amp;1
./libtool --mode=link mipsel-uclibc-gcc -g -O2 -DOS_UNIX=1 -I. -I../src -D_HAVE_SQLITE_CONFIG_H -DNDEBUG -I/usr/local/include -DSQLITE_THREADSAFE=1 -DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -o libsqlite3.la sqlite3.lo -lpthread \
 -rpath &quot;/usr/local/lib&quot; -version-info &quot;8:6:8&quot;
libtool: link: gcc -shared .libs/sqlite3.o -lpthread -Wl,-soname -Wl,libsqlite3.so.0 -o .libs/libsqlite3.so.0.8.6
.libs/sqlite3.o: file not recognized: Bad value
collect2: ld returned 1 exit status
make: *** [libsqlite3.la] Error 1
</code></pre>
</div>

<div>
Thank you. I already solve this problem.
</div>

<div>
&gt;&gt; How do you know the tools used by libtool are the ones for the normal gcc in error message? 
 
Not with 100% certainty, but the error message was consistent with trying to use libtool on object files with an unexpected format (ie. for another system).
</div>

<div>
<div class="content wysiwyg-content">
Hi, experts: 
My OS is Red Hat Linux. I compile SQLite3 source code with mipsel-uclibc-gcc compiler. I follow the README: 
--------------------------------------------------------- 
&nbsp; &nbsp; tar xzf sqlite.tar.gz &nbsp; &nbsp;;# &nbsp;Unpack the source tree into &quot;sqlite&quot; 
&nbsp; &nbsp; mkdir bld &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;;# &nbsp;Build will occur in a sibling directory 
&nbsp; &nbsp; cd bld &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ;# &nbsp;Change to the build directory 
&nbsp; &nbsp; ../sqlite/configure &nbsp; &nbsp; &nbsp;;# &nbsp;Run the configure script 
&nbsp; &nbsp; make &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ;# &nbsp;Run the makefile. 
&nbsp; &nbsp; make install &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ;# &nbsp;(Optional) Install the build products 
--------------------------------------------------------- 
After execute [../sqlite/configure], I modify the Makefile (replace gcc with mipsel-uclibc-gcc) 
&nbsp; &nbsp;BCC = mipsel-uclibc-gcc -g -O2 
&nbsp; &nbsp;TCC = mipsel-uclibc-gcc &nbsp;-g -O2 -DOS_UNIX=1 -I. -I${TOP}/src 
&nbsp; &nbsp;TCL = 0 
And I execute [make], I get the following error message: 
---------------------------------------------------------- 
mipsel-uclibc-gcc -g -O2 -o mkkeywordhash &nbsp;../tool/mkkeywordhash.c 
./mkkeywordhash &gt;keywordhash.h 
/bin/sh: line 1: ./mkkeywordhash: cannot execute binary file 
make: *** [keywordhash.h] Error 126 
---------------------------------------------------------- 
What should I do? 
Thank you.
</div>
</div>

Hi, experts:
My OS is Red Hat Linux. I compile SQLite3 source code with mipsel-uclibc-gcc compiler. I follow the README:
---------------------------------------------------------
    tar xzf sqlite.tar.gz    ;#  Unpack the source tree into "sqlite"
    mkdir bld                ;#  Build will occur in a sibling directory
    cd bld                   ;#  Change to the build directory
    ../sqlite/configure      ;#  Run the configure script
    make                     ;#  Run the makefile.
    make install             ;#  (Optional) Install the build products
---------------------------------------------------------
After execute [../sqlite/configure], I modify the Makefile (replace gcc with mipsel-uclibc-gcc)
   BCC = mipsel-uclibc-gcc -g -O2
   TCC = mipsel-uclibc-gcc  -g -O2 -DOS_UNIX=1 -I. -I${TOP}/src
   TCL = 0
And I execute [make], I get the following error message:
----------------------------------------------------------
mipsel-uclibc-gcc -g -O2 -o mkkeywordhash  ../tool/mkkeywordhash.c
./mkkeywordhash >keywordhash.h
/bin/sh: line 1: ./mkkeywordhash: cannot execute binary file
make: *** [keywordhash.h] Error 126
----------------------------------------------------------
What should I do? 
Thank you.

mipsel-uclibc-gcc compiles SQLite3

A Linux distribution is an operating system made as a software collection based on the Linux kernel and, often, on a package management system and are available for a variety of systems. A typical Linux distribution comprises a Linux kernel, GNU tools and libraries, additional software, documentation, a window system (the most common being the X Window System), a window manager, and a desktop environment. Most Linux systems are open-source software made available both as compiled binaries and in source code form, allowing modifications to the original software. Over three hundred distributions are in active development, including commercially backed distributions (such as Fedora, openSUSE and Ubuntu) and community-driven distributions (such as Debian, Slackware, Gentoo and Arch Linux).

Linux Distributions

C is a general-purpose, imperative computer programming language, supporting structured programming, lexical variable scope and recursion, while a static type system prevents many unintended operations. By design, C provides constructs that map efficiently to typical machine instructions, so it has found lasting use in applications that had formerly been coded in assembly language, including operating systems as well as various application software for computers ranging from supercomputers to embedded systems. It is distinct from C++ (which has its roots in C) and C#, and many later languages have borrowed directly or indirectly from C.