home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!cs.utexas.edu!asuvax!chnews!tmcconne
- From: tmcconne@sedona.intel.com (Tom McConnell~)
- Newsgroups: gnu.gcc.help
- Subject: Re: gcc and X11-R5-P21 woes
- Date: 30 Dec 1992 07:25:04 GMT
- Organization: Intel Corporation
- Lines: 29
- Sender: tmcconne@sedona (Tom McConnell~)
- Distribution: gnu
- Message-ID: <1hrisgINN265@chnews.intel.com>
- References: <9212292152.AA07566@rtl.cygnus.com> <9212292213.AA25255@mole.gnu.ai.mit.edu>
- Reply-To: tmcconne@sedona.intel.com
- NNTP-Posting-Host: thunder.intel.com
- Originator: tmcconne@sedona
-
-
- In article <9212292213.AA25255@mole.gnu.ai.mit.edu>, rms@gnu.ai.mit.edu (Richard Stallman) writes:
- > Please try version 2.3.3. It may fix this bug.
- >
-
- Using gcc-2.3.3, SunOS-4.1.1, I modified the X11 source per
- ./gcc-2.3.3/README.X11. I had no problems at all with the build, including the
- shared libraries. The executables execute, so I am happy.
-
- I made no modifications for the "syslimits.h" / "sys/limits.h"
- problem, since I have never seen this problem. My understanding, and my
- experience, is that gcc-2.3.x builds <syslimits.h>, usually with just an
- "#include_next <limits.h>". At least that is what my <syslimits.h> file looks
- like.
-
- I did make one cosmetic change to ./mit/lib/Xt/Xtos.h, for the definition of
- "alloca()", but even without the change X11R5p21 built fine.
-
- As far as _I_ can tell, everything works fine. I checked the log file, and
- "cc" is never used, always "gcc", and I tested out the executables.
-
- Cheers,
-
- Tom McConnell
- --
- Tom McConnell | Internet: tmcconne@sedona.intel.com
- Intel, Corp. C3-91 | Phone: (602)-554-8229
- 5000 W. Chandler Blvd. | The opinions expressed are my own. No one in
- Chandler, AZ 85226 | their right mind would claim them.
-