Bugs item #2716942, was opened at 2009-03-27 14:56
Message generated for change (Comment added) made by stmane
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2716942&group_id=56967
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: MonetDB Common "stable"
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Wouter Alink (vzzzbx)
Assigned to: Sjoerd Mullender (sjoerd)
Summary: GDK: Error: integer operand out of range
Initial Comment:
Regarding compilation:
./monetdb-install.sh --nightly=stable --enable-xquery
--prefix=/home/walink/opt/MonetDB-stable-debug/ --enable-debug
When I try to use the '--enable-debug' flag, compilation fails (see attached
log). The end of the log reads:
/tmp/cc6YZd3B.s:4926942: Error: integer operand out of range
/tmp/cc6YZd3B.s:4927107: Error: integer operand out of range
/tmp/cc6YZd3B.s:4927379: Error: integer operand out of range
gmake[5]: *** [libbat_la-gdk_scanselect_defs.lo] Error 1
gmake[4]: *** [all] Error 2
gmake[3]: *** [all-recursive] Error 1
gmake[2]: *** [all] Error 2
gmake[1]: *** [all-recursive] Error 1
gmake: *** [all] Error 2
making MonetDB failed
If I compile without "--enable-debug", all works fine.
Note that the machine used is an IA64 machine.
----------------------------------------------------------------------
>Comment By: Stefan Manegold (stmane)
Date: 2009-03-30 00:19
Message:
I can reproduce the compilation error with the source base from CVS
(Feb2009 branch) using default CVS configure settings (i.e.,
--enable-strict --enable-assert --enable-debug --disable-optimize) which is
about the same as using monetdb-install.sh with --enable-debug (default of
compilation from tarballs, and hence when using monetdb-install.sh, is
--disable-strict --disable-assert --disable-debug --disable-optimize).
In case you want/need to debug only other code but MonetDB Common (GDK)
consider compiling MonetDB without --enable-debug (with --disable-debug)
and only those parts that you want/need to debug with --ebale-debug ---
don't know though, whether monetdb-install.sh allows this easily --- or
consider reducing the code (and hence .o) file size via
$ .../configure --help
[...]
--enable-noexpand do not expand the comma-separated list of MIL
types
given as argument, or "all" if no expansion
should
be done default=
[...]
e.g.,
$ .../configure --enable-noexpand=ptr
or
$ .../configure --enable-noexpand=str
----------------------------------------------------------------------
Comment By: Wouter Alink (vzzzbx)
Date: 2009-03-29 11:17
Message:
hmmm, I found the following URL which might be related:
https://bugzilla.redhat.com/show_bug.cgi?id=33288. Is it related? Do I
understand correctly that this bug (which is marked "won't fix") is about
the object file becoming to large?, and that this 'shouldn't be done'.
I tried compiling without the 2 ALGODEBUG lines in
src/gdk/gdk_scanselect_defs.mx and that worked fine. The errors also
disappear when I only remove the BATgetId() calls in those lines.
----------------------------------------------------------------------
Comment By: Fabian (mr-meltdown)
Date: 2009-03-27 15:01
Message:
sorry, click error.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2716942&group_id=56967
------------------------------------------------------------------------------
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
