- Aug 25, 2017
-
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
- Aug 24, 2017
-
-
Rashad Kanavath authored
note: This is awful. Thank you
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
- Aug 23, 2017
-
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
the current version is makeself has some issue on running linux particulary on Ubuntu 14.04. I suspect this is the issue on test passed (but actually failed) only on linux. Linux (passed with no output messages): https://dash.orfeo-toolbox.org/testDetails.php?test=59547315&build=287532 OSX (passed with proper messages): https://dash.orfeo-toolbox.org/testDetails.php?test=60023362&build=287444 lurking on makeself's bug tracker, it could be a umask issue https://github.com/megastep/makeself/issues/58 https://github.com/megastep/makeself/commit/842dedfe1a1477237c5132dc3615fcf50dddcc65 https://github.com/megastep/makeself/commit/e75285d90df44fb7bd80a4f727442e784f6e73c5 I am not sure if this is the exact problem and upgrade will fix issue for us. Because we are not able to reproduce this bug on same machine executed under same constraints. Only change is that one is running via crontab and other directly from terminal.
-
Rashad Kanavath authored
-
- Aug 22, 2017
-
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
- Aug 21, 2017
-
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-
Rashad Kanavath authored
GNU ld now enables -Wl,-as-needed by default. This cause issue on our side in the final package. ITK: we link with ITK_LIBRARIES which includes, itknetlib and was not linked with any of OTB module. This bug was seen in windows package testing. https://dash.orfeo-toolbox.org/testDetails.php?test=59861738&build=287155 Shark: This is another example where wl,-as-needed is causing trouble shark link with a couple of boost libraries but no of them are linked into libshark.so due to default -Wl,-as-needed. With this option, the linker will drop an lib or .so on command line if none of it's symbols are used by the project. In both cases (ITK and Shark), there are upstream issues. Shark should not add boost_system to link flags if it is not used in sharklib. Maybe this boost component is used in examples. I don't know much. It is really an upstream issue. Same case with ITK, if itknetlib is built by default, and is not necessary for the activated itk modules, it should skip that. To get back old behaviour, we have to use -Wl,no-as-needed. The other option; Wl-no-undefined is to trigger a link error if an undefined reference is found. The exact behaviour of as-needed and no-undefined can be found on GNU LD man pages (man ld).
-
Rashad Kanavath authored
C, CXX, LINKER FLAGS are not passed to sous-projects in superbuild. This is giving several issues especially when building some NEW/example module using the package. Earlier we pass these flags only for ITK and OTB. Now that it affects all of them.
-
Rashad Kanavath authored
-
Rashad Kanavath authored
-