Can not get rsync 2.5.2 or CVS t build Solaris8/GNU RTFM
Dave Dykstra
dwd at bell-labs.com
Sat Mar 2 02:54:29 EST 2002
Where is it finding -lpopt? Is it searching any extra library directories
than the standard ones? I don't see a popt library on the Solaris 8 system
I checked. If you want it to search a non-standard directory for
libraries, you'll need to have it also search the corresponding include
directory so it can find popt.h.
- Dave Dykstra
On Wed, Feb 27, 2002 at 08:51:08AM -0800, Lancashire, Pete wrote:
> Here's what I did and the config.log, and the makefile are attached
>
> Thanks for looking into this. I hope it is something I've done.
>
> I used the CVS extract from yesterday, but I get the same problem from
> 2.5.2.
>
> rsync verson
> [root at sparky rsync-cvs]# ./rsync --version
> rsync version 2.5.3pre2 protocol version 26
> Copyright (C) 1996-2002 by Andrew Tridgell and others
> <http://rsync.samba.org/>
> Capabilities: 64-bit files, socketpairs, hard links, symlinks,
> batchfiles, no IPv6,
> 64-bit system inums, 64-bit internal inums
>
> gcc
> [root at sparky rsync-cvs]# gcc --version
> 2.95.3
>
> automake
> [root at sparky rsync-cvs]# automake --version
> automake (GNU automake) 1.4
>
> ok ...
>
> [root at sparky rsync-cvs]#make distclean
>
> first thing I see is everytime I run make I get
>
> [root at sparky rsync-cvs]# make distclean
> echo "WARNING: You need to run ./config.status --recheck"
> WARNING: You need to run ./config.status --recheck
>
> moved the config.log to config.log_old
>
> configure without any options
>
> [root at sparky rsync-cvs]#./configure
> configure: Configuring rsync 2.5.3pre2
> [chop]
> checking for poptGetContext in -lpopt... yes
> [chop]
> config.status: creating config.h
>
> rsync 2.5.3pre2 configuration successful
>
> Next the make
>
> [root at sparky rsync-cvs]# make
> echo "WARNING: You need to run ./config.status --recheck"
> WARNING: You need to run ./config.status --recheck
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c rsync.c -o rsync.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c rsync.c -o rsync.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c generator.c -o
> generator.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c receiver.c -o
> receiver.o
> receiver.c: In function `delete_already_done':
> receiver.c:58: warning: comparison between signed and unsigned
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c cleanup.c -o cleanup.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c sender.c -o sender.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c exclude.c -o exclude.o
> exclude.c: In function `get_exclude_tok':
> exclude.c:337: warning: subscript has type `char'
> exclude.c:350: warning: subscript has type `char'
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c util.c -o util.o
> util.c: In function `strlower':
> util.c:617: warning: subscript has type `char'
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c main.c -o main.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c checksum.c -o
> checksum.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c match.c -o match.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c syscall.c -o syscall.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c log.c -o log.o
> log.c: In function `log_transfer':
> log.c:574: warning: unused parameter `file'
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c backup.c -o backup.o
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c options.c -o options.o
> options.c:22: popt.h: No such file or directory
> make: *** [options.o] Error 1
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Pete Lancashire
> Unix Systems Administration
> Columbia Sportswear Co. Inc.
> PLancashire at Columbia.com
> (503) 985-4173
>
>
>
> -----Original Message-----
> From: Martin Pool [mailto:mbp at samba.org]
> Sent: Tuesday, February 26, 2002 2:34 PM
> To: Lancashire, Pete
> Cc: rsync at samba.org
> Subject: Re: Can not get rsync 2.5.2 or CVS t build Solaris8/GNU RTFM
>
>
> On 26 Feb 2002, "Lancashire, Pete" <PLancashire at columbia.com> wrote:
> > Sorry about that
> >
> > ./configure --with-included-popt
>
> It should have detected that automatically. Can you please look in
> config.log for some indication of why it did not?
>
> --
> Martin
More information about the rsync
mailing list