User forums > Using Code::Blocks
ld.exe cannot find /usr/lib/libc.so.3.5
MortenMacFly:
Ok... according to this:
https://en.wikipedia.org/wiki/Microsoft_Windows_Services_for_UNIX
These tools / SDK's ship with an own compiler you have to use. Don't use any other compiler than the one provided by Microsoft. If you do, it will fail. Period. Interesting to see that I figured that out with one Google search... isn't it? >:(
eb:
This is what I get for doing 3 things at the same time...
1. I've already been through the Wikipedia entry which was why I loaded it to begin with. But as far as I can tell there is no compiler that came with it. Or at least there is no cl.exe, gcc.exe or g++.exe. There is a GCC3.3 folder but there is nothing that Code Blocks seems to recognize as a compiler.
So if this means I can not configure Code Blocks with the proper Tool chain files (compiler, linker, debugger...) then I'll try using the supplied Cshell/Korn shell (UGH!)
2. If the libs were incompatible I would have thought that Code Blocks would have given me an error telling me the libs were incompatible and not that it could not find the libs.
3. Tim I heard you the first time about not mixing libs. I'm using just the svc4unix libs on a 32 bit computer. I'm trying to build the same project with cygwin libs on a 64 bit computer. ANd I am building another computer to run Umbuntu to try this in native linux even though the CAD system this has to ultimately run under only works under windows.
All I want to know is why Code Blocks (ld.exe) can not find libcompat30.a. Is it because libcompat30.a is not compatible with ld.exe?
Sorry for being so dense. Did I mention I'n new at this?
stahta01:
--- Quote from: eb on January 31, 2012, 10:18:38 pm ---All I want to know is why Code Blocks (ld.exe) can not find libcompat30.a. Is it because libcompat30.a is not compatible with ld.exe?
--- End quote ---
Code::Blocks is neither a Compiler nor a Linker (ld.exe); you need to ask this question on a programming support site!
The people on this site does NOT have the time or likely even the Knowledge to help you on the way to mix binary objects that are NOT supposed to be mixed.
I suggest locking this thread for NOT being a Code::Blocks appropriate topic.
Tim S.
eb:
How is this NOT a CodeBlocks question?
I'm asking why CodeBlocks can not see a library (*.a) file.
I'm asking which of my CodeBlocks settings is wrong when according to everything I've read so far they are correct.
MortenMacFly:
--- Quote from: eb on January 31, 2012, 03:24:36 am ---g++.exe -LC:\SFU -o bin\Release\Rap00Unix.exe obj\Release\main.o -s C:\SFU\usr\lib\libcompat30.a C:\SFU\usr\lib\libc.so
c:/mingw/bin/../lib/gcc/mingw32/4.6.1/../../../../mingw32/bin/ld.exe: cannot find /usr/lib/libc.so.3.5
c:/mingw/bin/../lib/gcc/mingw32/4.6.1/../../../../mingw32/bin/ld.exe: cannot find /usr/lib/libcompat30.a
--- End quote ---
This all makes no sense. Most likely you have screwed the tool chain path. Here, a non-MinGW g++ executable is mixed with MinGW executables. Otherwise you would not see "cannot find /usr/lib/libc.so.3.5". Also, you need to point the linker to the folder where the libraries are in and not the base of your compiler installation.
I suggest you check you PATH environment that you don't have another compiler in the PATH and additionally check your compiler setup that you pick the right executables of one compiler distribution (that's wrong: "C:\SFU").
I strongly suggest you first try at the command line, learn how compiler/linker work and then start using an IDE. Otherwise you'll never learn how to fix such yourself. That's all I can say... seriously.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version