public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: jbuck@synopsys.com (Joe Buck)
To: khan@xraylith.wisc.edu (Mumit Khan)
Cc: hjl@lucon.org, jbuck@synopsys.com, egcs@cygnus.com
Subject: Re: HJ's patch to libio works on Red Hat 4.2/libc 5.3.12
Date: Tue, 14 Oct 1997 12:55:00 -0000	[thread overview]
Message-ID: <9710141651.AA18340@beeblebrox.synopsys.com> (raw)
In-Reply-To: <199710140314.WAA08555@eh_pc11.xraylith.wisc.edu>

Mumit writes:

> Think I know what the problem is now. The following files are not 
> installed by default now in $prefix/include/g++:
>     
>     libio.h
>     libioP.h
>     iostreamP.h
>     iostdio.h
>     iolibio.h
>     floatio.h
> 
> I had these files leftover from Sept 24 snapshot, and weren't overwritten
> during subsequent snapshot installs.

Thanks for tracking this down, Mumit.

libg++ has suffered from similar problems for many years: failures due
to leftover files from previous versions (e.g. _G_config.h, etc).  Several
items in the g++ FAQ deal with this.

Perhaps "make install" should be fixed to remove everything in
$prefix/include/g++ before installing the new headers (and of course
we should warn folks that this is going to happen).

Joe



  reply	other threads:[~1997-10-14 12:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-10 15:09 Another libio patch H.J. Lu
1997-10-10 22:58 ` Ulrich Drepper
1997-10-11  9:49   ` H.J. Lu
1997-10-11 13:11     ` HJ's patch to libio works on Red Hat 4.2/libc 5.3.12 Joe Buck
1997-10-11 13:40       ` H.J. Lu
1997-10-11 18:35       ` Mumit Khan
1997-10-12 13:31         ` H.J. Lu
1997-10-12 17:03           ` Joe Buck
1997-10-12 18:05             ` Mumit Khan
1997-10-13  8:01             ` H.J. Lu
1997-10-13 20:18               ` Mumit Khan
1997-10-14 12:55                 ` Joe Buck [this message]
1997-10-16 15:19                 ` H.J. Lu
1997-10-13  5:49 ` Another libio patch Neal Becker
1997-10-17 13:49   ` H.J. Lu

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=9710141651.AA18340@beeblebrox.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=egcs@cygnus.com \
    --cc=hjl@lucon.org \
    --cc=khan@xraylith.wisc.edu \
    /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).