minji-um / iphone-dev

Automatically exported from code.google.com/p/iphone-dev
0 stars 0 forks source link

errors during llvm-gcc make #176

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. make LLVM_VERSION_INFO=2.0-svn-iphone-dev-0.3-svn

What is the expected output? What do you see instead?
Here's the output from my terminal
/usr/local/bin/arm-apple-darwin-ld:
/home/v1nsai/Documents/iPhone/FS//lib/libc.dylib load command 7 unknown cmd
field
collect2: ld returned 1 exit status
make[2]: *** [libgcc_s.dylib] Error 1
make[2]: Leaving directory
`/home/v1nsai/Documents/iPhone/iphone-dev/build/llvm-gcc-4.0-iphone/gcc'
make[1]: *** [stmp-multilib] Error 2
make[1]: Leaving directory
`/home/v1nsai/Documents/iPhone/iphone-dev/build/llvm-gcc-4.0-iphone/gcc'
make: *** [all-gcc] Error 2

What version of the product are you using? On what operating system?
I'm using svn version 42498 on Ubuntu 8.04.

I've made sure that HEAVENLY and LLVMOBJDIR are set properly and I just
don't know what else to try, I really appreciate any input though.

Original issue reported on code.google.com by v1n...@live.com on 4 Apr 2009 at 1:16

GoogleCodeExporter commented 8 years ago
There is already an issue post about this error. Check out issue 141 comment 
16. I
got that same error and followed what was said in that comment and it worked 
just fine.

http://code.google.com/p/iphone-dev/issues/detail?id=141

Original comment by undefinedspace on 4 Apr 2009 at 5:56

GoogleCodeExporter commented 8 years ago
I tried updating and patching everything in that post, but still getting the 
same errors

Original comment by v1n...@live.com on 4 Apr 2009 at 6:28

GoogleCodeExporter commented 8 years ago
Did you start with a fresh svn copy? I think I might have still been getting 
errors
until I did a fresh svn checkout.

Original comment by undefinedspace on 4 Apr 2009 at 10:55

GoogleCodeExporter commented 8 years ago
I checked out both svn's on the build page and still the same result.  
Strangely, I
forgot to reset HEAVENLY and LLVMOBJDIR and got the same results. I have 
heavenly set
to the location of my unpacked filesystem and LLVMOBJDIR set to the main 
llvm-svn
directory, isn't that right?  With both variables set like that, I still got 
the same
errors as in the OP.

Original comment by v1n...@live.com on 5 Apr 2009 at 3:53

GoogleCodeExporter commented 8 years ago
You used scp to get the file system, right? I have read from some that using scp
doesn't work right. Maybe try extracting the filesystem. Other than that, it 
seems
like you are doing everything right. What version of gcc/g++?

Original comment by undefinedspace on 7 Apr 2009 at 4:47

GoogleCodeExporter commented 8 years ago
Yea I tried using vfdecrypt but I haven't had any luck, I tried it on both 
linux and
windows too.  I got my hands on a VMware image of mac osx but it ran pretty 
sloppy so
I'm back to messing with this o_0

Anyway, the problem I've been having with vfdecrypt is that it simply does 
nothing. 
I enter my commands and hit enter and my cursor goes to the next line and just 
sits
there.  I've tried googling that problem in different wordings but haven't found
anything, any idea what I'm messing up with that?

Original comment by v1n...@live.com on 10 Apr 2009 at 5:24

GoogleCodeExporter commented 8 years ago
I had the same problem with vfdecrypt not doing anything. The blog I gave 
earlier:
http://pwnhome.wordpress.com/2009/03/30/the-first-steps-part-2/ talks about some
minor source editing to line 357's call to getopt that should fix the problem of
vfdecrypt not doing anything. Try that out, it worked for me! Good luck!

Original comment by undefinedspace on 10 Apr 2009 at 5:51