- From: Calin A. Culianu <calin_at_ajvar.org>
- Date: Mon, 27 Jan 2003 13:12:08 -0500 (EST)
Hehe. The preprocessor sucks huh? :) Strangely enough I think I had some problems with my gcc setup. It was a hacked together gcc that I didn't build from scratch but rather copied off some install cd's. I dunno why that makes a difference (maybe was misconfigured?) but after rebuilding gcc 3.2 from stratch the problem went away. -Calin On Mon, 27 Jan 2003, Frank Mori Hess wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Monday 27 January 2003 10:16 am, Calin A. Culianu wrote: > > > > So I ran the preprocessor (cpp) on the .c file using basically the above > > command-line and I get _blank_ preprocessor output! Well not totally > > blank, but just lines line: > > > > # 1 "<built-in>" > > # 1 "<command line>" > > # blah blah some other preprocessor marker for the compiler.. blah blah > > # etc... > > > > My guess would be it is the line > > #define DEBUG(x) x > > in the pcl driver and the fact that the c preprocessor generally sucks. > > - -- > Frank > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE+NW8j5vihyNWuA4URAtAmAJ9NZeG90q5r0JkFVtWTAFtZzzl2LwCfdRht > Fi3DWyANVhwDnXE7IOgtiUA= > =6eww > -----END PGP SIGNATURE----- >
Received on 2003-01-27Z18:12:08