abstract-sockets problem compiling dbus with arm-linux cross compiler

[Rob Taylor]

Havoc Pennington wrote:
> Hi,
> 
> On Wed, May 14, 2008 at 8:46 PM, Soh Kam Yung <sohkamyung at gmail.com> wrote:
>> I'm also getting this cross-compile issue with abstract sockets.  How
>> do I provide the default answer (supported/not-supported) to the
>> configure script so that it can skip the check for abstract sockets?
>>
>> BTW, I noticed that this question has appeared in the dbus mailing
>> list a few times (with different answers).  Perhaps a 'definitive'
>> answer could be provided on the dbus wiki or put into the
>> README/INSTALL file.
> 
> The thing is that this is not a dbus question, this is an autoconf
> question. I for one don't know the answer, because I've never
> cross-compiled anything. But if you're doing embedded development, you
> are going to have this same question about every single package that
> uses autoconf. There is nothing special about dbus as far as I know.
> 
> So, I think the definitive answer should be put in the autoconf docs
> (and it may well already be there).

Any autoconf tests that use AC_TRY_RUN do not work when cross compiling. 
Ususally you have to set a ac_av_* environment variable for the run of 
configure, set to the appropriate setting for your target.

In this case its ac_cv_have_abstract_sockets.

Thanks,
Rob