This was a mistake on my part; the 0.3.2 release that was originally tagged
had a typo in it, and the tag was subsequently moved.  See this link
<https://github.com/JuliaLang/julia/commit/8227746b95146c2921f83d2ae5f37ecd146592d8>
for the proper gitsha corresponding to the 0.3.2 tag.  Finally, deleting
the tag locally (`git tag -d v0.3.2`), pulling (`git pull`), and then
checking out 0.3.2 again (`git checkout v0.3.2`) should solve this.
Alternatively, you can just checkout the latest commit on the `release-0.3`
branch, since that branch is always considered stable.  (Ironic, since I
introduced a typo onto that branch just long enough for it to get tagged
into a release)
-E

On Wed, Oct 29, 2014 at 6:14 PM, Andy Reagan <[email protected]> wrote:

> I've gotten pretty far installing 0.3.2 on a Red Hat Enterprise Linux
> cluster, reading other posts, but have hit a issue I can't find anywhere
> else. The tail of output from "make" is:
>
> Making install in tests
>> Making install in tune
>>  /bin/mkdir -p '/gpfs1/home/a/r/areagan/bin/julia/usr/share/doc/mpfr'
>>  /bin/mkdir -p
>> '/gpfs1/home/a/r/areagan/bin/julia/usr/share/doc/mpfr/examples'
>>  /usr/bin/install -c -m 644  examples/ReadMe examples/divworst.c
>> examples/rndo-add.c examples/sample.c examples/version.c
>> '/gpfs1/home/a/r/areagan/bin/julia/usr/share/doc/mpfr/examples'
>>  /usr/bin/install -c -m 644  AUTHORS BUGS COPYING COPYING.LESSER NEWS
>> TODO '/gpfs1/home/a/r/areagan/bin/julia/usr/share/doc/mpfr/.'
>> make[2]: *** No rule to make target `arpack-ng-3.1.5.tar.gz', needed by
>> `arpack-ng-3.1.5/configure'.  Stop.
>> make[1]: *** [julia-release] Error 2
>> make: *** [release] Error 2
>
>
> So far, I've had to build "as" locally, and I've prepended this to my path.
> Here are some details that might be relevant:
>
> VACC% gcc --version
>> gcc (GCC) 4.8.1
>> VACC% as --version
>> GNU assembler (GNU Binutils) 2.24
>
>
> I've tried "find . -name arpack-ng-3.1.5" and "find . -name configure" to
> try to dig up this file, but no luck.
>
> Thoughts?
>
> Best,
> Andy
>
>

Reply via email to