HELP! I am using somebody's hacked version of Cygwin to cross-compile something. I installed something yesterday and I think it broke my environment (which was compiling OK). Uninstall appears to have not reset things.
gcc calls as, but cannot find it. I get an odd error. Suppose I "gcc foo.c". I will get an error from as about foo.o having "bfd assertion fail". When I saw this in the past, it was because of cross-compile issues. But this time, foo.o does not exist. I notice that the error message is prefixed with the name of the exe file, which looks kinda like this:
C:\one\two\three/../../suddenly/slashes/point/other/way
If you parse the \ and / correctly, the as.exe file is there, but can this be right?
What environment vars could possibly change that would cause gcc or as to suddenly not work? I check the usual suspects like include and lib...and find nothing unusual.
Any help is appreciated...can add details upon request. Compiling mips-elf code on a PC. Thx
2006-09-27 03:49:22 · 2 answers · asked by sideshot72 3 in Computers & Internet ➔ Programming & Design
Sounds like you have a pretty complex setup.
"bfd assertion fail" looks like an error generated by a program called "bfd" that had an assert fail. I don't know what "bfd" is.
What do you mean by "hacked" version of Cygwin?. Have you tried reinstalling your version of Cygwin from scratch? That may be the only way to resolve the problem.
It's pretty tough to troubleshoot something like this without being there, any details you can provide might help in the diagnosis.
2006-09-29 11:22:04 · answer #1 · answered by Will 6 · 0⤊ 0⤋
do no longer save it to c:cygwinbin. Create a itemizing on your default and save it there. Run GCC from the itemizing/folder which you have created -- i.e. make effective that the source document is interior the itemizing the place you're working it.
2016-10-18 01:48:23 · answer #2 · answered by freer 4 · 0⤊ 0⤋