Custom Query (16363 matches)
Results (2149 - 2151 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10160 | fixed | Compile virtual box with gcc 4.7 | ||
| Description |
Hi, has you may know for Fedora 17 will have packages rebuild with gcc 4.7, I try build VB with gcc 4.7, patch in attach.
In file included from /usr/include/string.h:642:0, from /builddir/build/BUILD/VirtualBox-4.1.8_OSE/include/iprt/string.h:87, from /builddir/build/BUILD/VirtualBox-4.1.8_OSE/src/VBox/Runtime/testcase/tstMemAutoPtr.cpp:33: /usr/include/bits/string3.h:77:28: note: 'void* memset(void*, int, size_t)' declared here, later in the translation unit In file included from /builddir/build/BUILD/VirtualBox-4.1.8_OSE/src/VBox/Runtime/testcase/tstMemAutoPtr.cpp:30:0: /builddir/build/BUILD/VirtualBox-4.1.8_OSE/include/iprt/cpp/mem.h: In instantiation of 'RTCMemAutoPtr<T, a_fnDestruct, a_fnAllocator>::RTCMemAutoPtr(size_t, bool) [with T = char; void (* a_fnDestruct)(T*) = RTCMemEfAutoFree<char>; void* (* a_fnAllocator)(void*, size_t, const char*) = RTMemEfReallocNP; size_t = long unsigned int]': /builddir/build/BUILD/VirtualBox-4.1.8_OSE/src/VBox/Runtime/testcase/tstMemAutoPtr.cpp:163:82: required from here /builddir/build/BUILD/VirtualBox-4.1.8_OSE/include/iprt/cpp/mem.h:172:13: error: 'memset' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation }}} |
|||
| #12011 | invalid | Compiling BIOS requires Open Watcom compiler | ||
| Description |
VirtualBox-OSE was recently removed from GNU/Linux distros ( https://www.gnu.org/gnu/gnu-linux-faq ) due to a compliance issue. It is required to use the non-free OpenWatcom compiler to make the software. Please help find or adjust the compiling process so that this very useful software can be included again by NOT use OpenWatcom during the compile process. Thank you! |
|||
| #8838 | fixed | Compiling Boost C++ libraries with 8 threads causes VM to reboot | ||
| Description |
VM is 64-bit Debian Squeeze running in 32-bit Vista host. Give the VM 768MB-1.3GB of memory (tried varying it to see if it would help) and run the following command to build the Boost C++ libraries: bjam --prefix=/usr/local -j 8 --without-mpi --without-python cxxflags=--no-strict-aliasing toolset=gcc variant=release --layout=tagged link=static,shared threading=single,multi -d 2 Doing -j 2 or using the default of 1 thread seems to work fine. The VM should give an out of memory error instead of what it does now. Eventually, the Boost build will lock up so the screen in the VM goes black and your cursor is sometimes visible. Other times, the VM will spontaneously reboot. One time, I saw VirtualBox totally crash. I think this is happening because compiling w/ multiple gcc threads is very memory and it runs out of memory. Swap is set to 720MB but it doesn't seem to be used much. |
|||

