public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David J Chase <dchase@math.rice.edu>
To: egcs@cygnus.com
Subject: egcs installed
Date: Fri, 14 Aug 1998 16:55:00 -0000	[thread overview]
Message-ID: <199808141404.JAA19350@math.rice.edu> (raw)

Hi,
I just installed installed egcs 1.0.3a on two machines (this week).

sparc-sun-solaris2.6
(installed as user in $HOME/local/)

i586-pc-linux-gnulibc1
(installed as su in /usr/local/)

the only trouble I had was (as mentioned in the FAQ) a stray : in a LIB_PATH
and (more annoyying) the include directories (both c++ and gcc) were given
permissions of 700.  I didn't notice this on the sun (since I'm the user)
but I just checked it and it happened there too.  On the PC I had to go
and reset the permissions on those directories after I found the error.

It was minor, but could be easily corrected (I'd rather someone who is familiar
with the Makefiles do the correcting though :-) 

I did not run the test suite, but all of the programs I tried to compile with
it worked beautifully.  The only changes that were really nec. were a few header
changes (and occasionally fixing some non-standard C++).

In particular, I decided to install egcs instead of sticking with gcc-2.7.2.x
when I found a trivial exception example in Stroustroup 3rd Ed which I needed
to use (catching alloc errors) and found I could not.  It works fine now.

Thanks for putting this all together.

David 

++++++++++++++++++++++++++++++++++++
David J. Chase
Sr. Analyst, Columbia Energy 
dchase@columbiaenergy.com  
<dchase@math.rice.edu>
713-350-8340 (voice)-----713-621-5392 (fax)
1330 Post Oak Blvd., Houston, TX  77056
++++++++++++++++++++++++++++++++++++


             reply	other threads:[~1998-08-14 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-14 16:55 David J Chase [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-07-31 18:50 Michael Brandt
1998-07-30 15:09 Carlos Cassino
1998-05-21 10:23 R. S. de Araujo
1998-04-23 10:41 letschert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199808141404.JAA19350@math.rice.edu \
    --to=dchase@math.rice.edu \
    --cc=egcs@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).