gcc preprocessor and -traditional problem

Article View: comp.sys.next.bugs

Article #53

Back to comp.sys.next.bugs Previous Next

#53

From: Dave Hess
Date: Tue, 12 Jan 1993 00:20

19 lines
1154 bytes

I was trying to put together a package (detex 2.4) that needed to be compiled
with -traditional and gcc puked on some NeXT include files. gcc apparently
won't interpret the funky macros that NeXT uses in some of their #include
statements (for the architecture independent stuff) if the -traditional
switch is on.

This seems like a bug to me. Has anybody else hit this or have a workaround?
Are there #pragmas that will do the same thing for me? The program dies when
compiled with normal gcc.

Thanks.

Dave

--
David K. Hess
Graduate Assistant                     David-Hess@tamu.edu
Supercomputer Center                  Texas A&M University

Technical Details

Message-ID: <1it2rtINNk7i@tamsun.tamu.edu>

Path:

arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!tamsun.tamu.edu!tamsun.tamu.edu!news

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!tamsun.tamu.edu!tamsun.tamu.edu!news
From: d1h1883@sc.tamu.edu (Dave Hess)
Newsgroups: comp.sys.next.bugs
Subject: gcc preprocessor and -traditional problem
Date: 12 Jan 1993 00:20:13 GMT
Organization: Texas A&M University, College Station, TX
Lines: 19
Distribution: world
Message-ID: <1it2rtINNk7i@tamsun.tamu.edu>
Reply-To: David-Hess@tamu.edu
NNTP-Posting-Host: posaune.tamu.edu