Recent changes to support-requests

dparser_wrap.c missing in d-1.19

Ted Herman — Fri, 27 Jun 2008 19:50:47 -0000

The python part of the install fails (gmake install in python directory), because dparser_wrap.c is missing. When did swig become a prereq?

DParser for python on Solaris

Anonymous — Mon, 13 Aug 2007 18:31:09 -0000

Hi everyone,

Sorry to ask this low-level question.
My friend introduced me DParser for python and I want to install it on my machine (Solaris).

I downloaded the package and first make the DParser package. It worked and 'make test' also worked.

However, I tried to install the python interface, I got relocation error. The error was generated when .so was generated:

# make install
python setup.py install
running install
running build
running build_py
creating build
creating build/lib.solaris-2.9-sun4u-2.4
copying dparser.py -> build/lib.solaris-2.9-sun4u-2.4
running build_ext
building 'dparser_swigc' extension
creating build/temp.solaris-2.9-sun4u-2.4
gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -DSWIG_GLOBAL -I/usr/local/include/python2.4 -c dparser_wrap.c -o build/temp.solaris-2.9-sun4u-2.4/dparser_wrap.o -Wall
In file included from /usr/local/include/python2.4/Python.h:8,
from dparser_wrap.c:47:
/usr/local/include/python2.4/pyconfig.h:836:1: warning: "_FILE_OFFSET_BITS" redefined
In file included from /usr/include/iso/string_iso.h:31,
from /usr/include/string.h:18,
from dparser_wrap.c:22:
/usr/include/sys/feature_tests.h:96:1: warning: this is the location of the previous definition
dparser_wrap.c:1590: warning: function declaration isn't a prototype
gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -DSWIG_GLOBAL -I/usr/local/include/python2.4 -c pydparser.c -o build/temp.solaris-2.9-sun4u-2.4/pydparser.o -Wall
gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -DSWIG_GLOBAL -I/usr/local/include/python2.4 -c make_tables.c -o build/temp.solaris-2.9-sun4u-2.4/make_tables.o -Wall
gcc -shared build/temp.solaris-2.9-sun4u-2.4/dparser_wrap.o build/temp.solaris-2.9-sun4u-2.4/pydparser.o build/temp.solaris-2.9-sun4u-2.4/make_tables.o -L../ -lmkdparse -ldparse -o build/lib.solaris-2.9-sun4u-2.4/dparser_swigc.so
Text relocation remains referenced
against symbol offset in file
<unknown> 0x2a8 ..//libmkdparse.a(gram.o)
<unknown> 0x2ac ..//libmkdparse.a(gram.o)
<unknown> 0x2b0 ..//libmkdparse.a(gram.o)
<unknown> 0x2b4 ..//libmkdparse.a(gram.o)
... <snip> .... (many relocation errors)

I'm using the following versions:
Solaris 9 (sun4u)
gcc (GCC) 3.4.2
Python 2.4.4
SWIG Version 1.3.29

As I don't see any errors in the original DParser package, I don't have any clue why 'python setup.py install' generates these errors.

Any suggestions will be highly appreciated.

Best regards,
Aki Niimura

Check return codes everywhere

Markus Elfring — Thu, 01 Mar 2007 15:07:36 -0000

Some checks for return codes are missing.

Examples:
Would you like to add more error handling for return values from "(f)printf" in functions like "print_declarations" and "print_no_comma"?
http://dparser.cvs.sourceforge.net/dparser/d/write_tables.c?revision=1.1.1.1&view=markup

Memory leak

Jamie Webb — Mon, 17 Jan 2005 16:26:24 -0000

I'm trying to write a Lua binding for DParser which
constructs parse tables on the fly, based on the code
from test_parser.c, but I haven't been able to figure
out how to free() the D_ParserTables object returned by
read_binary_tables_from_string(): it undergoes some
pointer arithmetic before it is returned and the base
address appears to be lost. Is there some way to
recover this? If not, is it safe to add an extra member
to D_ParserTables with this information?

Cheers

Support for "A - B" grammar in EBNF.

Jeff Max — Thu, 15 Apr 2004 15:49:49 -0000

Does dparser supports the EBNF grammar:
C ::= A - B, whose semantic is that C matches any
string that matches A but does not match B?

can't build under RHL 9

Jon Willeke — Thu, 04 Sep 2003 00:31:56 -0000

I built D Parser 1.5 fine with GCC 3.3 on SuSE Linux
8.2, but I'm getting a cryptic error with GCC 3.2.2 on
Red Hat Linux 9:

./make_dparser sample.g
make: *** [sample.g.d_parser.c] Illegal instruction

Any ideas, besides upgrading GCC?

Can't create header file

Anonymous — Thu, 28 Aug 2003 09:51:07 -0000

I submitted this to the help forum as well, but I'm not
sure if anybody monitors it.

I've managed to create my first DParser and it looks
like it's working (the test drivers fails and succeeds
as it should), but to go further I need to be able to
look at the parse tree, and for that I need headers.

Unfortuneatly the header files that are generated are
always empty (except for the ifndef/define/endif). Is
there some magic I'm missing?

something like yywrap?

Jason Bobier — Wed, 20 Aug 2003 00:12:06 -0000

So I think that the previous request's "streaming reading"
feature is the same thing that I'm after.

I would love to use dparser in the next version of our
software, but my data is coming off of the net, so I don't
know the buffer size when I call dparse. I need something
like yywrap to let me add to the buffer during the parse.

Or is there already some way to do this that I'm missing?

Thanx,

Jason

need some features

Anonymous — Fri, 13 Jun 2003 09:56:51 -0000

It looks good parser which I want,especially I like
scannerless architecture.

but It is not unusable a little,
I hope some features such as:

streaming reading(it seems user need to allocate memory
for parsing,doesn't it?)
reentrant parser(I could not confirm)
C++ parser output(If it can do)
multiple parser(I want to rename each parser)

I'm not good at English so I'm sorry if I make you
unpleasant.