HP3000-L Archives

January 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Eric F. Richards" <[log in to unmask]>
Reply To:
Eric F. Richards
Date:
Thu, 13 Jan 2000 16:52:10 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (75 lines)
Bill Cadier <[log in to unmask]> wrote:
> Hello Eric,

> You can use the c89 compiler under the MPE/iX Shell to accomplish
> what you need. Thru the wonders of cut'n'paste I took your example
> and modified it slightly to read...

> #define _POSIX_SOURCE
  ^^^^^^^^^^^^^^^^^^^^^

That made my actual test code go through the compiler, but I still
get an unresolved on alarm.  I'm running MPE C.55.07.  Don't know the
C compiler version (that is, I don't know where to find the info.)

Commands used:

ccxl timers.c timers.o $null -Aa -g
link from=timers.o, xdbend.lib.sys;to=timers.bin; &
   rl=^oarls.lib;xl="oraclexl.pub.oracle6";cap=ia,ba,ph,mr,pm;privlev=2

(The superfluous trash is because this is from a canned script.)

> c89 -o alarm alarm.c

HPIX2> [EFRDEV.PUB]:run sh.hpbin.sys;info="-L"

########################################################################

               MPE/iX Shell and Utilities (A.50.02)
    COPYRIGHT (c) Hewlett-Packard Company 1992, All Rights Reserved.

########################################################################


HPIX2> [/EFRDEV/PUB]$c89 -o alarm alarm.c
c89: file '/etc/c89.ccg': Permission denied
HPIX2> [/EFRDEV/PUB]$

(I think I need to talk to the admins...)

> HPPXUDC.PUB.SYS is a user defined command file we provide that, when
> set provides you with an 'sh' command to hop into the shell. The
> long hand way is

> RUN SH.HPBIN.SYS;INFO="-L"

> which will do to get you there if you happen to lack this UDC file.

> Hope this helps

> Bill Cadier
> HP Commercial Systems Div.


It gets me further, but as with most of these things, it can't exist
in a vacuum.  We have an extensive product that builds using the standard
CLI, and the "native" environment is what the software builds in.

However, you may know the answer to this:  Our docs don't mention alarm()
as a valid function and explicitly state that signal() is put there for
ANSI compatibility and that the only way to actually raise a signal is
with an explicit call to raise().  Is that no longer true?  At what version
of MPE, compiler, or other product did this change?

Thanks much, you've been very helpful!

Eric


--
Eric F. Richards
[log in to unmask]
"The weird part is that I can feel productive even when I'm doomed."
 - Dilbert

ATOM RSS1 RSS2