avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Banachowski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-374) After a fresh 'build.sh test' svn reports certain files modified in Ubuntu 9.10
Date Mon, 25 Jan 2010 19:03:34 GMT

    [ https://issues.apache.org/jira/browse/AVRO-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804650#action_12804650

Scott Banachowski commented on AVRO-374:

Hmm, as I suspected the warnings cannot be ignored, as the build fails on cygwin without the
autoreconf step (it spits out errors about incompatible autoconf).

If modifying those files is really a problem, what I can try is to let the build.sh script
run configure + make, and if it fails, then try autoreconf + configure + make.  This way,
it would only effect a subset of people.  

Another way would be to copy the whole source tree to build, and then only modify the copy.

Maybe the latter is the preferred approach?

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

View raw message