From: Jeffrey A Law <law@cygnus.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: Alexandre Oliva <oliva@dcc.unicamp.br>, egcs@cygnus.com
Subject: Re: libg++-980119 wouldn't build with egcs-980129 (patch)
Date: Sun, 01 Feb 1998 12:55:00 -0000 [thread overview]
Message-ID: <26580.886366424@hurl.cygnus.com> (raw)
In-Reply-To: <v03130303b0f9ff78c629@[195.180.235.207]>
In message < v03130303b0f9ff78c629@[195.180.235.207] >you write:
> >Can someone send a copy of this patch to the list?
> >
> >jeff
>
> It's in the archive:
> < http://www.cygnus.com/ml/egcs/1997-Oct/1067.html >
Thank you.
egcs already has the patch to configure.in.
I don't understand why we need the second patch. I've configured
and used egcs with absolute pathnames for a long time without
running into these kinds of problems.
jeff
next prev parent reply other threads:[~1998-02-01 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-31 14:34 Alexandre Oliva
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 [this message]
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=26580.886366424@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=egcs@cygnus.com \
--cc=oliva@dcc.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).