Re: Status of GTK port

Peter Wainwright <[email protected]>
Newsgroups gmane.comp.debugging.ddd.general
Message-ID <[email protected]>
On Thu, 2007-11-29 at 17:36 -0800, Scott wrote:

> Hi Peter,
> Mark me down as being interested in the gtk port.
> 
> I am trying to compile gddd from the latest svn sources and I'm getting hung up at this point
> g++ -DHAVE_CONFIG_H -I.  -I./.. -I../gtkx -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/atkmm-1.6 -I/usr/include/gtk-2.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/cairomm-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/atk-1.0   -I/usr/include/libxml2        -O2 -g  -trigraphs  -MT VSLRead.o -MD -MP -MF .deps/VSLRead.Tpo -c -o VSLRead.o VSLRead.C
> ./vsl-gramma.Y: In function ‘int VSLLib_parse()’:
> ./vsl-gramma.Y:215: error: ‘vsllinenumber’ was not declared in this scope
> ./vsl-gramma.Y:224: error: ‘vsllinenumber’ was not declared in this scope
> ./vsl-gramma.Y:268: error: ‘vsltext’ was not declared in this scope
> ./vsl-gramma.Y:306: error: ‘vsllinenumber’ was not declared in this scope
> ./vsl-gramma.Y:340: error: ‘vsllinenumber’ was not declared in this scope
> ./vsl-gramma.Y:533: error: ‘vsltext’ was not declared in this scope
> ./vsl-gramma.Y:541: error: ‘vsltext’ was not declared in this scope
> ./vsl-gramma.Y:548: error: ‘vsltext’ was not declared in this scope
> VSLRead.C: In member function ‘virtual void VSLLib::update(std::istream&)’:
> VSLRead.C:124: error: ‘vslstream’ was not declared in this scope
> VSLRead.C:129: error: ‘vslnameSet’ was not declared in this scope
> VSLRead.C:130: error: ‘pushback_ptr’ was not declared in this scope
> VSLRead.C:130: error: ‘pushback’ was not declared in this scope
> VSLRead.C:143: error: ‘vsllinenumber’ was not declared in this scope
> VSLRead.C: In member function ‘virtual void VSLLib::update(const string&)’:
> VSLRead.C:163: error: ‘switchreset’ was not declared in this scope
> VSLRead.C:164: error: ‘switchup’ was not declared in this scope
> VSLRead.C:166: error: ‘vslstream’ was not declared in this scope
> VSLRead.C:168: error: ‘topstack’ was not declared in this scope
> VSLRead.C: In function ‘void vslerror(const char*)’:
> VSLRead.C:182: error: ‘vsltext’ was not declared in this scope
> VSLRead.C: In static member function ‘static void VSLLib::parse_echo(const string&)’:
> VSLRead.C:192: error: ‘vsllinenumber’ was not declared in this scope
> make[2]: *** [VSLRead.o] Error 1
> 
> I saw a previous post about this being an issue with a newer version of bison. I was using version 2.3, so I tried downgrading to 1.35 but I got the same result.
> I have no previous experience with yacc or bison. How did you get around this problem?
> I am running this on a mostly stock Ubuntu 7.10 machine.
> 
> I think I could put some coding time in on this branch with a little direction, but I'm just starting to mess around with gtk programming so I'm not sure how much help I can be.
> 

Hi Scott,

some helping hands on the GTK port would be great...

I thought at first that I recognised your problem with the VSL parser.
However, it doesn't look quite like the problem I had before
(http://permalink.gmane.org/gmane.comp.debugging.ddd.general/7676).
vsllinenumber is supposed to be defined by vsl-lex.C, which is generated
from vsl-lex.L by flex (or lex) when you run ./CVSMake.  Can you check
if it is there?

[prw@ceiriog ddd]$ grep 'int vsllinenumber' vsl-lex.C
static int vsllinenumber;

(it doesn't matter that it's static: vsl-lex.C is #include'd by
VSLRead.C so we don't need an external symbol).

Peter

> 
> _______________________________________________
> Ddd mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/ddd
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.