Closed GoogleCodeExporter closed 9 years ago
Can you supply flags, toolchains, etc... Perhaps a build slave?
Original comment by dsalli...@gmail.com
on 25 Feb 2010 at 7:04
Yes. I'll setup a machine you can login an try to rebuild yourself with the
OpenWrt-SDK-x86.
This includes the toolchain for the release i try to build.
Is that okay for you ?
Original comment by h...@terminal-consulting.de
on 25 Feb 2010 at 7:39
That's a great start. I'd love a slave if you can contribute one:
http://code.google.com/p/memcached/wiki/BuildFarm
That way, we can make sure we continue to support your configuration.
Original comment by dsalli...@gmail.com
on 25 Feb 2010 at 8:21
I'll try to setup a buildbot with openwrt trunk. By the way using the sdk needs
less
work.
Original comment by h...@terminal-consulting.de
on 25 Feb 2010 at 8:48
Here are the news.
- 1.28 build without any issue
- 14.x up to 1.4.5 is not ready for cross compile
Have a look
-
mv -f .deps/memcached-memcached.Tpo .deps/memcached-memcached.Po
i486-openwrt-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -DNDEBUG
-I/openwrt/trunk/staging_dir/target-i386_uClibc-0.9.30.1/usr/include
-I/openwrt/trunk/staging_dir/target-i386_uClibc-0.9.30.1/include
-I/openwrt/trunk/staging_dir/toolchain-i386_gcc-4.4.4_uClibc-0.9.30.1/usr/includ
e -I/openwrt/trunk/staging_dir/toolchain-i386_gcc-4.4.4_uClibc-0.9.30.1/include
-O2 -pipe -march=i486 -funit-at-a-time -fhonour-copts -pthread -Wall
-pedantic -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls
-fno-strict-aliasing -MT memcached-hash.o -MD -MP -MF .deps/memcached-hash.Tpo
-c -o memcached-hash.o `test -f 'hash.c' || echo './'`hash.c
In file included from memcached.h:24,
from hash.c:12:
sasl_defs.h:4:1: warning: C++ style comments are not allowed in ISO C90
sasl_defs.h:4:1: warning: (this will be reported only once per input file)
In file included from hash.c:12:
memcached.h:305: warning: ISO C90 does not support flexible array members
hash.c:430:2: error: #error Must define HASH_BIG_ENDIAN or HASH_LITTLE_ENDIAN
make[5]: *** [memcached-hash.o] Error 1
make[5]: Leaving directory
`/openwrt/trunk/build_dir/target-i386_uClibc-0.9.30.1/memcached-1.4.5'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/openwrt/trunk/build_dir/target-i386_uClibc-0.9.30.1/memcached-1.4.5'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/openwrt/trunk/build_dir/target-i386_uClibc-0.9.30.1/memcached-1.4.5'
make[2]: ***
[/openwrt/trunk/build_dir/target-i386_uClibc-0.9.30.1/memcached-1.4.5/.built]
Error 2
make[2]: Leaving directory `/openwrt/packages/net/memcached'
make[1]: *** [package/feeds/packages/memcached/compile] Error 2
make[1]: Leaving directory `/openwrt/trunk'
make: *** [package/memcached/compile] Error 2
-
Also the checks for Cross-Compile are wrong. I still get messages like
--
checking for Sun cc in use... configure: error: in
`/openwrt/trunk/build_dir/target-i386_uClibc-0.9.30.1/memcached-1.4.5':
--
Seem to me, you only want to support Sun? Now Oracle ?
To sponsor you a buildbot for this issue is nothing like crap. But please
correct me.
Original comment by h...@terminal-consulting.de
on 8 Aug 2010 at 10:03
memcached needs a compiler that supports a standard at least 11 years old. The
one you're using does not appear to, or is not configured to do so.
I don't suspect many people are going to be going out of their way to create a
cross-compilation build system for you. We'd be happy to take your
well-written contribution to get things building for your system.
Original comment by dsalli...@gmail.com
on 9 Aug 2010 at 1:08
The problem in configure was that it tried to use try_run_ifelese, and that
don't work for cross compilation. Update your compiler and try again.
fixed in 2176290048d6a9a7292020256400b4cb9d498c7b
Original comment by trond.no...@gmail.com
on 11 Nov 2010 at 4:15
Thank you really much. I can confirm that the issue is fixed.
Original comment by h...@terminal-consulting.de
on 14 Nov 2010 at 10:09
Original issue reported on code.google.com by
h...@terminal-consulting.de
on 25 Feb 2010 at 5:12