Bugzilla Bug 37928

When I tried to emerge multisync-0.81 and found out the palm_sync plugin wasn't
built, I tried to edit the ebuild to include it. Building the plugin dies in:

checking for pi_socket in -lpisock... yes
checking pi-socket.h usability... no
checking pi-socket.h presence... no
checking for pi-socket.h... no
configure: error: You must have the libpisock-dev package installed.

...during configure. Building the palm_sync plugin and/or multisync from the
source at their website does the same. However, the missing file is available
on my system at /usr/include/libpisock/pi-socket.h, as part of the
app-pda/pilot-link package. Compiling pilot-link from original source seems to
give the exact same file.

The only problem the ebuild seems to have, is not finding the pi-socket.h file.
I can code a little although I have no experience with C, so I'm don't know how
to solve the problem (although it seems to me this could be as easy as
adjusting a path somewhere).

For now, I'm willing to test any adjustments and offer any other help on this
ebuild :)

To reproduce:
USE="+pda" emerge multisync (using attached ebuild)

See Bug #35399, Comment #7 by Tom Hendrikx.

Ebuild: http://bugs.gentoo.org/attachment.cgi?id=23609&action=view

I to have the exact same error after doing the exact same procedure.

Hi,

I can fix the problem by amending the ebuild to set CPPFLAGS=-I/usr/include/libpisock, however I'm unsure where to correctly add the necessary CPPFLAGS declaration as just defining CPPFLAGS in the ebuild doesn't appear to be passed through. The current hack is:

  src_compile() {
+     if [ `use pda` ] ; then
+         EXTRA_ECONF="CPPFLAGS=-I/usr/include/libpisock"
+     fi
      einfo "Building Multisync with these plugins:"

...which appears to allow the palm_sync plugin to build. There is bound to be a nicer way to get this working.

*** Bug 43723 has been marked as a duplicate of this bug. ***

Seems to need a path to libpysock. If I add -I/usr/include/libpysock/ to
CFLAGS, it works. 

has the new ebuild solved this problem? if so, just close this bug :)

Is there any update on this bug?  This "new" bug  just celebrated its first
birthday. :)  Anyway, it appears multisync-0.83_pre20050115 still has the same
problem:  no palm sync.

Created an attachment (id=49635) [details]
app-pda/multisync-0.83_pre20050115 ebuild with palm support

This ebuild builds the palm_sync plugin if USE="pda". However the original bug
problem (missing CFLAGS) still is valid. To emerge this ebuild succesfully,
you'll have to specify the extra CFLAGS on the commandline:

CPPFLAGS="-I/usr/include/libpisock" emerge multisync

Note: multisync shows the plugin to me so I conclude that it builds without
problems. But since I no longer use a palm (switched to ipod), bugreaders who
do use a palm are encouraged to test the ebuild and confirm that the plugin
actually works :)

currently the .83-pre ebuild in the tree is a mixture of stable and cvs code.
There is no support for the pda/palm_sync in there in this capacity.
I will have a proper look in the coming week

Created an attachment (id=56936) [details]
app-pda/multisync/multisync-0.83_pre20050115-r1.ebuild

not sure if there is a better way to do this, but this ebuild automatically
does the CFLAGS='-I/usr/include/libpisock' for the palm_sync plugin.

(From update of attachment 56936 [details])
does not work, working on a new one

Created an attachment (id=56954) [details]
app-pda/multisync/multisync-0.83_pre20050115-r1.ebuild

Ok, this one works.  Hope it helps... Credit is given to the above comment #3
Matt Dainty.