Okay, I installed Cygwin, downloaded vb_v810_gcc_03.tar.gz, unzipped the files in c:\cygwin\home\dasi\vb_v810_gcc_03, and ran ./make_v810.sh. Everything built successfully.
I had an issue building the latest gccvb using these steps which took me several hours to figure out so here’s my solution in case anyone else runs into the same problem:
If you’re like me, you may install Cygwin so that it uses DOS line endings instead of UNIX ones (I had it setup this way for a CS teaching asst. position I held at school). The problem with this is that the build process for binutils reads the CR character as part of the bfd_v810_arch definition, so you end up getting a linker error when building binutils complaining about an undefined reference to _bfd_v810_arch .
The solution to this, according to this page, is to run the following commands in the Cygwin bash shell before ./make_v810.sh :
set -o igncr
export SHELLOPTS
This sets up the environment to ignore the CR character, and allows binutils to build without error. If you setup Cygwin to use UNIX line endings (I think that’s the default) then as far as I know these commands will have no effect, but I haven’t tested that.
HTH. It sure took me a long time to figure this out. 🙂
Hi guys, I was trying to incorporate metaprogramming to my engine to being able to use class inheritance and found the cause to the problem about gccvb complaining because of the ‘\’ character in header files, it’s not gcc fault’s but Windows, since Microsoft alwasy like to do thing their on way, everytime you create a text file in windows it appends a special character to the end of each line, that character is interpreted as control character ^M by gnu progrmas, which makes gcc output an error.
There are some ways to solve this involving mounting the filesystem in some strange format, but here is an easier solution, I’ve attached a shell script which will take rid of those control characters in all your sources, you could make it being executed by your makefile before it compiles each source.
has anyone successfully built the new gccvb on vista yet? i am using a full cygwin installation and follow the guide, but keep getting the following error:
/bin/sh: line 5: C:gccvbbin: command not found
make: *** [all-libiberty]
Error 127 Error: building binutils
KR155E wrote:
has anyone successfully installed the new gccvb on vista yet? i am using a full cygwin installation and follow the guide, but keep getting the following error:
/bin/sh: line 5: C:gccvbbin: command not found
make: *** [all-libiberty]
Error 127 Error: building binutils
I think Cygwin interprets the backslashes in “C:\gccvb\bin” as escape characters… I ran into this problem and changed the path to a UNIX-style “/c/gccvb/bin” — note the use of forward slashes. This seemed to fix my build errors.
I also have MSYS installed which I think allows the C:\ = /c convention to work, so you might have to use /cygdrive/c instead.
hey blitter, how did you actually change the path? i executed the script up to the point where i get the error, and used ultra edit to replace all occurences of “C:\gccvb\bin” with “/cygdrive/c/gccvb/bin”, then continued, but still get the exact same error.
KR155E wrote:
hey blitter, how did you actually change the path? i executed the script up to the point where i get the error, and used ultra edit to replace all occurences of “C:\gccvb\bin” with “/cygdrive/c/gccvb/bin”, then continued, but still get the exact same error.
I have C:\cygwin\bin added to my PATH in Windows, as well as created a variable GCCVB that contains “/c/gccvb” — you can change these variables by going to My Computer->Properties->Advanced->Environment Variables in XP.
I’ve built the toolchain in Vista once before and I believe the procedure is very similar. You shouldn’t have to change anything in the tarball or the make_v810.sh script at all.
