From: Jeffrey A Law <law@cygnus.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>,
Kate Hedstrom <kate@ahab.rutgers.edu>
Cc: egcs@cygnus.com
Subject: Re: bastring.h trouble on mips-sgi-irix5.2
Date: Tue, 11 Nov 1997 07:49:00 -0000 [thread overview]
Message-ID: <11519.879263462@hurl.cygnus.com> (raw)
In-Reply-To: <9711102343.AA01932@moene.indiv.nluug.nl>
In message < 9711102343.AA01932@moene.indiv.nluug.nl >you write:
> I got exactly the same error as Kate, on m68k-next-nextstep3, after
> repairing the fact that, as distributed, egcs doesn't `fixinclude'
> the directory /NextDeveloper/Headers.
>
> However, I do note that not everyone is reporting this error.
> Might it be that I get it because I updated egcs from egcs-971031 to
> egcs-971105 using the ...diff.gz ? Kate ?
Look for any zero length files in libio/libstdc++ -- some stuff got
moved around. Maybe you're accidentally picking up a file that was
deleted in the distribution, but because you used "patch" to update
maybe it's just zero length (instead of deleted).
Jeff
next prev parent reply other threads:[~1997-11-11 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-10 13:47 Jeffrey A Law
1997-11-10 16:08 ` Toon Moene
1997-11-11 7:49 ` Jeffrey A Law [this message]
1997-11-10 19:34 ` Kriang Lerdsuwanakij
1997-11-11 6:24 Kate Hedstrom
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=11519.879263462@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=kate@ahab.rutgers.edu \
--cc=toon@moene.indiv.nluug.nl \
/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).