public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: Oyvind Yrke <oyvind@stavanger.geoquest.slb.com>
Cc: egcs@cygnus.com
Subject: Re: egcs 1.0.2
Date: Wed, 01 Apr 1998 19:44:00 -0000	[thread overview]
Message-ID: <199804020050.QAA02812@rtl.cygnus.com> (raw)
In-Reply-To: <351FD0C9.21BD7E3E@stavanger.geoquest.slb.com>

	The includedir was added in an attempt to let the config command
	find my local tcl & tk installation (without any success it seems :-( )

EGCS doesn't know anything about tcl/tk, so this isn't going to do anything
useful anways.

Dejagnu uses tcl/expect, but using your local copy is probably not a good
idea.  We know it works with the libraries included in the dejagnu package.
We don't know if it works with your local versions of the libraries.

     * make -k check didn't run any testsuites in the gcc area, and
       the only part being tested seems to be libio.  Anyway, the test
       completes after 4 min on an Ultra-30 which tells me that not very
       much has been tested.  Do these tests require a full install of
       dejagnu?  configure in dejagnu ended up with
       "... no X based programs will be installed."

What kind of output did you actually get?  I can't help if I have no idea
what output you got.  There probably is something wrong, but I have no idea
what.

You can ignore the dejagnu configure warning.  `make check' does not invoke
any X based programs, so the fact that they aren't built is not a problem.

     * there are a few compiler warnings, both when building stage1 using
       native sun cc, and when building stage{N} using stage{N-1}.

You can ignore the warnings.

In general, it may not be possible to make the source code warning free for
all possible compilers for all configurations.

We deliberately added -Wall to the stage2/stage3 builds to help find bugs,
and we are slowly in the process of adding patches to eliminate the gcc
warnings.

     * although I provided a program-prefix to configure, the programs
       installed still have the standard names (gcc, g++ etc), I'd expected
       egcs-gcc, egcs-g++ etc.

Offhand, I don't know.  I haven't tried using this option.

     * rtti - is there any reason why typeinfo.h is not shipped with egcs?
       I noticed that typeinfo.h was part of libg++2.7.2, but not in 2.8.x!!

I don't know.

Jim

  parent reply	other threads:[~1998-04-01 19:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-30 16:18 Oyvind Yrke
1998-04-01 13:41 ` Jeffrey A Law
1998-04-01 19:44 ` Jim Wilson [this message]
1998-04-03 21:52   ` Joe Buck
1998-04-03 21:52 ` Andreas Schwab
     [not found] <3525297C.4A20D761@stavanger.geoquest.slb.com>
1998-04-03 21:52 ` Jim Wilson
  -- strict thread matches above, loose matches on Subject: below --
1998-03-19 20:46 Felix Morley Finch
1998-02-16 13:34 Daniel Egger
1998-02-16 14:21 ` H.J. Lu
1998-02-15  8:24 egcs cvs'd between 980214 8:00 and 9:13 UTC on m68k-next-nextstep3: Success Jeffrey A Law
1998-02-15  8:32 ` egcs 1.0.2 H.J. Lu
1998-02-15  8:33   ` Jeffrey A Law
1998-02-15  8:42     ` H.J. Lu
1998-02-15  8:46       ` Jeffrey A Law
1998-02-15  8:50         ` H.J. Lu
1998-02-15 12:18   ` Joe Buck
1998-02-15 14:04     ` H.J. Lu
1998-02-16  4:49       ` Bernd Schmidt
1998-02-16 10:34         ` H.J. Lu
1998-02-16 18:19           ` Bruno Haible

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=199804020050.QAA02812@rtl.cygnus.com \
    --to=wilson@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=oyvind@stavanger.geoquest.slb.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).