From: "'David Scott Urban" <urban@ast.lmco.com>
To: oliva@lsd.ic.unicamp.br
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problem building egcs-20000313 on a Solaris 2.5.1 box
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200003151458.HAA22739@spica.ast.lmco.com> (raw)
Message-ID: <20000401000000.XWSR3qJsf675rxPPoBvronqKx5UxLH-Hz3YATLyInJY@z> (raw)
>
> On Mar 15, 2000, "'David Scott Urban" <urban@ast.lmco.com> wrote:
>
> > ../../egcs/gcc/stor-layout.c:691: `record_align' undeclared (first use in
this
>
> Yup, it's a simple typo, just open the file in the given line, look a
> few lines above and below and the fix will be obvious. Or just get
> the next delta from CVS :-)
>
Thanks. I knew it was something that simple. Just in too big of a hurry to get
things done.
Scott Urban
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 6:59 'David Scott Urban [this message]
2000-04-01 0:00 ` 'David Scott Urban
-- strict thread matches above, loose matches on Subject: below --
2000-03-15 6:28 'David Scott Urban
2000-03-15 6:32 ` Alexandre Oliva
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` 'David Scott Urban
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=200003151458.HAA22739@spica.ast.lmco.com \
--to=urban@ast.lmco.com \
--cc=gcc-help@gcc.gnu.org \
--cc=oliva@lsd.ic.unicamp.br \
/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).