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: Thu, 07 Sep 2006 17:43:00 -0000	[thread overview]
Message-ID: <3CE39F664D1EE14293F6923CD00E42C705DDFF17@montremsg32.na.future.ca> (raw)

Sorry,

Substitute:
 
mkdir -p /tmp/build/gdb
cd /tmp/build/gdb
/src/insight-6.5/configure --target=TARGET \
  --prefix=/gnutools -v 2>&1 | tee configure.out

For:

mkdir -p /tmp/build/gdb
cd /tmp/build/gdb
/src/insight-5.3/configure --target=TARGET \
  --prefix=/gnutools -v 2>&1 | tee configure.out 

-Ray 

-----Original Message-----
From: Joel Brobecker [mailto:brobecker@adacore.com] 
Sent: Thursday, September 07, 2006 9:15 AM
To: Ray Duran
Cc: gdb@sourceware.org
Subject: Re: gdb build error


> 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.

I'm pretty sure it used to exist at the time you unpacked the sources.
It must has been deleted somehow. The makefile says:

.l.c:
        if [ "$(FLEX)" ] && $(FLEX) --version >/dev/null 2>&1; then \
            $(FLEX) -o$@ $< && \
            rm -f $@.new && \
            sed -e '/extern.*malloc/d' \ 
                -e '/extern.*realloc/d' \
                -e '/extern.*free/d' \
                -e '/include.*malloc.h/d' \
                -e 's/\([^x]\)malloc/\1xmalloc/g' \
                -e 's/\([^x]\)realloc/\1xrealloc/g' \
                -e 's/yy_flex_xrealloc/yyxrealloc/g' \
              < $@ > $@.new && \
            rm -f $@ && \
            mv $@.new $@; \
        elif [ -f $@ ]; then \
            echo "Warning: $*.c older than $*.l and flex not
available."; \
        else \
            echo "$@ missing and flex not available."; \
            false; \
        fi

so the file MUST have existed for the warning you mentioned to be
printed (the -f test).

I can't really figure out what happened in your case without more
details. If you start from scratch, and send us the list of commands
you used to build your application, then maybe we'll be able to
understand what happened. Please also tell us exactly what package
you downloaded, and where you got it:

> 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?

Are you sure you mean insight? The last releases only included GDB,
not insight.

-- 
Joel


             reply	other threads:[~2006-09-07 17:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 17:43 Ray Duran [this message]
  -- 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:41 Ray Duran
2006-09-19  5:37 ` Joel Brobecker
2006-09-06 22:40 Ray Duran
2006-09-07 16:15 ` 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=3CE39F664D1EE14293F6923CD00E42C705DDFF17@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