jk@cs.man.ac.uk (John Kewley ICL) (10/30/90)
Two questions:
1. My versions of lex++ and yacc++ segmentation fault when run. Is this
common to others as well?
2. The headers provided with Sun C++ 2.0 contain comments that state:
"THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T"
Is this the same elsewhere.
I use SunOS 4.0.3, Sun 3/50.
Thanks, in advance,
--
J.K.
John M. Kewley, ICL, Wenlock Way, West Gorton, Manchester. M12 5DR
Tel: (+44) 61 223 1301 X2138 Email: jk@r6.cs.man.ac.uk / jk@nw.stl.stc.co.ukjhc@irwin.uucp (James H. Coombs) (11/01/90)
In article <1844@m1.cs.man.ac.uk> jk@cs.man.ac.uk (John Kewley ICL) writes: >Two questions: >1. My versions of lex++ and yacc++ segmentation fault when run. I have the same problem. In addition, CC/sun4/dbx always responds with the error: dbx: fatal error: I/O error rpcgen works but has not been well integrated into c++. Also, some of the function prototypes in rpc/xdr.h are simply wrong (e.g., xdr_u_short). >2. The headers provided with Sun C++ 2.0 contain comments that state: > "THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T" Yes. >I use SunOS 4.0.3, Sun 3/50. I use SunOS 4.1. I have worked with CC on a 4/110, a 4/280, and a Sparc. We tried reinstalling from the tape several times, but the result is the same. Has anyone solved these problems? --Jim
alan@cogswell.Jpl.Nasa.Gov (Alan S. Mazer) (11/01/90)
In article <54964@brunix.UUCP>, jhc@irwin.uucp (James H. Coombs) writes: | In article <1844@m1.cs.man.ac.uk> jk@cs.man.ac.uk (John Kewley ICL) writes: | >Two questions: | >1. My versions of lex++ and yacc++ segmentation fault when run. | | I have the same problem. In addition, CC/sun4/dbx always responds with | the error: | | dbx: fatal error: I/O error I'm running 4.1 on a SPARCstation and lex++, yacc++ and dbx all work fine for me. If someone wants my code, send mail. It's pretty short. Perhaps you don't have the latest stuff? -- -- Alan # My aptitude test in high school suggested that ..!ames!elroy!alan # I should become a forest ranger. Take my alan@elroy.jpl.nasa.gov # opinions on computers with a grain of salt.
rdr@mdavcr.UUCP (Randolph Roesler) (11/01/90)
At first, Sun's lex++ and yacc++ worked fine. Then, one day it started to core dump as has been described. The problem was that the sys-admin had "fixed" the standard .login and the new PATH did not have /usr/CC/sun4 (in my case) before the standard bin directories. Here is my current environment. Lex++ and Yacc++ work fine. CCROOTDIR=/usr/CC/sun4 MANPATH=/usr/share/man:/usr/local/man:/usr/CC/man:/usr/lang/man PATH=.:/home/mdavcr/r+d/rdr/bin:/usr/CC:/usr/CC/sun4:/usr/lang: /usr/ucb:/usr/bin/X11.R4:/usr/bin:/usr/local/bin:/usr/hosts -- Randy Roesler MacDonald Dettwiler & Assc. Ph. 604-278-3411 Fax. 604-278-2936 13800 Commerce Parkway, email ...!uunet!van-bc!mdavcr!rdr Richmond BC Canada rdr%mda.ca@wimsey.bc.ca or rdr@mda.ca V6V 2J3
truett@cup.portal.com (Truett Lee Smith) (11/01/90)
If lex++ and yacc++ are dumping core before they do anything, then you probably don't have the environment variable CCROOTDIR set. Unfortunately, the documentation is in error regarding the need to set it, saying that the program will look in the current directory for the pro-forma files used to build the C++ source output. It has to be set, usually to something like /usr/lib/CC. Truett Smith, Sunnyvale, CA truett@cup.portal.com OR truett@tdd.sj.nec.com