09-07-2001
That was it
Thanks for the reply. "./" did it.
Arthur P. Krebsbach
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi.Iam new to Linux.i got linux 7.0 pro and dont know how to run programs. I want a perl interputer and i know i installed one but how do i run it ??? Also how do i run a C or C++ editor ?and how do i run cron ? (3 Replies)
Discussion started by: perleo
3 Replies
2. Programming
I am confused about how to use a .exe file in unix along with a compiled C++ program. I've been using emacs and I compiled with g++, but I have no idea how that relates to use with a .exe. (1 Reply)
Discussion started by: adamsy
1 Replies
3. Shell Programming and Scripting
Hello All,
I have coded a C program which looks something like below... (program name: test.c)
#include<stdio.h>
main()
{
int dist,dm,dcm;
printf(" Enter the distance between 2 cities in KM : ");
scanf("%d",&dist);
dm=dist*1000;
dcm=dist*10;
printf("Distance between 2 cities in... (6 Replies)
Discussion started by: smarty86
6 Replies
4. Shell Programming and Scripting
Folks,
I'm really new to scripting and was wondering if you could help me out. I have the following script that I inherited:
#!/bin/bash
#
# Usage
# From the agent directory:
# ./run-any-agent AgentName
#
TAC_AGENT_HOME=`pwd`
LIB=${TAC_AGENT_HOME}/lib
CLASSPATH=.... (17 Replies)
Discussion started by: DTriniWay
17 Replies
5. UNIX for Dummies Questions & Answers
I am trying to make an application which works on unix to work on linux. I already tried copying the binary files and start it up but I am getting an error stating "Cannot execute binary file". Then I tried to recompile but i am getting an error whenever I tried to recompile. I am getting the... (1 Reply)
Discussion started by: khestoi
1 Replies
6. Homework & Coursework Questions
Long story short: I'm working inside of a Unix SSH under a bash shell. I have to code a C program that generates a random number. Then I have to call the compiled C program with a Perl program to run the C program 20 times and put all the generated random #s into a text file, then print that text... (1 Reply)
Discussion started by: jdkirby
1 Replies
7. Shell Programming and Scripting
Hi All,
How to run c# program using shell script ? (1 Reply)
Discussion started by: srikar.ch
1 Replies
8. Solaris
Hi,
We upgraded our servers from solaris 9 to 10. We recompiled all the Pro*C programs with the new oracle version as well. Oracle is 11g. We are facing core dump with the below error for certain executions. But when we are placing new statements between the error fucntion we get junk values to... (1 Reply)
Discussion started by: saroopkris85
1 Replies
9. Programming
I have put some yellow color codes and works well.
I call the funstion using
print_usage(stderr, 0);
I would like to know if there is any way, to store the ansi color codes in variables and then call them inside fprintf.
Or have a format followed by the strings I want to output.
... (5 Replies)
Discussion started by: kristinu
5 Replies
10. Red Hat
Will a program compiled in ubuntu 14.04 execute in Centos 7? That is to say a tarball or zip is downloaded from github and extracted, compiled, and make is all done in ubuntu 14.04, can I mv the program from ubuntu 14.04 to Centos 7, add it to path in Centos 7. And run it? Thank you :) (3 Replies)
Discussion started by: cmccabe
3 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: 2010/10/31 11:16:49 $ LUAC(1)