Latest version fails to build. Scanning dependencies of target libssh2 [ 9%] Unpacking libssh2 ... [ 10%] Building libssh2 checking whether to enable maintainer-specific portions of Makefiles... no checking for sed... /bin/sed checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking libssh2 version... 1.4.3 checking build system type... i686-pc-mingw32 checking host system type... i686-pc-mingw32 configure: autobuild project... libssh2 configure: autobuild revision... 1.4.3 configure: autobuild hostname... Techlab configure: autobuild timestamp... 20140401-173417 checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for long long... yes checking if _REENTRANT is already defined... no checking if _REENTRANT is actually needed... no checking if _REENTRANT is onwards defined... no checking for library containing socket... no checking for library containing inet_addr... no checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking whether ln -s works... no, using cp -pR checking whether make sets $(MAKE)... (cached) yes checking for sshd... no checking for as... as checking for dlltool... dlltool checking for objdump... objdump checking how to print strings... printf checking for a sed that does not truncate output... (cached) /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... c:/mingw/mingw32/bin/ld.exe checking if the linker (c:/mingw/mingw32/bin/ld.exe) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /c/MinGW/bin/nm checking the name lister (/c/MinGW/bin/nm) interface... BSD nm checking the maximum length of command line arguments... 8192 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert i686-pc-mingw32 file names to i686-pc-mingw32 format... func_convert_file_msys_to_w32 checking how to convert i686-pc-mingw32 file names to toolchain format... func_convert_file_msys_to_w32 checking for c:/mingw/mingw32/bin/ld.exe option to reload object files... -r checking for objdump... (cached) objdump checking how to recognize dependent libraries... file_magic ^x86 archive import|^x86 DLL checking for dlltool... (cached) dlltool checking how to associate runtime and link libraries... func_cygming_dll_for_implib checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /c/MinGW/bin/nm output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking for dlfcn.h... no checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -DDLL_EXPORT -DPIC checking if gcc PIC flag -DDLL_EXPORT -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (c:/mingw/mingw32/bin/ld.exe) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether byte ordering is bigendian... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... unknown checking for _LARGE_FILES value needed for large files... unknown checking for ld used by GCC... c:/mingw/mingw32/bin/ld.exe checking if the linker (c:/mingw/mingw32/bin/ld.exe) is GNU ld... yes checking for shared library run path origin... done checking for libssl... no checking for libgcrypt... no configure: error: cannot find OpenSSL or Libgcrypt, try --with-libssl-prefix=PATH or --with-libgcrypt-prefix=PATH make[2]: *** [thirdparty/out/bin/libssh2-1.dll] Error 1 make[1]: *** [thirdParty/libssh2/CMakeFiles/libssh2.dir/all] Error 2 make: *** [all] Error 2 User@Techlab ~/PharoVM/pharo-vm/build $ On Tue, Apr 1, 2014 at 2:34 PM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
Hi,
in last version of sources you have a
#generateForDebug who prepares the sources for debugging. Check in the PharoVMBuilder.
Esteban
On 01 Apr 2014, at 09:02, phil@highoctane.be wrote:
On Tue, Apr 1, 2014 at 1:22 PM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
Hi,
I use CDT regularly (bah, its been like 6 months that I don't, but I use it when I need it :) ) It is not a problem with the current configuration (and debug flags), but is a bit of work for adding the source paths.
I do not know if it can be done easier... would be cool, but I don't know how feasible :)
Esteban
Now, I managed to get GDB to work with my build.
I had to change the compile options a bit (-g -O0) in the code generation and add a couple of source folders in the .gdbinit file to get the sources to show:
directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/src/plugins directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/src/vm directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/win32 directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/Cross directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/Cross/vm directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/Cross/plugins directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/win32/vm directory C:/MinGW/msys/1.0/home/User/PharoVmHeadlessWin/pharo-vm/platforms/win32/plugins break sqMain
Now it works.
But that's not really funny to work like that, so, back to the UI integration.
Esteban, do you debug with CDT with the current flags?
compilerFlagsRelease "Define NDEBUG for production to exclude asserts " ^ '-g0 -O2 -march=pentium4 -momit-leaf-frame-pointer -maccumulate-outgoing-args -funroll-loops ', '-DNDEBUG -DDEBUGVM=0'
for debugging I've set things to:
compilerFlagsDebug "Define NDEBUG for production to exclude asserts " ^ '-g -O0 -march=pentium4 ', '-DNDEBUG -DDEBUGVM=0'
and
compilerFlags "depends on config ..." ^ self commonCompilerFlags, ' ' , self compilerFlagsDebug "was Release"
I've checked that the flags were right with building with
make VERBOSE=1
in the build.sh
I am interested in looking at the startup process for the VM and getting a real windows headless system. The current one isn't working at the moment. Also, the pharo as a service should work again (is now with -DNO_SERVICE in the compilation)
I've noticed that the OSX Version supports debug options, but not Windows. Am I right?
Phil
On 01 Apr 2014, at 03:56, Torsten Bergmann <astares@gmx.de> wrote:
I'd like to know if someone managed to get Code::Blocks to work with the MinGW configuration.
No - but I think it would be good if there would be a preconfigured project for easy debugging with Eclipse CDT (C/C++ Development Tooling).
Thx T.
<DBG01-04-14 13-16-17.png>