can't compile today
![](https://secure.gravatar.com/avatar/bb65b6b3a109d97cf9f8d6c014ede042.jpg?s=120&d=mm&r=g)
OK, I downloaded and installed gtkmm and sigc++. Still no luck:
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -I../../src -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libart-2.0 -I/usr/include/libxml2 -g -O2 -I/usr/local/include/gtkmm-2.0 -I/usr/local/lib/gtkmm-2.0/include -I/usr/local/lib/sigc++-1.2/include -I/usr/local/include/sigc++-1.2 -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/atk-1.0 -c -o nr-pixblock.o `test -f 'nr-pixblock.cpp' || echo './'`nr-pixblock.cpp nr-pixblock.cpp: In function `void nr_pixblock_setup_fast(NRPixBlock*, int, int, int, int, int, int)': nr-pixblock.cpp:45: error: `rpl_malloc' undeclared (first use this function) nr-pixblock.cpp:45: error: (Each undeclared identifier is reported only once for each function it appears in.) nr-pixblock.cpp: In function `void nr_pixblock_setup(NRPixBlock*, int, int, int, int, int, int)': nr-pixblock.cpp:75: error: `rpl_malloc' undeclared (first use this function) nr-pixblock.cpp: In function `NRPixBlock* nr_pixblock_new(int, int, int, int, int, int)': nr-pixblock.cpp:148: error: `rpl_malloc' undeclared (first use this function) nr-pixblock.cpp: In function `unsigned char* nr_pixelstore_4K_new(int, unsigned char)': nr-pixblock.cpp:181: error: `rpl_malloc' undeclared (first use this function) nr-pixblock.cpp: In function `unsigned char* nr_pixelstore_16K_new(int, unsigned char)': nr-pixblock.cpp:215: error: `rpl_malloc' undeclared (first use this function) nr-pixblock.cpp: In function `unsigned char* nr_pixelstore_64K_new(int, unsigned char)': nr-pixblock.cpp:249: error: `rpl_malloc' undeclared (first use this function)
_________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...
![](https://secure.gravatar.com/avatar/eb3fe37da4a199eb4e3b479d8a57f808.jpg?s=120&d=mm&r=g)
On Fri, 2003-12-26 at 17:05, bulia byak wrote:
nr-pixblock.cpp:45: error: `rpl_malloc' undeclared (first use this function) nr-pixblock.cpp:45: error: (Each undeclared identifier is reported only once for each function it appears in.)
Line 45 uses nr_new() which is defined in nr-macros.h:
#define nr_new(t,n) ((t *) malloc ((n) * sizeof (t)))
Now, apparently AC_FUNC_MALLOC will redefine malloc to rpl_malloc if it determines malloc isn't "GNU compatible" ... which is probably a good reason not to use AC_FUNC_MALLOC. I'm not sure how that could possibly count as a feature.
I'll remove AC_FUNC_MALLOC from configure.in.
-mental
![](https://secure.gravatar.com/avatar/8d5128b5b838ecedc34635fba7995f7f.jpg?s=120&d=mm&r=g)
On Fri, 26 Dec 2003, MenTaLguY wrote:
On Fri, 2003-12-26 at 17:05, bulia byak wrote:
nr-pixblock.cpp:45: error: `rpl_malloc' undeclared (first use this function) nr-pixblock.cpp:45: error: (Each undeclared identifier is reported only once for each function it appears in.)
Line 45 uses nr_new() which is defined in nr-macros.h:
#define nr_new(t,n) ((t *) malloc ((n) * sizeof (t)))
Now, apparently AC_FUNC_MALLOC will redefine malloc to rpl_malloc if it determines malloc isn't "GNU compatible" ... which is probably a good reason not to use AC_FUNC_MALLOC. I'm not sure how that could possibly count as a feature.
Hmm, though isn't this what Autoconf is supposed to do? E.g., presumably there are non-GNU compilers that lack a proper malloc function so use this replacement.
Bryce
![](https://secure.gravatar.com/avatar/eb3fe37da4a199eb4e3b479d8a57f808.jpg?s=120&d=mm&r=g)
On Fri, 2003-12-26 at 18:33, Bryce Harrington wrote:
Now, apparently AC_FUNC_MALLOC will redefine malloc to rpl_malloc if it determines malloc isn't "GNU compatible" ... which is probably a good reason not to use AC_FUNC_MALLOC. I'm not sure how that could possibly count as a feature.
Hmm, though isn't this what Autoconf is supposed to do? E.g., presumably there are non-GNU compilers that lack a proper malloc function so use this replacement.
For values of "proper malloc" where malloc(0) returns a valid pointer, I suppose. I have yet to find code that relies on that behavior (ours certainly doesn't).
AC_FUNC_MALLOC should more properly be called AC_FUNC_GNU_MALLOC, IMO.
Anyway, if we're building on a platform that doesn't even provide malloc() we probably have bigger problems to worry about.
-mental
![](https://secure.gravatar.com/avatar/f9d6294b37cdbbb51eb70be7d329a9e0.jpg?s=120&d=mm&r=g)
Did I imagine it or is there a user manual in preparation somewhere? I seem to remember a French? one, and maybe an English version. can someone point me in the right direction? Thanks. vellum
![](https://secure.gravatar.com/avatar/8d5128b5b838ecedc34635fba7995f7f.jpg?s=120&d=mm&r=g)
On Sat, 27 Dec 2003, vellum wrote:
Did I imagine it or is there a user manual in preparation somewhere? I seem to remember a French? one, and maybe an English version. can someone point me in the right direction? Thanks. vellum
You can get a copy from Inkscape CVS - it's the 'manual' module.
Bryce
participants (4)
-
Bryce Harrington
-
bulia byak
-
MenTaLguY
-
vellum