[
https://issues.apache.org/jira/browse/AVRO-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804642#action_12804642
]
Scott Banachowski commented on AVRO-374:
----------------------------------------
Hi Thiru, this is because build.sh is running autoreconf, If your version of
autotools is different version than mine, it ends up copying the files from
yours into the build directory so the build works.
I think I added this to get around warnings that were being issued by the
configure script when run on machines with different versions of autotools. If
these warnings don't really break the build, I suppose we can skip running
autoreconf and just run configure.
I'll patch that shortly.
> After a fresh 'build.sh test' svn reports certain files modified in Ubuntu
> 9.10
> -------------------------------------------------------------------------------
>
> Key: AVRO-374
> URL: https://issues.apache.org/jira/browse/AVRO-374
> Project: Avro
> Issue Type: Bug
> Components: c++
> Reporter: Thiruvalluvan M. G.
> Priority: Minor
>
> After fresh checkout and a "build.sh test", svn says certain C++ related
> files as modified:
> {code}
> M lang/c++/configure
> M lang/c++/Makefile.in
> M lang/c++/config/depcomp
> M lang/c++/config/missing
> M lang/c++/config/config.guess
> M lang/c++/config/config.sub
> M lang/c++/config/ltmain.sh
> M lang/c++/config/install-sh
> M lang/c++/config/ylwrap
> M lang/c++/INSTALL
> M lang/c++/aclocal.m4
> {code}
> It appears that these files are generated during the build and they are
> platform-dependent. If so, they should not be checked in to svn.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
