Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!cernvax!chx400!bernina!karrer
From: karrer@bernina.ethz.ch (Andreas Karrer)
Newsgroups: comp.lang.perl
Subject: perl4.010 -P (cpp flag) is busted
Summary: cppstdin wrapper stays in source directory
Keywords: cpp wrapper
Message-ID: <1991Jun11.102941.9804@bernina.ethz.ch>
Date: 11 Jun 91 10:29:41 GMT
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Lines: 17

It seems that on SunOS/Ultrix/ConvexOS and probably others, perl4.010 -P
will only work if your perl source is in exactly the same spot as it
was when perl was installed.

This is because Configure decides (after cc -E fails) to use the following
script to invoke the C preprocessor:

	cat >.$$.c; cc -E ${1+"$@"} .$$.c; rm .$$.c

Unfortunately, the cppstdin script is not installed into $privlib; and
the pathname <perl-source-directory>/cppstdin is glued into the perl
binary. Im my case, this happens to be an automounted directory from
a machine which is 3 routers away; hardly a relyable path...

+-----------
  Andi Karrer, Communication Systems, ETH Zuerich, Switzerland
  karrer@bernina.ethz.ch                 - terible simplifieur