[ 
https://issues.apache.org/jira/browse/AVRO-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Douglas Creager updated AVRO-950:
---------------------------------

    Attachment: 0001-AVRO-950.-C-Set-VERSION-correctly-in-dist-tarballs.patch

Here's a patch that fixes this.  The problem was that we were looking in 
../../share/VERSION.txt for the version number.  This works when building out 
of a SVN checkout, but doesn't in the released tarball.

The fix follows the same logic as the C++ bindings.  I've updated the dist 
script to copy VERSION.txt over to the root source directory before creating 
the tarball.  And the version.sh script looks in the current directory for 
VERSION.txt before falling back on ../../share/VERSION.txt.
                
> Avro-C library version is "undef" in release 1.6.0
> --------------------------------------------------
>
>                 Key: AVRO-950
>                 URL: https://issues.apache.org/jira/browse/AVRO-950
>             Project: Avro
>          Issue Type: Bug
>          Components: c
>    Affects Versions: 1.6.0
>         Environment: Ubuntu 11.10 x86_64
> cmake version 2.8.5
> avro-c 1.6.0
>            Reporter: Michael Cooper
>              Labels: avro, c, release
>         Attachments: 
> 0001-AVRO-950.-C-Set-VERSION-correctly-in-dist-tarballs.patch
>
>
> The version number is set to undef in the avro-c release for 1.6.0
> I downloaded the 1.6.0 tar.gz from 
> http://apache.mirror.aussiehq.net.au//avro/avro-1.6.0/c/avro-c-1.6.0.tar.gz
> {code}
> $ pkg-config --modversion avro-c
> undef
> {code}
> {code}
> $ cat /usr/local/lib/pkgconfig/avro-c.pc
> Name: avro-c
> Description: C library for parsing Avro data
> Version: undef
> URL: http://avro.apache.org/
> Libs: -L/usr/local/lib -lavro
> Cflags: -I/usr/local/include
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to