RE: gdb build error

RE: gdb build error

[Ray Duran]

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

RE: gdb build error

[Ray Duran]

Thank you very much Michael for your explanation.

I will try both options; Copying file from gdb release
and using flex.

Thanks again.

-Ray

-----Original Message-----
From: Michael Snyder [mailto:Michael.Snyder@palmsource.com] 
Sent: Tuesday, September 19, 2006 12:07 PM
To: Joel Brobecker; Ray Duran
Cc: gdb@sourceware.org
Subject: RE: gdb build error



Ray, here's your problem in a nutshell:

ada-lex.c is not a "primary source file" -- it's a generated file.
It's normally generated by 'flex', which is the GNU version of lex, 
during the make process.  The source file that it is generated from
is called ada-lex.l, (l for lex), and that file SHOULD be present 
in your source (tarball) tree.

However, since some people don't have flex installed, we (the gdb
maintainers) usually go ahead and include ada-lex.c in our source
distribution, just to make things easy.  And in fact, you will find
it in our tarball for gdb-6.5 (I hope).

However*2, you are not getting your source tarball from us.
You're getting it from the insight maintainers.  And for whatever
reason, they seem to have omitted this file, perhaps assuming that
everyone has flex installed and therefore can generate it.

So there are a number of things you can do at this point.
I can only think of one that would fall under the category
of "supported", though, and that would be --

     Install flex.

This is not difficult to do, and you don't even have to be
root to install it somewhere locally.

If you don't want to do that, you could obtain the actual
gdb-6.5 tarball (as opposed to the insight gdb tarball), 
unpack it, and copy the file from there into your insight
tree.  This SHOULD be ok, but we can't make you any guarantees.
There's always the possibility that their version is different
(but it's highly unlikely).

To be safe, you could diff the two versions of ada-lex.l.
If they are the same, then you are home free.

Michael



-----Original Message-----
From: gdb-owner@sourceware.org on behalf of Joel Brobecker
Sent: Tue 9/19/2006 10:52 AM
To: Ray Duran
Cc: gdb@sourceware.org
Subject: Re: gdb build error
 
> I looked at the tarball after "untaring" file and I cannot see
> ada-lex.c.  Where can I find an insight tarball that I can build gdb(
> with ada-lex.c)

That's the problem - the tarball should include that file.
What you need to do is to tell the people who created that tarball
to make sure that ada-lex.c is included.

Or perhaps it was an intentional decision on their part. This file
is not part of the CVS tree, but is automatically created during
the GDB release creation process.

-- 
Joel

RE: gdb build error

[Ray Duran]

Joel,

Is there a good site that you know of where I can get a download where I
will not have 
this problem?

Thanks,

-Ray

-----Original Message-----
From: Joel Brobecker [mailto:brobecker@adacore.com] 
Sent: Tuesday, September 19, 2006 10:53 AM
To: Ray Duran
Cc: gdb@sourceware.org
Subject: Re: gdb build error


> I looked at the tarball after "untaring" file and I cannot see
> ada-lex.c.  Where can I find an insight tarball that I can build gdb(
> with ada-lex.c)

That's the problem - the tarball should include that file.
What you need to do is to tell the people who created that tarball
to make sure that ada-lex.c is included.

Or perhaps it was an intentional decision on their part. This file
is not part of the CVS tree, but is automatically created during
the GDB release creation process.

-- 
Joel

Re: gdb build error

[Joel Brobecker]

> Is there a good site that you know of where I can get a download where
> I will not have this problem?

I'm sorry, I don't.

-- 
Joel

Re: gdb build error

[Daniel Jacobowitz]

On Tue, Sep 19, 2006 at 10:59:02AM -0700, Joel Brobecker wrote:
> > Is there a good site that you know of where I can get a download where
> > I will not have this problem?
> 
> I'm sorry, I don't.

Ray, you're looking at an Insight release.  Insight has its own mailing
list, insight@sourceware.org; I recommend asking there.

-- 
Daniel Jacobowitz
CodeSourcery

Re: gdb build error

[Keith Seitz]

Joel Brobecker wrote:
>> Is there a good site that you know of where I can get a download where
>> I will not have this problem?
> 
> I'm sorry, I don't.

That was my bad. I'm working on fixing this. Silly me, I didn't actually 
know that there was a release process. [cough]

Anyway, the three easiest solutions for Ray are to either: 1) install 
flex and whatever else may be needed to generate the missing files; 2) 
untar the insight "release" and then copy the insight bits (gdb/gdbtk, 
tcl, tk, itcl,libgui) into a real gdb release; or 3) wait for me to 
announce that a fixed release is available.

Keith

RE: gdb build error

[Ray Duran]

Hi Joel,

Thanks very much for replying.

I went off on a side project, but I still need to build a gdb.

I looked at the tarball after "untaring" file and I cannot see
ada-lex.c.
Where can I find an insight tarball that I can build gdb( with
ada-lex.c)

Thanks,

-Ray

-----Original Message-----
From: Joel Brobecker [mailto:brobecker@adacore.com] 
Sent: Monday, September 18, 2006 10:37 PM
To: Ray Duran
Cc: gdb@sourceware.org
Subject: Re: gdb build error


Ray,

(sorry about the delay - work suddenly became crazy)

> -Yes, I agree that the file probably existed.
> 
> - I am not sure what mirror site I downloaded the file from, but the
> name of 
> the tar is: insight-6.5.tar.bz2.

Have you been able to build GDB since then?

> - I followed the list of configure and build command that I found on
> the eCos page for installing GNU tools. My final application is to use
> eCos on an ARM.

That may be where you got the sources from. I don't know what this
package contains, so it's going to be difficult for me to help you
further. Maybe the people who actually created the tarball might be
able to help you further.

Otherwise, check before doing the configure that this file exists.
Then do the configure, and check again. Then do the build, and check
again. If it disappears during the build as I suspect, then grep
for that filename in the build output - that should give you a good
clue as to what is happening.

As a workaround, you may want to retrieve that file and copy it back
right after the build failed, and then restart the build. That should
work.

Another approach, of course, is to install flex, check out www.gnu.org.

-- 
Joel

Re: gdb build error

[Joel Brobecker]

> I looked at the tarball after "untaring" file and I cannot see
> ada-lex.c.  Where can I find an insight tarball that I can build gdb(
> with ada-lex.c)

That's the problem - the tarball should include that file.
What you need to do is to tell the people who created that tarball
to make sure that ada-lex.c is included.

Or perhaps it was an intentional decision on their part. This file
is not part of the CVS tree, but is automatically created during
the GDB release creation process.

-- 
Joel

RE: gdb build error

[Michael Snyder]

Ray, here's your problem in a nutshell:

ada-lex.c is not a "primary source file" -- it's a generated file.
It's normally generated by 'flex', which is the GNU version of lex, 
during the make process.  The source file that it is generated from
is called ada-lex.l, (l for lex), and that file SHOULD be present 
in your source (tarball) tree.

However, since some people don't have flex installed, we (the gdb
maintainers) usually go ahead and include ada-lex.c in our source
distribution, just to make things easy.  And in fact, you will find
it in our tarball for gdb-6.5 (I hope).

However*2, you are not getting your source tarball from us.
You're getting it from the insight maintainers.  And for whatever
reason, they seem to have omitted this file, perhaps assuming that
everyone has flex installed and therefore can generate it.

So there are a number of things you can do at this point.
I can only think of one that would fall under the category
of "supported", though, and that would be --

     Install flex.

This is not difficult to do, and you don't even have to be
root to install it somewhere locally.

If you don't want to do that, you could obtain the actual
gdb-6.5 tarball (as opposed to the insight gdb tarball), 
unpack it, and copy the file from there into your insight
tree.  This SHOULD be ok, but we can't make you any guarantees.
There's always the possibility that their version is different
(but it's highly unlikely).

To be safe, you could diff the two versions of ada-lex.l.
If they are the same, then you are home free.

Michael



-----Original Message-----
From: gdb-owner@sourceware.org on behalf of Joel Brobecker
Sent: Tue 9/19/2006 10:52 AM
To: Ray Duran
Cc: gdb@sourceware.org
Subject: Re: gdb build error
 
> I looked at the tarball after "untaring" file and I cannot see
> ada-lex.c.  Where can I find an insight tarball that I can build gdb(
> with ada-lex.c)

That's the problem - the tarball should include that file.
What you need to do is to tell the people who created that tarball
to make sure that ada-lex.c is included.

Or perhaps it was an intentional decision on their part. This file
is not part of the CVS tree, but is automatically created during
the GDB release creation process.

-- 
Joel

RE: gdb build error

[Ray Duran]

Hello Joel,

-Yes, I agree that the file probably existed.

- I am not sure what mirror site I downloaded the file from, but the
name of 
the tar is: insight-6.5.tar.bz2.

- I followed the list of configure and build command that I found on the
eCos
page for installing GNU tools. My final application is to use eCos on an
ARM.
 
*********************************************
Configure Insight:


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


Build and install Insight:


make -w all install 2>&1 | tee make.out 

*********************************************

With my target= arm-elf

- I say that this is insight only because the name of the TAR. It may
very well be
gdb.

Thank you very much for your time and attention,

-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

Re: gdb build error

[Joel Brobecker]

Ray,

(sorry about the delay - work suddenly became crazy)

> -Yes, I agree that the file probably existed.
> 
> - I am not sure what mirror site I downloaded the file from, but the
> name of 
> the tar is: insight-6.5.tar.bz2.

Have you been able to build GDB since then?

> - I followed the list of configure and build command that I found on
> the eCos page for installing GNU tools. My final application is to use
> eCos on an ARM.

That may be where you got the sources from. I don't know what this
package contains, so it's going to be difficult for me to help you
further. Maybe the people who actually created the tarball might be
able to help you further.

Otherwise, check before doing the configure that this file exists.
Then do the configure, and check again. Then do the build, and check
again. If it disappears during the build as I suspect, then grep
for that filename in the build output - that should give you a good
clue as to what is happening.

As a workaround, you may want to retrieve that file and copy it back
right after the build failed, and then restart the build. That should
work.

Another approach, of course, is to install flex, check out www.gnu.org.

-- 
Joel

RE: gdb build error

[Ray Duran]

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

Re: gdb build error

[Joel Brobecker]

> 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

gdb build error

[Ray Duran]

Hello,

When I build gdb 6.5, I get the output, ada-lex.c missing and flex not
availiable. I searched the gdb archives and see
similar concerns for gdb 6.3, but I don't see any clues on how to
resolve this.

Any thoughts?

I am not sure if this is the correct address/forum for this question, so
I apologize in advance.

Thanks,

-Ray

Ray Duran 
Altera Design Specialist
Future Electronics 
2220 O'Toole Avenue 
San Jose Ca. 95131 
408 232 1478 
ray.duran@futureelectronics.com 
The information in this transmission contains information that is
confidential and is intended only for the use of the individual or
entity to whom it is addressed. If the reader of this message is not the
intended recipient please delete it and immediately notify the sender. 
If the purpose of this transmission is to provide a quotation or to
confirm or acknowledge an order or to provide information in relation to
the Products and Services offered, unless otherwise agreed in writing,
the FUTURE ELECTRONICS TERMS AND CONDITIONS OF SALE exclusively govern
the sale of Products and the provision of services by Future Electronics
Inc. and its divisions, subsidiaries and affiliates and take precedence
over supplemental or conflicting terms and conditions to which notice of
objection is hereby given. The FUTURE ELECTRONICS TERMS AND CONDITIONS
OF SALE are available at www.futureelectronics.com
<http://www.futureelectronics.com/>  and may be provided on invoices,
packing slips, order acknowledgements or other method. 

Re: gdb build error

[Joel Brobecker]

> When I build gdb 6.5, I get the output, ada-lex.c missing and flex not
> availiable. I searched the gdb archives and see
> similar concerns for gdb 6.3, but I don't see any clues on how to
> resolve this.

You'll need flex to generate ada-lex.c. Has this tool been installed
on your machine?

-- 
Joel

Re: gdb build error

[Daniel Jacobowitz]

On Wed, Sep 06, 2006 at 03:05:57PM -0700, Joel Brobecker wrote:
> > When I build gdb 6.5, I get the output, ada-lex.c missing and flex not
> > availiable. I searched the gdb archives and see
> > similar concerns for gdb 6.3, but I don't see any clues on how to
> > resolve this.
> 
> 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?

-- 
Daniel Jacobowitz
CodeSourcery

Re: gdb build error

[Mark Kettenis]

> Date: Wed, 6 Sep 2006 18:10:31 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Wed, Sep 06, 2006 at 03:05:57PM -0700, Joel Brobecker wrote:
> > > When I build gdb 6.5, I get the output, ada-lex.c missing and flex not
> > > availiable. I searched the gdb archives and see
> > > similar concerns for gdb 6.3, but I don't see any clues on how to
> > > resolve this.
> > 
> > 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?

Yes!

Mark

Re: gdb build error

[Joel Brobecker]

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