10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
Hello,
I'm trying to install ansifilter which is a program that translates ansi text to HTML.
The idea is to install it on AIX 7.1 but is failing. All de appropriate gcc libraries and requirements for this software were installed successfully, but when I do the gmake I get the following... (4 Replies)
Discussion started by: bazajav
4 Replies
2. Programming
Hi,
I have a program which collects performance data from AIX. It works fine on older releases (< 5.3) but I fail to get data from /proc.
I would really appreciate it if someone could compile (using ANSI compat C compiler), run the program (for 30-40 minutes) on AIX 6.1 and send me the... (2 Replies)
Discussion started by: StuBob
2 Replies
3. UNIX for Advanced & Expert Users
Hi Guys,
I wonder I had have a look to the cc compile options but I could be missing one but basically I'm compliling a c program where I will storing a command to connect to a database and also userid and password. The issue is that after the module is generated using a command like strings I... (14 Replies)
Discussion started by: arizah
14 Replies
4. Programming
Can anyone tell me how to compile a c programs on SunSolaris OS 5.1 Version as gcc and cc are not working
Thanks!!!! (4 Replies)
Discussion started by: shivu
4 Replies
5. Solaris
Hi,
wcslen(), strlen() returns size_t.
On 64-bit platform i want to use int like
str length is 10.
int len = wcslen(str);
On 64-bit what should I need to do if i wants the length in int. Because getting error as "Conversion of 64 bit type value to "int" causes truncation".
if i... (17 Replies)
Discussion started by: amit_27
17 Replies
6. Programming
I am trying to compile a c program on AIX 5.3L 64-bit unix.
I have used this program in the past and it works.
Does anybody know what this error means?
/usr/local/bin> gcc get_epoch_secs.c get_epoch_secs
gcc: get_epoch_secs: No such file or directory
get_epoch_secs.c: In function... (8 Replies)
Discussion started by: djehresmann
8 Replies
7. BSD
Hi ,
I have freeBSD installed. I need to compile a c program which has embedded informix sql statement in it.
Can you please help me to to do the same. I need to know what I should I do to make BSD compatable to compile the c program ?
Thanks in advance
Jisha (3 Replies)
Discussion started by: jisha
3 Replies
8. Programming
how can i do static compilation in cc and -lldap
i have system defined and user defined header file.
Can any one suggest any site where from i can get some information about static and dynamic compilation.
Thankx (1 Reply)
Discussion started by: bhakti
1 Replies
9. Programming
Hi all,
Yeasterday I try to compile c program by using cygwin. I just find an errors the fist one is concerinig about the end of the line.
To summit my Assignment which is the day after tommorow I have to compile my c program by using just gcc.
If any one know what do I have to... (5 Replies)
Discussion started by: Bell
5 Replies
10. Programming
how do i go about compiling a simple hello world script in mandrake linux? this is something i have had no luck in finding on the main site, please help?
thank you (2 Replies)
Discussion started by: CmpKillr
2 Replies
LUAC(1) General Commands Manual LUAC(1)
NAME
luac - Lua compiler
SYNOPSIS
luac [ options ] [ filenames ]
DESCRIPTION
luac is the Lua compiler. It translates programs written in the Lua programming language into binary files that can be later loaded and
executed.
The main advantages of precompiling chunks are: faster loading, protecting source code from accidental user changes, and off-line syntax
checking.
Pre-compiling does not imply faster execution because in Lua chunks are always compiled into bytecodes before being executed. luac simply
allows those bytecodes to be saved in a file for later execution.
Pre-compiled chunks are not necessarily smaller than the corresponding source. The main goal in pre-compiling is faster loading.
The binary files created by luac are portable only among architectures with the same word size and byte order.
luac produces a single output file containing the bytecodes for all source files given. By default, the output file is named luac.out, but
you can change this with the -o option.
In the command line, you can mix text files containing Lua source and binary files containing precompiled chunks. This is useful to com-
bine several precompiled chunks, even from different (but compatible) platforms, into a single precompiled chunk.
You can use '-' to indicate the standard input as a source file and '--' to signal the end of options (that is, all remaining arguments
will be treated as files even if they start with '-').
The internal format of the binary files produced by luac is likely to change when a new version of Lua is released. So, save the source
files of all Lua programs that you precompile.
OPTIONS
Options must be separate.
-l produce a listing of the compiled bytecode for Lua's virtual machine. Listing bytecodes is useful to learn about Lua's virtual
machine. If no files are given, then luac loads luac.out and lists its contents.
-o file
output to file, instead of the default luac.out. (You can use '-' for standard output, but not on platforms that open standard out-
put in text mode.) The output file may be a source file because all files are loaded before the output file is written. Be careful
not to overwrite precious files.
-p load files but do not generate any output file. Used mainly for syntax checking and for testing precompiled chunks: corrupted files
will probably generate errors when loaded. Lua always performs a thorough integrity test on precompiled chunks. Bytecode that
passes this test is completely safe, in the sense that it will not break the interpreter. However, there is no guarantee that such
code does anything sensible. (None can be given, because the halting problem is unsolvable.) If no files are given, then luac
loads luac.out and tests its contents. No messages are displayed if the file passes the integrity test.
-s strip debug information before writing the output file. This saves some space in very large chunks, but if errors occur when run-
ning a stripped chunk, then the error messages may not contain the full information they usually do. For instance, line numbers and
names of local variables are lost.
-v show version information.
FILES
luac.out default output file
SEE ALSO
lua(1)
http://www.lua.org/
DIAGNOSTICS
Error messages should be self explanatory.
AUTHORS
L. H. de Figueiredo, R. Ierusalimschy and W. Celes
$Date: 2006/01/06 16:03:34 $ LUAC(1)