Re: including a new gnulib module

[John W. Eaton]

On 24-Jul-2012, c. wrote:

| I added the module as suggested and indeed it seems to have been built:
| 
| $ ls libgnu/base64.*
| libgnu/base64.c               libgnu/base64.h         libgnu/base64.lo
| 
| $ nm -a libgnu/.libs/libgnu.a | grep base64
| nm: no name list
| nm: no name list
| libgnu/.libs/libgnu.a(base64.o):
| 0000081e T _base64_decode_alloc_ctx
| 000002b0 T _base64_decode_ctx
| 0000029f T _base64_decode_ctx_init
| 00000000 T _base64_encode
| 000001d7 T _base64_encode_alloc
| 00000265 T _isbase64
| 
| but I stiil seem to have problems linkng to it from a DLD function, as I get:
| 
| Undefined symbols:
|   "base64_encode_alloc(char const*, unsigned long, char**)", referenced from:
|       Fbase64_encode(octave_value_list const&, int)in base64.o
| ld: symbol(s) not found
| collect2: ld returned 1 exit status
| 
| Can anyone see what am I doing wrong in the attached changeset?

I'm gussing that you need to link with libgnu.la, which is something
that is apparently not done for other files in the DLD-FUNCTIONS
directory.

But since these functions are quite small and don't rely on any
external libraries except gnulib, it might be better to just put them
in the data.cc file.

jwe