lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) (10/20/90)
In article <TML.90Oct19160331@hemuli.tik.vtt.fi> tml@tik.vtt.fi (Tor Lillqvist) writes:
: The header files on HP-UX are full of #ifdef __hp9000s800 type stuff.
: H2ph turns this into if (defined &__hp9000s800). Now the question is:
: How to get perl to predefine the appropriate subroutines? The h2ph
: generated files are rather useless now...
How about this?
sub __hp9000s800 { 1; }
Larrytml@tik.vtt.fi (Tor Lillqvist) (10/20/90)
The header files on HP-UX are full of #ifdef __hp9000s800 type stuff. H2ph turns this into if (defined &__hp9000s800). Now the question is: How to get perl to predefine the appropriate subroutines? The h2ph generated files are rather useless now... -- Tor Lillqvist, working, but not speaking, for the Technical Research Centre of Finland
tml@tik.vtt.fi (Tor Lillqvist) (10/22/90)
In article <10035@jpl-devvax.JPL.NASA.GOV> lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) writes:
How about this?
sub __hp9000s800 { 1; }
Sure... However, I was thinking of some way to automagically
predefine the same identifiers that the compiler predefines (sun, vax,
hpux, __hpux, etc).
It probably is too difficult to figure out the appropriate identifiers
automatically in the Configure script. Maybe the script simply should
suggest a set of identifiers based on its guesses about the system
type.
--
Tor Lillqvist,
working, but not speaking, for the Technical Research Centre of Finland