ya question on cross compiling. was: RE: [Patch] Fixing signedvs. unsigned char* warnings

Macartney, Geoff gmacartney at tycoint.com
Wed Sep 3 02:46:20 PDT 2008


Ok, thanks for the update.

Hopefully I'll get some time soon to look at this again; if I do have a success story, I'll be sure to post it!

cheers
Geoff


 
--------------------------------------------------------

Tyco Safety Products/CEM Systems Ltd.
Registered in Northern Ireland: NI 25728.  Registered Office: Unit 4 Ravenhill Business Park, Ravenhill Road, Belfast, BT6 8AW..
 
Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. This email and any attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately and delete any copies in your possession.
 
-----Original Message-----

From: dbus-bounces at lists.freedesktop.org [mailto:dbus-bounces at lists.freedesktop.org] On Behalf Of Thiago Macieira
Sent: 03 September 2008 09:58
To: dbus at lists.freedesktop.org
Subject: Re: ya question on cross compiling. was: RE: [Patch] Fixing signedvs. unsigned char* warnings

On Quarta 03 Setembro 2008 10:38:28 Macartney, Geoff wrote:
> Oh all right then :-)... so is it actually possible to cross compile
> *and* get dbus working on Arm? We've tried it and, while the compilation
> succeeds and the bus runs on the device, any attempt to connect to the
> bus fails. Compiling natively avoids this problem, and we have never got
> to the bottom of why this is.
>
> I searched the archives and have watched the list since then, and have
> seen various messages of the sort you mention, some complaining about
> inability to compile, but others describing the subsequent "can't
> connect" behaviour, and, at least from the threads I read, there didn't
> seem to be a satisfactory resolution to the problem.
>
> I was left with the impression there were known issues with dbus cross
> compilation and sucessful operation. So should it in fact be possible to
> get it going successfully after all?

Yes, of course it is. The Nokia tablets run D-Bus, so it works.

No one posts success stories though. And my feeling is that all of the people 
who post problems have since unsubscribed from the list. Whether they finally 
succeeded in making it work, we'll never know.

Also, the most I recall of issues was when people didn't set their cross-
compilation environment correctly. They ended up having the host paths in the 
default addresses for the sockets.

In other words, people didn't use configure --prefix=... and make DESTDIR=... 
install correctly.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358


More information about the dbus mailing list