From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: egcs@cygnus.com
Subject: libg++-980119 wouldn't build with egcs-980129 (patch)
Date: Sat, 31 Jan 1998 14:34:00 -0000 [thread overview]
Message-ID: <orhg6ki8gl.fsf@amazonas.dcc.unicamp.br> (raw)
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
Hi!
Some interfaces between configure scripts were changed in last
snapshot, in a way that libg++ was broken. Here's a patch that
updates libg++'s configure files so that it builds with the latest
egcs snapshot.
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil
[-- Attachment #2: libg++-egcs-980129.diff.gz --]
[-- Type: application/x-gzip, Size: 1435 bytes --]
next reply other threads:[~1998-01-31 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-31 14:34 Alexandre Oliva [this message]
1998-02-01 1:05 ` Franz Sirl
1998-02-01 1:22 ` Jeffrey A Law
1998-02-01 1:34 ` Franz Sirl
1998-02-01 12:55 ` Jeffrey A Law
1998-02-01 15:08 ` H.J. Lu
1998-02-01 15:35 ` Franz Sirl
1998-02-01 15:42 ` H.J. Lu
1998-02-01 15:28 ` libg++ 2.8.1 980201 is released 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=orhg6ki8gl.fsf@amazonas.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--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).