public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Ludovic Brenta <ludovic.brenta@skynet.be>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/10740: ../../gcc/gcc/gengtype.c:430: undefined reference to "lexer_line"
Date: Wed, 14 May 2003 08:06:00 -0000	[thread overview]
Message-ID: <20030514080601.24663.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/10740; it has been noted by GNATS.

From: Ludovic Brenta <ludovic.brenta@skynet.be>
To: Dara Hazeghi <dhazeghi@yahoo.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/10740: ../../gcc/gcc/gengtype.c:430: undefined
	reference to "lexer_line"
Date: 14 May 2003 09:59:59 +0200

 Yes, it is a problem of lingering files.  I traced it to the file
 
 gcc/gcc/gengtype-lex.c
 
 which flex creates in the source, not object, directory.  For one reason
 or another, this file ends up being empty, but newer than its source,
 which is gengtype-lex.l.  Then, it gets compiled into an object file
 which lacks "lexer_line" and other symbols.
 
 At first I thought it was a binutils issue; then I thought it was a flex
 issue; not I'm not sure anymore.  I think it is a combination of two
 problems: (1) the build scripts should create gengtype-lex.c in the
 object directory, which I erase completely before each bootstrap; and
 (2) flex should fail instead of creating an empty C file.
 
 I've had success this night bootstrapping GCC 3.3 after downgrading flex
 to 2.5.4a (stable) and erasing the C file.  I'll try again with the
 testing version of flex (2.5.31) to see if it's a flex problem.
 
 BTW, the build scripts also create other files in the source directory;
 for example, gengtype-yacc.c (from gengtype-yacc.y), and some .info
 files in the ada subdirectory (from .texinfo files).  This does not
 appear to create problems for me right now, but I see this as a latent
 bug.
 
 --
 Ludovic Brenta.
 
 
 


             reply	other threads:[~2003-05-14  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  8:06 Ludovic Brenta [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-19 13:36 Ludovic Brenta
2003-05-14  7:06 Dara Hazeghi
2003-05-11 15:26 ludovic.brenta

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=20030514080601.24663.qmail@sources.redhat.com \
    --to=ludovic.brenta@skynet.be \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).