Re: [coldsync-hackers] coldsync cant open connection

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

On Sun, Nov 24, 2002 at 07:44:19PM -0700, chris wrote:
> On Sun, 2002-11-24 at 19:00, Andrew Arensburger wrote:
> > 	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. 
[...]
> actually its the other way around. its vendorNo in the original
> configure.in and i changed it to udi_vendorNo

	So you did. It's a convention in the Unix world that when you
run 'diff' to get a patch, you use
		diff [options] old-version new-version
rather than
		diff [options] new-version old-version
I hadn't noticed that you had used the latter.

> > 	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?
> 
> am running freebsd-4.7-rc. have just started upgrading to the latest
> stable a little while ago.

	Then the port should automatically patch both "configure" and
"libpconn/PConnection_usb.c" to add the "udi_" prefixes.

> the port doesnt compile. it fails with
> 
> bison -y -d parser.y
> parser.y:1002.2-1010.9: type clash (`string' `') on default action
> parser.y:1010.10: parse error, unexpected ":", expecting ";" or "|"
> parser.y:1033.11: parse error, unexpected ":", expecting ";" or "|"
> *** Error code 1

	Bizarre. I can't even tell where these errors are occurring.

> > 	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.
> 
> the version i tried to build by hand is coldsync-2.2.5.
>
> heres another snippet of the error messages
> 
> gcc -Wall -ansi -pedantic -g -O2 -DHAVE_CONFIG_H -I. -I./.. -I./../include
> -I/usr/home/chris/test/include -c conduit.c
> In file included from conduit.c:14:
> /usr/include/stdlib.h:110: warning: ANSI C does not support `long long'
> /usr/include/stdlib.h:114: warning: ANSI C does not support `long long'

	Ignore these for now.
	Except, what's that "-I/usr/home/chris/test/include"? Why did
you add that?

> conduit.c:66: syntax error before `RETSIGTYPE'
> conduit.c:66: warning: type defaults to `int' in declaration of `RETSIGTYPE'
> conduit.c:66: ANSI C forbids data definition with no type or storage class

	Most likely, the symbol RETSIGTYPE hasn't been defined. Check
the "config.h" file that was created by 'configure', and make sure it
has a line that says

	#define RETSIGTYPE void

Most of the rest of the errors you got are variations on this theme.

> > 	Also, check the output of 'configure'. Did it correctly figure
> > out the return type for signal handlers?
> 
> in config.log it shows
> 
> #define RETSIGTYPE void
> 
> was this the right way to check what configure thinks RETSIGTYPE was?

	My copy of config.log doesn't have this line. I don't know why
yours does. I was thinking of the output from 'configure': it should
print a line like

	checking return type of signal handlers... void

or you could look in "config.h", which is what the code will really be
using.

-- 
Andrew Arensburger                      This message *does* represent the
arensb@ooblick.com                      views of ooblick.com
	Error: Remove disk, spit on it, insert disk and retry.

-- 
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.