Re: [coldsync-hackers] coldsync cant open connection

[chris <reddaemon at shaw dot ca>]

On Sun, 2002-11-24 at 19:00, Andrew Arensburger wrote:
> > i tried to compile coldsync by hand to see if i could get a working
> > version but i am having installation troubles.
[snip]
> 	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.

actually its the other way around. its vendorNo in the original
configure.in and i changed it to udi_vendorNo

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

the port doesnt compile. it fails with

cc -Wall -ansi -pedantic -O6 -pipe -march=pentiumpro -DHAVE_CONFIG_H -I.
-I./.. -I./../include -I/usr/local/include -c misc.c
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

the port version is coldsync-2.1.3_3. the tree was cvsupped today so it
should be the latest version of the port.

> 	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'
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
conduit.c:85: syntax error before `sigchld_handler'
conduit.c:85: warning: type defaults to `int' in declaration of `sigchld_handler
conduit.c:85: ANSI C forbids data definition with no type or storage class
conduit.c: In function `run_conduit':
conduit.c:265: syntax error before `old_sigchld'
conduit.c:370: `old_sigchld' undeclared (first use in this function)   
conduit.c:370: (Each undeclared identifier is reported only once
conduit.c:370: for each function it appears in.)
conduit.c:370: warning: passing arg 2 of `signal' from incompatible pointer type
conduit.c: At top level:
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'
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
conduit.c:85: syntax error before `sigchld_handler'
conduit.c:85: warning: type defaults to `int' in declaration of `sigchld_handler
conduit.c:85: ANSI C forbids data definition with no type or storage class
conduit.c: In function `run_conduit':
conduit.c:265: syntax error before `old_sigchld'
conduit.c:370: `old_sigchld' undeclared (first use in this function)   
conduit.c:370: (Each undeclared identifier is reported only once
conduit.c:370: for each function it appears in.)
conduit.c:370: warning: passing arg 2 of `signal' from incompatible pointer type
conduit.c: At top level:
conduit.c:1990: syntax error before `sigchld_handler'
conduit.c:1991: warning: return-type defaults to `int'
conduit.c: In function `sigchld_handler':
conduit.c:2009: warning: `return' with no value, in function returning non-void
conduit.c:2025: warning: `return' with no value, in function returning non-void
conduit.c:2081: warning: `return' with no value, in function returning non-void
gmake[1]: *** [conduit.o] Error 1
gmake[1]: Leaving directory `/usr/home/chris/coldsync-2.2.5/src'
all: Leaving directory `./src'

is this better?

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

thank you very much for your help
chris


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