[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] dbus cross compilation

From: tarek allaoua
Subject: Re: [Ltib] dbus cross compilation
Date: Tue, 5 May 2009 13:17:34 +0200

Hi Stuart,
Thank you for the answer.
I ended by removing all test related code in configure script directely, it builds and it works perfectely, i was looking for an elegant way (dbus people to cross compile and fix errors manually until it build ...).
Regarding dbus-glib i have more problems. it always try to link with my /usr/lib/ rather then the libraries presend in my rootfs. I have tried most available versions of it without success right now.

I will submit anything related to dbus and hopefully dbus-glib (if isucceed with this one..)

2009/5/5 Stuart Hughes <address@hidden>
Hi Tarek,

I've committed the attached SPEC file to Savannah CVS (and also updated packages.lkc).  In this case I pre-set the configure option to avoid the  cross-compilation intermediate executable test you ran into.

So far as dbus-glib goes, hopefully you'll be able to figure that out by looking at dbus.  If you do, please submit a patch back.

Regards, Stuart

tarek allaoua wrote:

I have asked this question previously and i'm still stuck.  I need both dbus and dbus-glib. For the moment i'm using the attached dbus.spec file.
The problem is more like configure issue then ltib itself. The error is :

checking abstract socket namespace... configure: error: in `/home/allaoua/mpc5121/ltib-mpc5121ads-20081208/rpm/BUILD/dbus-1.2.6':
configure: error: cannot run test program while cross compiling
See `config.log' for more details.
error: Bad exit status from /home/allaoua/mpc5121/ltib-mpc5121ads-20081208/tmp/rpm-tmp.44291 (%build)

The configure script has this section:

#### Abstract sockets

ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'

{ $as_echo "$as_me:$LINENO:
" >&5
$as_echo_n "checking abstract socket namespace... " >&6; }
if test "${ac_cv_have_abstract_sockets+set}" = set; then
 $as_echo_n "(cached) " >&6
 if test "$cross_compiling" = yes; then
 { { $as_echo "$as_me:$LINENO: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
{ { $as_echo "$as_me:$LINENO: error: cannot run test program while cross compiling
See \`config.log' for more details." >&5
$as_echo "$as_me: error: cannot run test program while cross compiling
See \`config.log' for more details." >&2;}
  { (exit 1); exit 1; }; }; }
 cat >conftest.$ac_ext <<_ACEOF
/* confdefs.h.  */
cat confdefs.h >>conftest.$ac_ext
cat >>conftest.$ac_ext <<_ACEOF
/* end confdefs.h.  */


As you can see the build is aborted while testing Abstract sockets during crosscompilation. I would like to know (for people who played with dbus) what cha,ges to be done to avoid this tests. I haven't seen any AC_TRY_RUN.

ltib version:
 App version  = 8.1.2
 CVS version  = 1.421.4.1

Thank you in advance.



LTIB home page:

Ltib mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]