I am currently using LPRng 3.8.15 with ifhp 3.5.10. The only configure
options I used were the prefixes. At one time, I had needed the option
describing the linker (I believe it is in the CHANGES file), but no
longer. This is HP 11.00 I am talking about.

I always download the source from LPRng.com and compile that.

Recently, on HP-UX 11.11 (11i), I compiled LPRng 3.8.20 (no ifhp -- this
is a test machine). I have had no trouble with it, and again, I only set
the prefix, nothing else.

---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  |  | Ryan Novosielski - Jr. UNIX Systems Admin
|$&| |__| |  | |__/ | \| _|  | [EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630

> Ryan,
>
>     Which version of LPRng and IFHP are you using ? what are the configure options
> ? Did you use the original downloaded source code for LPRng and IFHP?  I wonder
> what's going on with HPUX11.x.
>
>     Thanks
>
>     Jin
>
> Danial Howard wrote:
>
> > Ryan Novosielski wrote:
> > > I always use the HP-UX ANSI-C compilers for my HP-UX machines, and it
> > > works like a star. If you have access to the ANSI-C compilers
> > > (/opt/ansic/bin/cc), give them a whack.
> > >
> >
> > Thanks, Ryan. Yes, I do have the HP ANSI C compiler and used it to
> > compile LPRng and ifhp without the warnings received from gcc.
> >
> > So I have LPRng working on it's own. I also have ifhp working fine
> > separately. Now when I configure a print queue to use ifhp, the print
> > job just hangs. I think there is a problem in LPRng/ifhp on HP-UX
> > 11.00 and 11.11 that prevents one from passing jobs to the other. In
> > fact, I created a simple shell script filter and put that in the
> > printcap. Jobs to that queue hang too. So it's not ifhp. It's filters
> > in general. I can't quite pin it down.
> >
> > See another thread in the mailing list titled "HP-UX 11i, LPRng, and
> > ifhp". I see you've added a message to that thread. I'll try your
> > suggestion.
> >
> > If you have LPRng and ifhp working on HP-UX, what configure options
> > did you use and how was it built?
> >
> > I use this:
> >
> > ./configure --prefix=/opt/lprng --with-linker=/usr/bin/ld \
> >              CFLAGS=-Ae FILEUTIL=/opt/file/bin/file CC=cc
> >
> > and then GNU Make to build.
> >
> > --
> > Danial M. Howard
> > IT Systems Programmer, Computing and Communications
> > Idaho State University, Pocatello, Idaho, USA
> >
> > -----------------------------------------------------------------------------
> > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> > The address you post from MUST be your subscription address
> >
> > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> > or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
> > to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
> > with:                           | example:
> > subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
> > unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]
> >
> > If you have major problems,  send email to [EMAIL PROTECTED] with the word
> > LPRNGLIST in the SUBJECT line.
> > -----------------------------------------------------------------------------
>

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to