Displaying 4 results from an estimated 4 matches for "sysbol".
Did you mean:
symbol
2017 Aug 24
4
cmenu.c32 Symbol not found luaL_checklstring
...loads
ldlinux.e64. All is fine.
But when I want to use cmenu.c32 (with UI cmenu.c32 in the config file),
the loader downloads:
* cmenu.c32
* libmenu.c32
* libcom32.c32
* libutil.c32
Then syslinux reports: "unable to load cmenu.c32: symbol not found
luaL_checklstring".
This sysbol is defined in liblua.c32, that is present in the TFTP
directory. The TFTP log file however does not show any attempt to load
this library....
How to fix this???
syslinux.efi: 6.03 (EFI; 20151222)
Kind regards,
Reinier Kleipool
2017 Aug 28
0
cmenu.c32 Symbol not found luaL_checklstring
...But when I want to use cmenu.c32 (with UI cmenu.c32 in the config
> file), the loader downloads:
> * cmenu.c32
> * libmenu.c32
> * libcom32.c32
> * libutil.c32
> Then syslinux reports: "unable to load cmenu.c32: symbol not found
> luaL_checklstring".
> This sysbol is defined in liblua.c32, that is present in the TFTP
> directory. The TFTP log file however does not show any attempt to load
> this library....
cmenu.c32 is a Lua library, use it from a Lua script. See
simplemenu.lua in the Syslinux source tree for an example.
--
Feri
2015 Nov 04
2
Building R for AIX in 64-bit mode
...mbol: N01_kind
ld: 0711-224 WARNING: Duplicate symbol: LoadInitFile
ld: 0711-224 WARNING: Duplicate symbol: R_ReadItemDepth
ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_lock
ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_unlock
collect2: error: ld returned 8 exit status
The undefined sysbols can be resolved by adding -lpthread to the gcc
command (and can be automated by adding that to LDFLAGS I expect, but
imho - better if that gets caught by configure).
It then ends with:
RESOLVE: 6793 of 18448 symbols were kept.
RESOLVE: The return code is 4.
(ld): addgl /usr/lib/glink64.o
ADDGL...
2015 Oct 15
3
Building R for AIX in 64-bit mode
Hi.
Just wanted to let you know I am getting close to packaging R for AIX in
64.bit mode.
One comment - the libtool.m4 I see used is quite old. The one I have on my
system is 2.4.6, and what I see in R says:
I am hoping a new libtool will clean up most of the manual work now needed.
# Which release of libtool.m4 was used?
macro_version=2.2.6
macro_revision=1.3012
This may be all that is