Latest Bugs & Tasks
Fixed in hrev46994.
I have a Dell Optiplex 745 with an integrated Intel i965Q (82Q963/Q965 Integrated Graphics Controller)
I cant set a native resolution, if i boot up first time, i have to use Failsafe Videomode with, lets say 1024x768, after that i can start without using it, but iam bound to 1024x768. If i want to change to 1440x900 i get a very strange output. (This "trick" works with any VESA resolution). The TFT is connected per VGA.
Along with its switch over to DWARF 4 by default, gcc 4.8.1 has started generating info entries corresponding to rvalue reference types, which we don't currently handle. This needs to be addressed.
Furthermore, it seems it's generating DWARF 4 output without generating a separate debug_types section, which the current implementation did not anticipate. Needs further investigation.
Fixed in hrev46989.
This is actually still an issue. (one I see quite often)
The issue is due to the lack of a libroot_build.so and the usage of rm_attrs to erase files on clean. There is a situation that can exist where libroot_build.so is missing, thus rm_attrs fails to execute...
Clean clean Clean clean /home/kallisti5/Code/haiku/generated.arm/objects/linux/x86_64/release/tools/rm_attrs: error while loading shared libraries: libroot_build.so: cannot open shared object file: No such file or directory export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/kallisti5/Code/haiku/generated.arm/objects/linux/lib ; /home/kallisti5/Code/haiku/build/scripts/rm_attrs /home/kallisti5/Code/haiku/generated.arm/objects/linux/x86_64/release/tools/rm_attrs -f "/home/kallisti5/Code/haiku/generated.arm/objects/haiku/arm/release/system/libroot/posix/string/bzero.o" "/home/kallisti5/Code/haiku/generated.arm/objects/haiku/arm/release/system/libroot/posix/string/ffs.o" "/home/kallisti5/Code/haiku/generated.arm/objects/haiku/arm/release/system/libroot/posix/string/memccpy.o" "/home/kallisti5/Code/haiku/generated.arm/objects/haiku/arm/release/system/libroot/posix/string/memchr.o"...
I think the solution is to check for the existence of generated.arm/objects/linux/lib/libroot_build.so before attempting to use rm_attrs. Maybe if libroot_build.so is missing, the clean will attempt to build it.. or just fall back to rm vs rm_attrs.
The change needs to occur in build/jam/BuildSetup ~line 530.
We know the directory where libroot_build.so *should* be (HOST_BUILD_COMPATIBILITY_LIB_DIR), before setting RM to rm_attrs... we should check for libroot_build.so first, and fall back to rm if needed.
Fixed by dropping the automatic redirect back to http on logout.
As the summary states, clicking the 'Logout' link in Trac currently results in the browser indicating a redirect loop error. This has been reproduced across multiple browsers.
Ticket #10655 (Jam help target does not contain info on how to build haiku targets with ...) created
The help target of jam does not provide any information on how to build targets for specific profiles such as nightly, bootstrap and release. Adding this information would help decide which specific target is required.
This is hrev46974.
Loading this CNet website is reproducibly crashing Web+. See attached reports with and without libroot_debug.so.
Could someone please delete this idiot's account?
This is hrev46974.
After running for about 2 hours with various open tabs (mostly idling the last 30 minutes while I watched clips from youtube), Web+ crashed after closing a tab. The segment violating thread is probably the tab that was supposed to be displayed after I have closed a tab.
Web+ does not stay logged on in vbulletin and many other forums. Prior versions of webpositive worked fine with most forum software and normal logins.