veekays / iphonedevonlinux

Automatically exported from code.google.com/p/iphonedevonlinux
0 stars 0 forks source link

Failed to proceed from llvm gcc checkout #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Run ./toolchain.sh all or ./toolchain.sh build, or ./toolchain.sh rebuild
2. The process will stop at:  
git checkout b3dd8400196ccb63fbf10fe036f9f8725b2f0a39 

What is the expected output? 
The script should be able to proceed to the next line, instead of exit or
halting.

What do you see instead?
On ./toolchain.sh all
Simply stops at that line.

On ./toolchain.sh rebuild
error: pathspec 'b3dd8400196ccb63fbf10fe036f9f8725b2f0a39' did not match
any file(s) known to git.

What version of the product are you using? 
The latest toolchain.sh script

On what operating system?
Ubuntu

Original issue reported on code.google.com by mnemonic...@gmail.com on 7 Feb 2009 at 4:17

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Sorry, I think the issues are more on when the llvm gcc is not downloaded 
completely
from the git repo. 

Then, if we do a ./toolchain.sh rebuild, it will failed to continue the build 
process
with the pathspec error.

Original comment by mnemonic...@gmail.com on 7 Feb 2009 at 7:43

GoogleCodeExporter commented 8 years ago
Interesting, I wonder if that means it's interpreting the revision ID as a 
path. Just 
for further information, what is the output of git --version?

Thanks for the report.

Original comment by m4d...@gmail.com on 7 Feb 2009 at 2:43

GoogleCodeExporter commented 8 years ago
git version 1.5.6.3

I'm not sure about whether it's interpreting the revision ID as a path.

I'm still unable to completely download llvm-gcc-4.2 (don't know why connection 
to
this git repo is so slow), so I could not further analyze this.

Original comment by mnemonic...@gmail.com on 7 Feb 2009 at 3:31

GoogleCodeExporter commented 8 years ago
I think I may have needed to add a pull command, since a half-cloned repo isn't 
going
to like checking out a revision. This seemed to fix the issue for me.

Original comment by m4d...@gmail.com on 7 Feb 2009 at 5:45