From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: Clark Evans <clark.evans@manhattanproject.com>
Cc: egcs@cygnus.com
Subject: Re: gperf switch
Date: Tue, 26 Jan 1999 18:18:00 -0000 [thread overview]
Message-ID: <oru2xdpiko.fsf@araguaia.dcc.unicamp.br> (raw)
In-Reply-To: <36AE6ADB.B008652F@manhattanproject.com>
On Jan 26, 1999, Clark Evans <clark.evans@manhattanproject.com> wrote:
> I just downloaded the current ecgs HEAD? from the cvs tree
> using the anonymous access.
> gperf: invalid option -- F
> I typed "gperf --version" gives me GNU gperf 2.7, I looked and this
> seems to be the most updated version (ftp.gnu.org)
Check for a gperf patch within the infrastructure directory, in the
egcs ftp site, or use contrib/egcs_update to update your CVS tree.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
WARNING: multiple messages have this Message-ID
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: Clark Evans <clark.evans@manhattanproject.com>
Cc: egcs@cygnus.com
Subject: Re: gperf switch
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <oru2xdpiko.fsf@araguaia.dcc.unicamp.br> (raw)
Message-ID: <19990131235800.ernRIeNgRQPfXseK906LG0-PUpXrbGg2tiLizjKitqg@z> (raw)
In-Reply-To: <36AE6ADB.B008652F@manhattanproject.com>
On Jan 26, 1999, Clark Evans <clark.evans@manhattanproject.com> wrote:
> I just downloaded the current ecgs HEAD? from the cvs tree
> using the anonymous access.
> gperf: invalid option -- F
> I typed "gperf --version" gives me GNU gperf 2.7, I looked and this
> seems to be the most updated version (ftp.gnu.org)
Check for a gperf patch within the infrastructure directory, in the
egcs ftp site, or use contrib/egcs_update to update your CVS tree.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
next prev parent reply other threads:[~1999-01-26 18:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-25 14:44 mutex in frame code Ulrich Drepper
1999-01-26 5:06 ` Jeffrey A Law
1999-01-26 7:48 ` Ulrich Drepper
1999-01-31 23:58 ` Ulrich Drepper
1999-01-26 9:54 ` Joe Buck
1999-01-26 9:57 ` Jeffrey A Law
1999-01-26 10:23 ` Joe Buck
1999-01-26 10:27 ` David Edelsohn
1999-01-26 10:42 ` Joe Buck
1999-01-26 10:56 ` David Edelsohn
1999-01-26 11:28 ` Joe Buck
1999-01-26 11:44 ` David Edelsohn
1999-01-31 23:58 ` David Edelsohn
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` David Edelsohn
1999-01-26 11:02 ` Nick Ing-Simmons
1999-01-31 23:58 ` Nick Ing-Simmons
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` David Edelsohn
1999-01-26 13:17 ` Gabriel Dos Reis
1999-01-31 23:58 ` Gabriel Dos Reis
1999-01-31 23:58 ` Joe Buck
[not found] ` <36AE692E.A5DD45E6@manhattanproject.com>
1999-01-26 17:27 ` gperf switch Clark Evans
1999-01-26 18:18 ` Alexandre Oliva [this message]
1999-01-26 19:57 ` Donn Terry
1999-01-31 23:58 ` Donn Terry
1999-01-31 23:58 ` Alexandre Oliva
1999-01-31 23:58 ` Clark Evans
1999-01-31 23:58 ` mutex in frame code Jeffrey A Law
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Ulrich Drepper
[not found] <Pine.OSF.4.03.9901271026270.12890-100000@busboy.sped.ukans.edu>
1999-03-09 10:52 ` gperf switch Gerald Pfeifer
1999-03-31 23:46 ` Gerald Pfeifer
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=oru2xdpiko.fsf@araguaia.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=clark.evans@manhattanproject.com \
--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).