trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2015

Re: [trinity-devel] libtdeldap fails to build on ARM

From: Slávek Banko <slavek.banko@...>
Date: Mon, 28 Dec 2015 16:28:43 +0100
On Monday 28 of December 2015 16:15:35 Michael Howard wrote:
> I'm having problems building libtdeldap for ARM. The build fails with
> the following errors;
>
> ldappasswddlg.cpp: In constructor
> 'LDAPPasswordDialog::LDAPPasswordDialog(TQWidget*, const char*, bool,
> bool)':
> ldappasswddlg.cpp:36:96: warning: enumeral and non-enumeral type in
> conditional expression [enabled by default]
> ldappasswddlg.cpp:36:123: warning: enumeral and non-enumeral type in
> conditional expression [enabled by default]
> In file included from /usr/include/hdb_asn1.h:8:0,
>                   from /usr/include/hdb.h:44,
>                   from libtdeldap.cpp:56:
> ../config.h:210:56: error: declaration of C function 'long unsigned int
> rk_strlcat(char*, const char*, long unsigned int)' conflicts with
> /usr/include/roken.h:146:42: error: previous declaration 'size_t
> rk_strlcat(char*, const char*, size_t)' here
> ../config.h:222:56: error: declaration of C function 'long unsigned int
> rk_strlcpy(char*, const char*, long unsigned int)' conflicts with
> /usr/include/roken.h:143:42: error: previous declaration 'size_t
> rk_strlcpy(char*, const char*, size_t)' here
>
> strlcat &  strlcpy don't appear to be defined anywhere until configure
> is run ...............
>
> checking for strlcat... no
> checking if strlcat needs custom prototype... yes - in libtdefakes
> checking for strlcpy... no
> checking if strlcpy needs custom prototype... yes - in libtdefakes
>
> .... and they are then defined in the subsequent config.h as folllows;
>
> unsigned long strlcat(char*, const char*, unsigned long);
> unsigned long strlcpy(char*, const char*, unsigned long);
>
> ...... which conflicts with '/usr/include/roken.h' as the error above
> states.
>
> Anybody know how I resolve this correctly, without manually intervening
> and modifying the auto-generated config.h?
>
> Cheers,
> Mike.

You do update automake build files before configure?
For example as is in debian rules:

	! [ -f /usr/share/libtool/ltmain.sh ] || \
	cp -f /usr/share/libtool/ltmain.sh admin/ltmain.sh
	! [ -f /usr/share/libtool/config/ltmain.sh ] || \
	cp -f /usr/share/libtool/config/ltmain.sh admin/ltmain.sh
	cp -f /usr/share/aclocal/libtool.m4 admin/libtool.m4.in
	
	make -f admin/Makefile.common cvs

What branch? Master or r14.0.x?

-- 
Slávek