xiaoyin0208 / lz4

Automatically exported from code.google.com/p/lz4
0 stars 0 forks source link

Not compilable on linux x64 #27

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. make all 

Actual result:
make all
gcc -m32 -Os -march=native -I. -std=c99 -Wall -W -Wundef 
-Wno-implicit-function-declaration lz4hc.c lz4.c bench.c lz4demo.c -o lz4demo32
In file included from /usr/include/features.h:385,
                 from /usr/include/stdlib.h:25,
                 from lz4hc.c:83:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory
In file included from /usr/include/features.h:385,
                 from /usr/include/stdlib.h:25,
                 from lz4.c:139:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory
In file included from /usr/include/features.h:385,
                 from /usr/include/stdlib.h:25,
                 from bench.c:48:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory
In file included from /usr/include/features.h:385,
                 from /usr/include/stdio.h:28,
                 from lz4demo.c:40:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory
make: *** [lz4demo32] Error 1

What is the expected output? What do you see instead?
Binaries created

What version of the product are you using? On what operating system?
libgcc-4.4.6-4.el6.x86_64
gcc-4.4.6-4.el6.x86_64
libgcc-4.4.6-4.el6.i686

Original issue reported on code.google.com by pe...@domyseo.com.au on 11 Jul 2012 at 3:26

GoogleCodeExporter commented 8 years ago
It seems you are trying to build the 32-bits binary on a 64-bits Linux 
distribution.

It is possible, but you need additional libraries installed on your system,
typically glibc-devel.

As a quick work around, you can also build the 64-bit binary directly :
make lz4demo64

Original comment by yann.col...@gmail.com on 11 Jul 2012 at 10:34

GoogleCodeExporter commented 8 years ago
did it help ?

Original comment by yann.col...@gmail.com on 18 Jul 2012 at 7:13

GoogleCodeExporter commented 8 years ago
In order to avoid such situation, r69 now generates native binary by default.
Compiling 32-bits binary on 64-bits systems is still possible, using : make 
lz4demo32

Original comment by yann.col...@gmail.com on 18 Jul 2012 at 8:15