User forums > Using Code::Blocks
C::B new releases hung on linkage in cygwin
MortenMacFly:
--- Quote from: oBFusCATed on September 13, 2012, 12:50:54 pm ---I suppose, we have to wait for MortenMacFly to say something about it, because he has done the change.
--- End quote ---
Just noticed this thread.
--- Quote from: oBFusCATed on September 13, 2012, 12:50:54 pm ---Is it possible to provide a test project?
--- End quote ---
This is a requirement to come a step further. The modification was actually needed to really use the compiler as setup and avoid launching a wrong compiler present in the PATH. So this change should not be reverted. However, if it does something different for Cygwin we have to take care. The method used hereby is (however) a wx methods to handle PATH's. So it maybe that we have to do something "by hand" because when it comes to files/path's Cygwin even on Windows is different.
From what I see in the PATH output: Are you really on Windows, or do you cross-compile from Linux? It would be really helpful if you can provide a test project and state your OS and version of Cygwin (DLL).
littlegene:
Now the problem is ultimately clear.
Cygwin hangs on linkage as described (within its own terminal environment, not only within C::B execution) *IF* PATH set to
"/usr/bin:/:/usr/local/bin". It is a problem of cygwin.
If C::B would modify PATH to more correct
"/usr/bin:/usr/local/bin" instead , then cygwin linkage would function well.
The problem of C::B is in incorrect ("/usr/bin:/:/usr/local/bin" instead of for ex. "/usr/bin:/usr/local/bin") and, may be, unnecessary cutting off the native and very long well PATH that contains many other directories, which do not only belong to linux-like filesystem.
MortenMacFly:
--- Quote from: littlegene on September 14, 2012, 10:50:24 am ---The problem of C::B is in incorrect ("/usr/bin:/:/usr/local/bin" instead of for ex. "/usr/bin:/usr/local/bin")
--- End quote ---
I've just installed a most recent version of Cygwin. Created a console project using the Cygwin compiler - compiling and linking just works for me as it should.
If you don't provide what we asked several times now we cannot help you. Period.
oBFusCATed:
Morten: He is using a custom makefile project and it seems that the env for make is broken.
MortenMacFly:
--- Quote from: oBFusCATed on September 14, 2012, 06:26:56 pm ---Morten: He is using a custom makefile project and it seems that the env for make is broken.
--- End quote ---
Still: What is so had to provide a minimal test case? I don't see this on our side. In fact I very, very rarely use custom makefiles, so I might even do something wrong. W/O a test case I see no point in "guessing" whats wrong. In the end you can also manipulate the env-vars from the custom makefile. What, if that had happened?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version