05-10-2006
nmake is Microsoft's win32 make tool, yes? You might notice this is a UNIX forum. UNIX is not windows.
If I had to guess, I'd say the problem might be in other object files, not that file's.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a doubt with an error message, and i want to be sure if this is a normal situation or not.
Situation: I was formating and installing a SCSI 36Gb HD with UNIX SCO 5.05, the problem happens when is making the division and filesystem on disk 1, and the message error is "Exit value 139... (1 Reply)
Discussion started by: jav_v
1 Replies
2. Programming
dear all ,
iam trying to compile a progam using gcc compiler on a sun 280 R machine running solaris 9 .
iam getting an error in the last step when the compiler tries to link the objects , although the compiler executes some applicarions that contains no objects smoothly,
the error that... (1 Reply)
Discussion started by: ppass
1 Replies
3. UNIX for Advanced & Expert Users
Hi ,
attempting to purify code on the link line generates a fatal error
like this
#ERROR: (fatal) Cannot find libtest.so in the search path .
command line:
-------------
purify -show-directory=yes -always-use-cache-dir -cache-dir=/ppic/users/avadhani/sgi/pure /usr/bin/CC -n32 -mips3... (2 Replies)
Discussion started by: avadhani
2 Replies
4. Shell Programming and Scripting
Hi ,
I a stuck with this problem. I am trying to execute this script1 on SERVER 1 from SERVER 2 using script2
script1 on SERVER 1
#!/usr/bin/ksh
/opt/perf/bin/glance -f -adviser_only -iterations 2 -maxpages 2 > /home/user/scripts/glance.op
cpuval1=`grep ^CPU... (4 Replies)
Discussion started by: newbie07
4 Replies
5. Programming
i am trying to compile my program using a makefile and i keep getting this message:
Undefined first referenced
symbol in file
main
/usr/local/lib/gcc-lib/sparc-sun-solaris2.9/3.3/crt1.o
ld: fatal: Symbol referencing errors. No output written to prog5
collect2: ld returned 1 exit status
***... (2 Replies)
Discussion started by: betterdayz
2 Replies
6. AIX
Background
-------------
Os: IBM AIXL 5.1 (Unix)
Problem
-------------
I run the dbx in csh as follows
% dbx mainprog
-- The following is the systemm replay
Type 'help' for help.
reading symbolic information ...warning: stab entry unrecognized: name ,type 45, class a8, value 0'
... (1 Reply)
Discussion started by: skfn1203
1 Replies
7. Solaris
Hello,
I wonder if anyone has a clue what could be wrong.
I get the following error on SUN Netra-T4 server when some applications try to start (e.g. slpd) also even if I try commands such as "jar" I get the same error:
ld.so.1: /usr/java1.2/jre/bin/sparc/native_threads/java: fatal:... (3 Replies)
Discussion started by: Juha
3 Replies
8. UNIX for Dummies Questions & Answers
Hi all
I'm trying to install sudo. When I first ran the sudo configure script it errored saying that I didn't have a C compiler. I have since installed the GCC 3.4.6 package for sol8 from sun freeware.
Doing that resolved the no C complier found error. I was then getting an error saying... (1 Reply)
Discussion started by: Donkey25
1 Replies
9. Linux
Hi guys,
i am using the below command to send mail
mail -s "HI" abcd@how.com < temp_mail.txt
I am getting the below error
send-mail: fatal: bad string length 0 < 1: myorigin =
My os version is as
Linux
Help me with ur suggestion guys thank u. (3 Replies)
Discussion started by: mohanalakshmi
3 Replies
10. What is on Your Mind?
Today, I noticed some errors in our SSL cert renewal log files, mostly related to domains where the IP address had changed. Concerned about this, rebuilt out SSL cert, which normally goes well without a hiccup.
However, for today, for some reason which I cannot explain, there was a PHP error... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT MOJAVE
vmsish
vmsish(3pm) Perl Programmers Reference Guide vmsish(3pm)
NAME
vmsish - Perl pragma to control VMS-specific language features
SYNOPSIS
use vmsish;
use vmsish 'status'; # or '$?'
use vmsish 'exit';
use vmsish 'time';
use vmsish 'hushed';
no vmsish 'hushed';
vmsish::hushed($hush);
use vmsish;
no vmsish 'time';
DESCRIPTION
If no import list is supplied, all possible VMS-specific features are assumed. Currently, there are four VMS-specific features available:
'status' (a.k.a '$?'), 'exit', 'time' and 'hushed'.
If you're not running VMS, this module does nothing.
"vmsish status"
This makes $? and "system" return the native VMS exit status instead of emulating the POSIX exit status.
"vmsish exit"
This makes "exit 1" produce a successful exit (with status SS$_NORMAL), instead of emulating UNIX exit(), which considers "exit 1" to
indicate an error. As with the CRTL's exit() function, "exit 0" is also mapped to an exit status of SS$_NORMAL, and any other
argument to exit() is used directly as Perl's exit status.
"vmsish time"
This makes all times relative to the local time zone, instead of the default of Universal Time (a.k.a Greenwich Mean Time, or GMT).
"vmsish hushed"
This suppresses printing of VMS status messages to SYS$OUTPUT and SYS$ERROR if Perl terminates with an error status, and allows
programs that are expecting "unix-style" Perl to avoid having to parse VMS error messages. It does not suppress any messages from
Perl itself, just the messages generated by DCL after Perl exits. The DCL symbol $STATUS will still have the termination status, but
with a high-order bit set:
EXAMPLE:
$ perl -e"exit 44;" Non-hushed error exit
%SYSTEM-F-ABORT, abort DCL message
$ show sym $STATUS
$STATUS == "%X0000002C"
$ perl -e"use vmsish qw(hushed); exit 44;" Hushed error exit
$ show sym $STATUS
$STATUS == "%X1000002C"
The 'hushed' flag has a global scope during compilation: the exit() or die() commands that are compiled after 'vmsish hushed' will be
hushed when they are executed. Doing a "no vmsish 'hushed'" turns off the hushed flag.
The status of the hushed flag also affects output of VMS error messages from compilation errors. Again, you still get the Perl
error message (and the code in $STATUS)
EXAMPLE:
use vmsish 'hushed'; # turn on hushed flag
use Carp; # Carp compiled hushed
exit 44; # will be hushed
croak('I die'); # will be hushed
no vmsish 'hushed'; # turn off hushed flag
exit 44; # will not be hushed
croak('I die2'): # WILL be hushed, croak was compiled hushed
You can also control the 'hushed' flag at run-time, using the built-in routine vmsish::hushed(). Without argument, it returns the
hushed status. Since vmsish::hushed is built-in, you do not need to "use vmsish" to call it.
EXAMPLE:
if ($quiet_exit) {
vmsish::hushed(1);
}
print "Sssshhhh...I'm hushed...
" if vmsish::hushed();
exit 44;
Note that an exit() or die() that is compiled 'hushed' because of "use vmsish" is not un-hushed by calling vmsish::hushed(0) at
runtime.
The messages from error exits from inside the Perl core are generally more serious, and are not suppressed.
See "Perl Modules" in perlmod.
perl v5.18.2 2014-01-06 vmsish(3pm)