Hi There,
I have a cron script that returns the error:
syntax error on line 1, teletype
Has any one seen this, know what it is, or know's how to get rid of it?
Thanks,
Jeremy. (1 Reply)
I compiled C program under SUN OS sparcv9 ...I had a problem related to SIGBUS which has been resolved by adding an option to the CC compiler which is memory alignement option ..-memalign=1i as I remmber ...after running the program I got the below error please let me KNow more details what should... (2 Replies)
Hi all,
I've a problem with oracle10.1.0.2 installation on Solaris 10 (I already know this is possible) but when I run "./runInstaller" command from CD I read "syntax error at line 2" followed by several lines (ex. \200\201\203\206...ect).
Can you help me please? It is very urgent! (19 Replies)
hi can anyone pls look into this....shell script...
Pls find the error below:
> sh -n tmp
tmp: syntax error at line 28: `(' unexpected
isql -Usa -S$1 -P`grep $1 dbpassword|cut -d ":" -f3` -w2000 -b<<!
set nocount on
declare @i int
declare @dbname char(6)
declare @tmp int
if... (10 Replies)
hi ,
while running this script i am getting below error:
Syntax error at line 11 : `for' is not matched.
here is program:
#! /bin/ksh
sqlplus -s << !+!
user/password
update GR_SUB_SCRIPT_PC set act_del_ind='0';
commit;
exit;
!+!
cd /home/salunke/pvcsfiles/source_files
for i in... (5 Replies)
Help please! :confused:
I have the following error with the following file and the emails are not arriving to the email, any idea please?
ERROR: ./launch_full_backup.sh: Syntax error at line 28 : `else' is not expected.
FECHA=`date +%d%m%y%H%M`... (2 Replies)
Hi,
I am trying to execute the above attached script. and i am getting the error as syntax error at line 8: `<<' is not matched.
While i am trying to run that particular line (cat <<EOF > /tmp/query.sql) independently in the prompt it is running successfully without any error.
I am running... (2 Replies)
Hi All
I am quite new to Unix. Following is a shell script that i have written and getting the subject mentioned error.
#!/bin/ksh
#-------------------------------------------------------------------------
# File: ang_stdnld.ksh
#
# Desc: UNIX shell script to extract Store information.... (3 Replies)
Hi,
I am getting an wired error.... the script is running fine when i run it manually... but the same when i try to run in nohup mode, i am getting error
if
Error:
syntax error at line 24: `(' unexpected
The above if is the 24th line!!! I dont understand the error... (4 Replies)
I have the following piece and getting
make
-----------------------------------
getvel
./getvel_main.cpp
./getvel_main.cpp: 1: ./getvel_main.cpp: //: Permission denied
./getvel_main.cpp: 2: ./getvel_main.cpp: //: Permission denied
./getvel_main.cpp: 3: ./getvel_main.cpp: //:... (2 Replies)
Discussion started by: kristinu
2 Replies
LEARN ABOUT CENTOS
extutils::makemaker::tutorial
ExtUtils::MakeMaker::Tutorial(3) User Contributed Perl Documentation ExtUtils::MakeMaker::Tutorial(3)NAME
ExtUtils::MakeMaker::Tutorial - Writing a module with MakeMaker
SYNOPSIS
use ExtUtils::MakeMaker;
WriteMakefile(
NAME => 'Your::Module',
VERSION_FROM => 'lib/Your/Module.pm'
);
DESCRIPTION
This is a short tutorial on writing a simple module with MakeMaker. It's really not that hard.
The Mantra
MakeMaker modules are installed using this simple mantra
perl Makefile.PL
make
make test
make install
There are lots more commands and options, but the above will do it.
The Layout
The basic files in a module look something like this.
Makefile.PL
MANIFEST
lib/Your/Module.pm
That's all that's strictly necessary. There's additional files you might want:
lib/Your/Other/Module.pm
t/some_test.t
t/some_other_test.t
Changes
README
INSTALL
MANIFEST.SKIP
bin/some_program
Makefile.PL
When you run Makefile.PL, it makes a Makefile. That's the whole point of MakeMaker. The Makefile.PL is a simple program which loads
ExtUtils::MakeMaker and runs the WriteMakefile() function to generate a Makefile.
Here's an example of what you need for a simple module:
use ExtUtils::MakeMaker;
WriteMakefile(
NAME => 'Your::Module',
VERSION_FROM => 'lib/Your/Module.pm'
);
NAME is the top-level namespace of your module. VERSION_FROM is the file which contains the $VERSION variable for the entire
distribution. Typically this is the same as your top-level module.
MANIFEST
A simple listing of all the files in your distribution.
Makefile.PL
MANIFEST
lib/Your/Module.pm
File paths in a MANIFEST always use Unix conventions (ie. /) even if you're not on Unix.
You can write this by hand or generate it with 'make manifest'.
See ExtUtils::Manifest for more details.
lib/
This is the directory where the .pm and .pod files you wish to have installed go. They are laid out according to namespace. So
Foo::Bar is lib/Foo/Bar.pm.
t/ Tests for your modules go here. Each test filename ends with a .t. So t/foo.t/ 'make test' will run these tests. The directory is
flat, you cannot, for example, have t/foo/bar.t run by 'make test'.
Tests are run from the top level of your distribution. So inside a test you would refer to ./lib to enter the lib directory, for
example.
Changes
A log of changes you've made to this module. The layout is free-form. Here's an example:
1.01 Fri Apr 11 00:21:25 PDT 2003
- thing() does some stuff now
- fixed the wiggy bug in withit()
1.00 Mon Apr 7 00:57:15 PDT 2003
- "Rain of Frogs" now supported
README
A short description of your module, what it does, why someone would use it and its limitations. CPAN automatically pulls your README
file out of the archive and makes it available to CPAN users, it is the first thing they will read to decide if your module is right
for them.
INSTALL
Instructions on how to install your module along with any dependencies. Suggested information to include here:
any extra modules required for use
the minimum version of Perl required
if only works on certain operating systems
MANIFEST.SKIP
A file full of regular expressions to exclude when using 'make manifest' to generate the MANIFEST. These regular expressions are
checked against each file path found in the distribution (so you're matching against "t/foo.t" not "foo.t").
Here's a sample:
~$ # ignore emacs and vim backup files
.bak$ # ignore manual backups
# # ignore CVS old revision files and emacs temp files
Since # can be used for comments, # must be escaped.
MakeMaker comes with a default MANIFEST.SKIP to avoid things like version control directories and backup files. Specifying your own
will override this default.
bin/
SEE ALSO
perlmodstyle gives stylistic help writing a module.
perlnewmod gives more information about how to write a module.
There are modules to help you through the process of writing a module: ExtUtils::ModuleMaker, Module::Install, PAR
perl v5.16.3 2013-06-14 ExtUtils::MakeMaker::Tutorial(3)