>> I was not aware openwrt lua was heavily patched. I am curious as to
>> what it will take to move forward to lua 5.2?
Since the Lua authors decided to rework the complete environment
handling (getfenv, setfenv, ...) in 5.2, LuCI will completely break.
It is a considerable effort to rework that
On Fri, Jan 13, 2012 at 8:54 PM, Jo-Philipp Wich wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> just seen your message on the Lua list - be aware that OpenWrt Lua is
> heavily patched, so maybe try again with some of the Lua patches removed
> and see if the issue persists.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
just seen your message on the Lua list - be aware that OpenWrt Lua is
heavily patched, so maybe try again with some of the Lua patches removed
and see if the issue persists.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
C
On Fri, Jan 13, 2012 at 12:50 PM, Jo-Philipp Wich wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> You can suppress this note by ensuring the compiler is called with
> "-fhonour-copts". If the configure script does not respect the CFLAGS
> variable, you can try to redefine CC as
> CC=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You can suppress this note by ensuring the compiler is called with
"-fhonour-copts". If the configure script does not respect the CFLAGS
variable, you can try to redefine CC as
CC="$(TARGET_CC) -fhonour-cflags".
hth,
~ Jow
-BEGIN PGP SIGNATURE--
The previous test is failing because the mutex_attr stubs are not
present in libc. The work around is to add --enable-pthread=yes on
./configure.
That triggers another failure; the configure test is looking for a
clean stderr. The openwrt compiler is producing this warning: cc1:
note: someone does
I can't figure out why this configure test is failing for
`pthread_mutexattr_init' but it is passing for 'pthread_mutex_init'.
Any ideas?
configure:33721: arm-openwrt-linux-uclibcgnueabi-gcc -o conftest
-D_REENTRANT
-I/home/apps/openwrt/trunk/staging_dir/target-arm_v5te_uClibc-0.9.32_eabi/usr/inc
