songer@orchestra.ecn.purdue.edu (Christopher M Songer) (02/13/91)
Hi, I was installing patch the other evening. The configure program (which is suposed to configure the patch source for any flavor of UNIX) would not recognize /lib/cpp as the c preprocessor, even though it tried to use it. It turns out that the program was running the following test file to see if /lib/cpp was indeed the preprocessor: #define ABC abc #define XYZ xyz ABC.XYZ The expected final line is, of course: abc.xyz I tried it out and much to my suprise the result was: abc .xyz ^ :Note unsightly white space! :) I have made sure that all the white space was cut from the end of the #define lines and have tried this on both 1.0 and 2.0. The result remains the same. Certainly, extra white space is not going to be a problem for the compiler, but things other than cc use cpp. Does anyone know if this is a GNU thing which I can fix simply by getting the newest version of cpp? Or has cpp been messed with (I'd lay money on this one) by NeXT, and I'm outa luck to have a fully-up to-spec version until 2.1 or 3.0? As a side note -- I got burned with this install by the absence of a libc too. Is there a good reason not to set a symlink from libsys to libc? Thanks, Chris
lacsap@plethora.media.mit.edu (Pascal Chesnais) (02/13/91)
In article /lib/cpp bug. songer@orchestra.ecn.purdue.edu (Christopher M Songer) of : Purdue University Engineering Computer Network writes: Hi, I was installing patch the other evening. The configure program This keeps getting beaten to death here. What you are observing is NOT a bug with gnu cpp, GNU cpp is ANSI compliant. So you need to fix the configure script to account for the white space. pasc