From: Carlo Wood <carlo@alinoe.com>
To: David Ayers <d.ayers@inode.at>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
gcc@gcc.gnu.org, kcook34@ford.com
Subject: Re: Someone broke bootstrap
Date: Wed, 08 Oct 2003 11:57:00 -0000 [thread overview]
Message-ID: <20031008115745.GA19191@alinoe.com> (raw)
In-Reply-To: <3F83E286.9090404@inode.at>
On Wed, Oct 08, 2003 at 12:10:14PM +0200, David Ayers wrote:
> John David Anglin wrote:
> >How about
> >
> >if flex -o g-$$ ../../gcc/gcc/gengtype-lex.l; then \
> > mv -f g-$$ ../../gcc/gcc/gengtype-lex.c ; \
> >else \
> > rm -f g-$$ ; \
> > false ; \
> >fi
> >flex: can't open g-16194
> >
> >on i686-pc-linux-gnu.
> >
> >There are also a bunch of testsuite regressions on hppa64-hp-hpux11.11.
> >
> >Dave
> >
> >
> This seems to be caused by:
>
> http://gcc.gnu.org/ml/gcc-patches/2003-10/msg00529.html
>
> Is flex 2.5.4 unsupported?
No, the patch is wrong.
I'll write a patch and commit it as obvious in a few minutes.
Flex doesn't take a space after the -o option. It must be -ooutput,
not -o output. Kelley, assuming you tested this - what version
of flex do you use that this worked for you??
--
Carlo Wood <carlo@alinoe.com>
next prev parent reply other threads:[~2003-10-08 11:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 2:47 John David Anglin
2003-10-08 10:15 ` David Ayers
2003-10-08 11:57 ` Carlo Wood [this message]
2003-10-08 12:29 ` [PATCH] " Carlo Wood
2003-10-08 12:43 ` Eric Botcazou
2003-10-08 12:57 ` Carlo Wood
-- strict thread matches above, loose matches on Subject: below --
2003-10-09 3:02 Roger Sayle
2003-10-08 14:03 Kelley Cook
[not found] <no.id>
2003-10-08 3:11 ` John David Anglin
2003-10-08 7:25 ` Eric Christopher
2003-10-08 17:26 ` John David Anglin
2003-10-08 2:11 Carlo Wood
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=20031008115745.GA19191@alinoe.com \
--to=carlo@alinoe.com \
--cc=d.ayers@inode.at \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc@gcc.gnu.org \
--cc=kcook34@ford.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).