HP3000-L Archives

April 1999, Week 3

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:
Steve Donnelly <[log in to unmask]>
Reply To:
Date:
Mon, 19 Apr 1999 14:02:14 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (59 lines)
Thanks for the great suggestions from Mark K, Mark B, and Lars.  The tricks for
porting to MPE Posix were very helpful.  I'm also grateful to Mark K for sending
the /usr/contrib/include files.  The "dotme" scripts by Lars are a neat trick
also.

I tried all the suggestions, i.e. file security, missing or incorrect include
files, unset shell environment variables, but the situation never improved.  The
compile continues to fail at the ap_signal.c module.

For those who would like to port Apache 1.3.6 to MPE6.0, there is a problem.
The apache source module "src/ap/ap_signal.c" declares the 'act' and 'oact'
variables using a struct named 'sigaction'.  'sigaction' is not defined anywhere
on the HP3000 (missing from /usr/include/* and /usr/contrib/include/*).  I
compared this to HPUX and found that 'sigaction' is defined in
/usr/include/sys/signal.h.

I'm experimenting with a workaround right now and hope to have good news RSN!

Steve Donnelly
Expeditors International -- IS Support






>My quick and dirty workaround was to copy /usr/include/signal.h to
>/usr/include/sys/signal.h.  This corrected the "No such file or directory"
>error.

That's quick, but real dirty. Please remember to remove it.

The best way is to obtain the /usr/contrib/include hierarchy which will
include many of the missing items one needs to be able to port to MPE.
Steve, if you don't have the FREEWARE tape, let me know and I'll send
this to you directly under separate cover.

In the near future (RSN and all that), this will be publically available
on the net under CVS for anonymous access (I just gotta get the web pages
done and approved :-)).

>gcc -c  -I../os/unix -I../include -D_POSIX_SOURCE -D_SOCKET_SOURCE
-I/IX/PUB/mpe
>/inc  -DMPE -D_POSIX_SOURCE -D_SOCKET_SOURCE -DUSE_HSREGEX `../apaci`
ap_signal.

Here is a group of standard variables I always define for my ports:

export CFLAGS="-I/usr/contrib/include -DSYSV -D_POSIX_SOURCE -D_SOCKET_SOURCE \
  -D_MPEIX_SOURCE -D_MPEXL_SOURCE"
export CXXFLAGS="$CFLAGS"
export CPPFLAGS="$CFLAGS"
export LDFLAGS="-lsocket -lcurses -lsvipc"
export CC=gcc
export CPP="gcc -E"

The CFLAGS and LDFLAGS are pretty much essential before running a configure
script.

ATOM RSS1 RSS2