ya question on cross compiling. was: RE: [Patch] Fixing signed vs. unsigned char* warnings
thiago at kde.org
Wed Sep 3 01:58:09 PDT 2008
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=...
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freedesktop.org/archives/dbus/attachments/20080903/89acdb71/attachment.pgp
More information about the dbus