Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ray Duran" <Ray.Duran@FutureElectronics.com>
To: "Joel Brobecker" <brobecker@adacore.com>
Cc: <gdb@sourceware.org>
Subject: RE: gdb build error
Date: Wed, 06 Sep 2006 22:40:00 -0000	[thread overview]
Message-ID: <3CE39F664D1EE14293F6923CD00E42C704CD96A3@montremsg32.na.future.ca> (raw)

Hi Joel,

Yes, I do see a warning before my error that says:
"Warning: ada-lex.c older than ada-lex.l and flex not available".

However, I have done a search of ada-lex.c and cannot find anywhere.
That in fact make the message a bit of an anomaly, since the warning
says that ada-lex.c is older but it does not exist.

If I re-downloaded insight tar 6.5 or an earlier version could I
configure and build 
Insight over what I have already done? There isn't any need for deleting
old insight stuff?

Thanks,

-Ray 

-----Original Message-----
From: Joel Brobecker [mailto:brobecker@adacore.com] 
Sent: Wednesday, September 06, 2006 3:18 PM
To: Ray Duran; gdb@sourceware.org
Subject: Re: gdb build error


> > You'll need flex to generate ada-lex.c. Has this tool been installed
> > on your machine?
> 
> Wasn't this supposed to be pregenerated in release tarballs?

Humpf, of course, I should have paid more attention to the version
number. I just double-checked, it is part of the release tarball.

The only scenario that I can think of that might lead to this problem
would be that the timestamp of ada-lex.c somehow became earlier than
the timestamp of ada-lex.l, so the Makefile determined that ada-lex.c
should be rebuilt.

When I unpacked the sources from gnu.org on a linux machine, the
timestamps were in the right order.

While we look at this, the obvious workaround that would work, assuming
my theory is right, would be to "touch gdb/ada-lex.c" before doing the
build.

-- 
Joel


             reply	other threads:[~2006-09-06 22:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06 22:40 Ray Duran [this message]
2006-09-07 16:15 ` Joel Brobecker
  -- strict thread matches above, loose matches on Subject: below --
2006-09-19 21:38 Ray Duran
2006-09-19 17:54 Ray Duran
2006-09-19 17:59 ` Joel Brobecker
2006-09-19 18:00   ` Daniel Jacobowitz
2006-09-19 18:54   ` Keith Seitz
2006-09-19 17:49 Ray Duran
2006-09-19 17:52 ` Joel Brobecker
2006-09-19 19:07   ` Michael Snyder
2006-09-07 17:43 Ray Duran
2006-09-07 17:41 Ray Duran
2006-09-19  5:37 ` Joel Brobecker
2006-09-06 22:01 Ray Duran
2006-09-06 22:06 ` Joel Brobecker
2006-09-06 22:10   ` Daniel Jacobowitz
2006-09-06 22:14     ` Mark Kettenis
2006-09-06 22:18     ` Joel Brobecker

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=3CE39F664D1EE14293F6923CD00E42C704CD96A3@montremsg32.na.future.ca \
    --to=ray.duran@futureelectronics.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.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