Re: [coldsync-hackers] coldsync cant open connection

[Andrew Arensburger <arensb+CShackers at ooblick dot com>]

On Sun, Nov 24, 2002 at 05:16:54PM -0700, chris wrote:
> hi i have been unable to get coldsync working. i installed the coldsync
> package provided by freebsd but attempts to use it result in
> 
> Error: USB support not enabled
> Error: Can't open connection

	Hm. Evidently the package maintainers decided not to include
USB support. I'm not sure why, but that's what the ports are for.

> i tried to compile coldsync by hand to see if i could get a working
> version but i am having installation troubles.
> 
> one problem is with configure. it prints
> 
> checking for BSD USB support... no
> 
> despite usb support being available. this patch makes configure work
> correctly
> 
> --- configure.in        Sun Nov 24 16:03:45 2002
> +++ configure.in.bak    Sun Nov 24 16:02:57 2002
> @@ -512,7 +512,7 @@
>         AC_TRY_COMPILE(dnl
>                 [#include <dev/usb/usb.h>],dnl
>                 [struct usb_device_info udi;
> -                udi.udi_vendorNo = 0x082d;],dnl
> +                udi.vendorNo = 0x082d;],dnl
>                 [AC_DEFINE_UNQUOTED(WITH_USB)
>                 AC_MSG_RESULT(yes)],dnl
>                 [AC_MSG_RESULT(no)])

	This is confusing. On one hand, the fact that you felt the
need to change "udi_vendorNo" to "vendorNo" indicates that you're
running 4.4 or lower. On the other hand, your patch above looks
nothing like the "configure.in" file that comes with the current
version of the port.
	Which version of FreeBSD are you running? Are you trying to
build the port? If so, are you building the latest version? Which
version of ColdSync are you building?

	You may want to forego the port (which is rather out of date)
and just grab the latest version from CVS (see
http://www.coldsync.org/ for details). Its 'configure' script should
be able to correctly figure out whether you need "udi_vendorNo" or
"vendorNo".

> i dont know how to fix the following error. i was hoping someone could
> help me here.
> 
> conduit.c:66: syntax error before `*'

	Aside from the version of ColdSync you're trying to build, it
would also be helpful to have the part of 'make's output that you
snipped, specifically the part above this that gives the command-line
options it used.
	Also, check the output of 'configure'. Did it correctly figure
out the return type for signal handlers?

-- 
Andrew Arensburger                      This message *does* represent the
arensb@ooblick.com                      views of ooblick.com
   Obviously the only rational solution to your problem is suicide.

-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.