Re: Compilation error during rsync-3.0.9
On Tue 30 Apr 2013, Gauri Senad wrote: I am compiling rsync-3.0.9 in my build system (which is for 2.6.10 linux kernel. I am using windriver build system), compilation is failing due to size of “uint32” and “uint16” was computed wrongly during configuration. Hmm, it took some googling to see that windriver should be parsed as wind-river and not win-driver :-) checking size of int... (cached) 4 checking size of long... (cached) 4 checking size of long long... (cached) 8 checking size of short... (cached) 2 checking size of int16_t... 2 *checking size of uint16_t... (cached) 0* checking size of int32_t... 4 *checking size of uint32_t... (cached) 0* checking size of int64_t... 8 checking size of off_t... (cached) 8 checking size of off64_t... 8 checking size of time_t... 4 checking for inline... (cached) inline As I am new to this kind of build system I am confused, which file is referred for checking the values of variable “ac_cv_sizeof_uint32_t/checking size of uint16_t” ? As far as my study during this error debugging it seems the value is looked from the cache file. There should be no cache file present the first time you run configure. If there is, wipe the directory clean and unpack the rsync sources again, and check that there is no cache file at that point. Then rerun configure. Paul -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Compilation error during rsync-3.0.9
I am new to usage of this mailing list, I have was going through some of
the archives to see if my question is addressed already but I could find
it. I could see mostly people are discussing about issues with rsync. My
query is not much related with issues with rsync but it is related to
compilation error which I am facing with latest version of rsync.
I am compiling rsync-3.0.9 in my build system (which is for 2.6.10 linux
kernel. I am using windriver build system), compilation is failing due to
size of “uint32” and “uint16” was computed wrongly during configuration.
Output during configuration:-
checking size of int... (cached) 4
checking size of long... (cached) 4
checking size of long long... (cached) 8
checking size of short... (cached) 2
checking size of int16_t... 2
*checking size of uint16_t... (cached) 0*
checking size of int32_t... 4
*checking size of uint32_t... (cached) 0*
checking size of int64_t... 8
checking size of off_t... (cached) 8
checking size of off64_t... 8
checking size of time_t... 4
checking for inline... (cached) inline
Compilation error
In file included from
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.c:22:
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:575: warning: no
semicolon at end of struct or union
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:575: error: parse
error before node_size
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:577: error: parse
error before '}' token
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:639: warning: no
semicolon at end of struct or union
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:639: error: parse
error before unum
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:645: warning: no
semicolon at end of struct or union
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:645: error: parse
error before len32
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:646: error: parse
error before mode
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:646: warning: type
defaults to `int' in declaration of `mode'
/home/xjitgor/RSYNC-WRS1.1/pkgsrc/rsync-3.0.9/rsync.h:646: warning: data
definition has no type or storage class
As I am new to this kind of build system I am confused, which file is
referred for checking the values of variable
“ac_cv_sizeof_uint32_t/checking size of uint16_t”
? As far as my study during this error debugging it seems the value is
looked from the cache file.
However the cache file which is referred during configuration has presence
of ” ac_cv_sizeof_uint32_t/ checking size of uint16_t”
Could any one help me on understanding how and where the vaues are getting
reffred for following condidtion?
{ $as_echo $as_me:${as_lineno-$LINENO}: checking size of uint32_t 5
$as_echo_n checking size of uint32_t... 6; }
if ${ac_cv_sizeof_uint32_t+:} false; then :
$as_echo_n (cached) 6
else
if ac_fn_c_compute_int $LINENO (long int) (sizeof (uint32_t))
ac_cv_sizeof_uint32_t$ac_includes_default; then :
else
if test $ac_cv_type_uint32_t = yes; then
{ { $as_echo $as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd': 5
$as_echo $as_me: error: in \`$ac_pwd': 2;}
as_fn_error 77 cannot compute sizeof (uint32_t)
See \`config.log' for more details $LINENO 5; }
else
ac_cv_sizeof_uint32_t=0
fi
fi
fi
{ $as_echo $as_me:${as_lineno-$LINENO}: result: $ac_cv_sizeof_uint32_t 5
$as_echo $ac_cv_sizeof_uint32_t 6; }
Thanks and Regards,
Harshada Senad
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: compilation error
Sounds like your gcc is not installed properly.
- Dave Dykstra
On Mon, Oct 29, 2001 at 06:17:20PM -0500, SANJEEV wrote:
I have two machine on which I am getting this error. Both machine is Solaris
7 and rsync version I am trying is 2.4.6.
This is the error
checking whether the C compiler
(gcc -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 ) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
when I saw the config.log file. Both have almost same error.
Machine1/config.log==
configure:698: checking for gcc
configure:811: checking whether the C compiler
(gcc -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 ) works
configure:827: gcc -o conftest -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
conftest.c 15
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.0/../../../../sparc-sun-solari
s2.7/bin/ld: cannot open values-Xa.
o: No such file or directory
collect2: ld returned 1 exit status
configure: failed program was:
#line 822 configure
#include confdefs.h
main(){return(0);}
Machine2/config.log ==
configure:698: checking for gcc
configure:811: checking whether the C compiler
(gcc -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 ) works
configure:827: gcc -o conftest -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
conftest.c 15
/usr/local/sparc-sun-solaris2.7/bin/ld: cannot open values-Xa.o: No such
file or directory
collect2: ld returned 1 exit status
configure: failed program was:
#line 822 configure
#include confdefs.h
main(){return(0);}
Thanks for any help here.
-S
- Original Message -
From: Dave Dykstra [EMAIL PROTECTED]
To: SANJEEV [EMAIL PROTECTED]
Sent: Wednesday, October 10, 2001 12:03 PM
Subject: Re: compilation error
On Fri, Oct 05, 2001 at 03:50:46PM -0400, SANJEEV wrote:
While running ./configure, I got an error as below -
compiler cannot create executables
before this error , it declares that OFFSET is 64.
I also found on rsync.samba.org, which explains my problem.
Note that on some systems you will have to force configure not to use
gcc because gcc may not support some features (such as 64 bit file
offsets) that your system may support. Set the environment variable CC
to the name of your native compiler before running configure in this
case.
Now my question is how to set OFFSET -- 32 ?
Thanks.
You may get a better response if you post again listing your operating
system and rsync version number.
- Dave Dykstra
Re: compilation error
I have two machine on which I am getting this error. Both machine is Solaris
7 and rsync version I am trying is 2.4.6.
This is the error
checking whether the C compiler
(gcc -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 ) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
when I saw the config.log file. Both have almost same error.
Machine1/config.log==
configure:698: checking for gcc
configure:811: checking whether the C compiler
(gcc -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 ) works
configure:827: gcc -o conftest -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
conftest.c 15
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.0/../../../../sparc-sun-solari
s2.7/bin/ld: cannot open values-Xa.
o: No such file or directory
collect2: ld returned 1 exit status
configure: failed program was:
#line 822 configure
#include confdefs.h
main(){return(0);}
Machine2/config.log ==
configure:698: checking for gcc
configure:811: checking whether the C compiler
(gcc -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 ) works
configure:827: gcc -o conftest -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
conftest.c 15
/usr/local/sparc-sun-solaris2.7/bin/ld: cannot open values-Xa.o: No such
file or directory
collect2: ld returned 1 exit status
configure: failed program was:
#line 822 configure
#include confdefs.h
main(){return(0);}
Thanks for any help here.
-S
- Original Message -
From: Dave Dykstra [EMAIL PROTECTED]
To: SANJEEV [EMAIL PROTECTED]
Sent: Wednesday, October 10, 2001 12:03 PM
Subject: Re: compilation error
On Fri, Oct 05, 2001 at 03:50:46PM -0400, SANJEEV wrote:
While running ./configure, I got an error as below -
compiler cannot create executables
before this error , it declares that OFFSET is 64.
I also found on rsync.samba.org, which explains my problem.
Note that on some systems you will have to force configure not to use
gcc because gcc may not support some features (such as 64 bit file
offsets) that your system may support. Set the environment variable CC
to the name of your native compiler before running configure in this
case.
Now my question is how to set OFFSET -- 32 ?
Thanks.
You may get a better response if you post again listing your operating
system and rsync version number.
- Dave Dykstra
compilation error
While running ./configure, I got an error as below - " compiler cannot create executables" before this error , it declares that OFFSET is 64. I also found on rsync.samba.org, which explains my problem. Note that on some systems you will have to force configure not to usegcc because gcc may not support some features (such as 64 bit fileoffsets) that your system may support. Set the environment variable CCto the name of your native compiler before running configure in thiscase. Now my question is how to set OFFSET -- 32 ? Thanks.
