User forums > Using Code::Blocks
C::B new releases hung on linkage in cygwin
littlegene:
--- Quote from: oBFusCATed on September 12, 2012, 07:43:45 pm ---What is the difference between the executed commands, if there is a difference?
--- End quote ---
Have no idea - what the difference is ;--) All executed commands are the same in ALL cases of compilationa via several C::B.: The custom Makefile is the same always and no matter which additional environment variables I use (in test cases I used none) because I did not even build for these C::B versions the envvars.dll plugin that could control the other ways of build process.
--- Quote from: oBFusCATed on September 12, 2012, 07:43:45 pm ---Also have you tried to put an env command in you makefile to see, if the environment variables are the same with the working and with the broken versions?
--- End quote ---
No, I did not try. I am not aware of how to put "env command in makefile" and for what.
Makefile was created by a special build target (within C::B) and it was created once.
--- Quote from: oBFusCATed on September 12, 2012, 07:43:45 pm ---Also is the working directory for make the same?
--- End quote ---
Of course. In any C::B I open the same .cbp, choose custom makefile option, and have no envvars that could influence...
I use the same personality profile (*.conf file) in ALL tests.
Other make.exe utilities (in other directories) just unable to compile cygwin sources. CYgwin itself is unique installation per host.
oBFusCATed:
So, if you save the build logs produced by make, they will be the same when using the two versions of C::B (broken and working)?
As you can see in the code, the compiler plugin modifies the PATH variable, it could be that it does it differently in the newer versions.
Can you try to put echo $PATH in some of the rules?
Keep in mind that I don't use cygwin or I've never used it so I have no experience with it.
littlegene:
--- Quote from: oBFusCATed on September 12, 2012, 09:04:12 pm ---So, if you save the build logs produced by make, they will be the same when using the two versions of C::B (broken and working)?
--- End quote ---
Previously I compared (visually) from the build log only the excerpts where problematic command (command that hangs) resides, but now ok - I will "file compare" in both cases all previous text lines from the log, till the line where broken compilation hangs.
(But I am still sure - no diff...s)
--- Quote from: oBFusCATed on September 12, 2012, 09:04:12 pm ---As you can see in the code, the compiler plugin modifies the PATH variable, it could be that it does it differently in the newer versions.
Can you try to put echo $PATH in some of the rules?
--- End quote ---
Will try.
--- Quote from: oBFusCATed on September 12, 2012, 09:04:12 pm ---Keep in mind that I don't use cygwin or I've never used it so I have no experience with it.
--- End quote ---
I am aware.
littlegene:
--- Quote from: oBFusCATed on September 12, 2012, 09:04:12 pm ---As you can see in the code, the compiler plugin modifies the PATH variable, it could be that it does it differently in the newer versions.
Can you try to put echo $PATH in some of the rules?
--- End quote ---
Yes! I did not guess it myself...
It is what you have described. I put echoing string in a corresponding makefile.am of my proj.
check-local:
@echo $(PATH)
and the two PATH outputs are different ;-(
The broken build process prints:
/usr/bin:/:/usr/local/bin
While the successful variant prints:
/usr/bin:/cygdrive/c/Program Files/Common Files/NetSarang:/cygdrive/c/Program Files/NVIDIA Corporation/PhysX/Common:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/d/Program Files/Bazaar:/cygdrive/c/Program Files/Microsoft SQL Server/100/DTS/Binn:/usr/local/bin:/cygdrive/c/Program Files/TortoiseSVN/bin:/cygdrive/d/Dev-Cpp/bin
Do you want for me to make a private patch for local usage with newest C::B revisions and cygwin, or you can assume to handle with the situation globally?
Thanks for you help anyway.
oBFusCATed:
--- Quote from: littlegene on September 13, 2012, 12:45:19 pm ---Do you want for me to make a private patch for local usage with newest C::B revisions and cygwin, or you can assume to handle with the situation globally?
--- End quote ---
I suppose, we have to wait for MortenMacFly to say something about it, because he has done the change.
Is it possible to provide a test project?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version