kerberos, imake, & rs/6000?

Thread View: comp.protocols.kerberos

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Jeff Hayward Thu, 17 Dec 1992 19:24

#846

Author: Jeff Hayward
Date: Thu, 17 Dec 1992 19:24

12 lines
930 bytes

I'm sure this is some sort of rookie problem, but I'm not getting
anywhere with it.  I'm trying to build Kerberos V4 pl 10 on an IBM
rs/6000 running AIX 3.2.  The C pre-processor is complaining when
imake hands it a line like /**/# <anything>, and the makefiles
generated get errors from make complaining about missing separators.

Surely there's something simple I'm missing.  Can someone give me a
clue?  Thanks.
--
Jeff Hayward
The University of Texas System			+1 512 471 2432
Office of Telecommunication Services		j.hayward@utexas.edu

Re: kerberos, imake, & rs/6000?

#847

Author: Richard Basch
Date: Sun, 20 Dec 1992 18:59

8 lines
746 bytes

The simple answer is to do:

	setenv IMAKECPP /usr/lpp/X11/Xamples/util/cpp/cpp

The standard cpp doesn't work well with imake on a RISC/6000.

-Richard Basch
MIT IS/Athena Development

Re: kerberos, imake, & rs/6000?

#848

Author: David Joyner
Date: Sun, 20 Dec 1992 19:35

33 lines
1912 bytes

Jeff Hayward (jah@mojo.ots.utexas.edu) wrote:
: I'm sure this is some sort of rookie problem, but I'm not getting
: anywhere with it.  I'm trying to build Kerberos V4 pl 10 on an IBM
: rs/6000 running AIX 3.2.  The C pre-processor is complaining when
: imake hands it a line like /**/# <anything>, and the makefiles
: generated get errors from make complaining about missing separators.
: 
: Surely there's something simple I'm missing.  Can someone give me a
: clue?  Thanks.
: 

The C-preprocessor is probably barfing out on the # after the
comments.  I hacked my build to use a previously installed imake that
didn't have this problem.  There is probably another (better)
solution.  If you stick with the supplied imake, make sure
"REDUCED_TO_ASCII_SPACE" gets defined.

You will also run into other problems with the C compiler.  You would
do well to use "bsdcc" as outlined in /usr/lpp/bos/bsdport.

There are also some runtime problems under AIX 3.2.  The only ones I
can remember right now are:

	. the infamous malloc(0) returns NULL
	. file locking is attempted on files that were not
	  opened O_RDWR.

I could probably kludge together my changes if you are interested.

--
David Joyner (nsysdbj@acs.ncsu.edu)
Unix Systems Programmer                            | Phone: (919) 515-2794  |
NCSU Administrative Computing Services             | FAX:   (919) 515-3787  |

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads