octave and uClibc?

[John W. Eaton]

On 29-Aug-2006, Micah A Colon wrote:

| 
| 
| I've been working on updating some small mobile 
| robots, which previously used a mini-distro and
| an ancient version of Matlab.  The goal is to
| move the robots to all open-source, and in the
| interest of size, we've used uClibc/uClibc++ 
| instead of glibc.
| 
| Compiling octave breaks when it hits Array.h,
| looking like it has issues with some of the 
| overloaded functions (error messages included
| below).
| 
| My question is:  Is anyone aware of a successful
| compile of octave using uClibc/uClibc++ instead
| of glibc?  If so, what version, and was there 
| any additional tweaking needed?
| 
| 
| ------
| 
| i386-linux-uclibc-g++ -c -I. -I.. -I../liboctave -I../src -I../libcruft/misc  
-DHAVE_CONFIG_H  -Wall -W -Wshadow -g -O2 Bounds.cc -o Bounds.o
| In file included from MArray.h:32,
|                  from dColVector.h:31,
|                  from Bounds.h:33,
|                  from Bounds.cc:34:
| Array.h:521:44: error: macro "index" passed 3 arguments, but takes just 2
| Array.h:533:44: error: macro "index" passed 4 arguments, but takes just 2
| Array.h:536:44: error: macro "index" passed 3 arguments, but takes just 2
| Array.h:520: error: expected ';' before 'const'
| Array.h:532: error: expected ';' before 'const'
| Array.h:535: error: expected ';' before 'const'
| make[3]: *** [Bounds.o] Error 1

Is there some uClibc/uClibc++ header file in the that is defining
index as a macro even when it should not be?  Octave assumes that
standard headers don't define random non-standard macros.

jwe