Latest Bugs & Tasks
Fixed in a different way in hrev50540.
Applied in hrev50540.
Agreed, thanks for the patch! I've applied it in hrev50538.
When I update Haiku via pkgman update, the following text is shown:
Continue? [yes/no] (yes) : *** please enter 'yes' or 'no'
The "(yes)" Usually means that it's the default, and that I just have to press enter to continue.
Continue? [yes/no] (yes) : y
And even if it demanded a "yes" or "no", it will happily accept a "y", too.
Applied in hrev50537. Thanks!
Added a new Patch will loads new refs and so on as a new tab after the history was loaded
Install netfs from the Haiku repository.
Modify the netfs_mount script to work... copy the file out of bin to the Desktop, change the permissions so that one may write, open in Styled edit, add #!/bin/sh as line one and mark the file executable. Double-click the file. Now there is a Networkn icon on the Desktop or in the Disks, "/" folder.
icons at 32x32
change to icon view and change the icon size to anything other than 32x32 and the Network icon either is gone or looks like a TV display that is not properly synced.
I do not know what component is at fault as I could not locate the icon.
Currently, inlined functions are more or less ignored. This can be problematic for a number of reasons though ; for instance, when a call is made to an inlined function, it is currently not possible to see the execution of that function. The requisite information to do so is present in the DWARF information generated by GCC4/5 though.
Another case that currently isn't properly handled is that gcc appears to generate a line number program that maps source lines for inlined functions that are not optimized out entirely. The line numbers are mapped to the corresponding inlined addresses in the calling function though, which plays havoc with how we currently map source lines to statements. It is currently assumed that if we could not find a function whose source line start/end map directly to the line in question, then the previous function might overlap. This behavior probably needs to be made more intelligent, though it first needs to be investigated if the debug information provides the necessary information to indicate that the function containing the inlined call does in fact include those lines as well, since they may be at an entirely different file/compilation unit from the actual function itself.
Note that the above cases are mainly only of concern when the combination of optimization and debug information is used.
Fixed in hrev50534.
ATI Radeon X1950 Pro graphics card
Graphics card is not supported - only VESA driver
ASUS A8N-VM CSM motherboard
- display showing horizontal lines during boot sequence (attached IMG_0241.JPG)
- (VGA output) native resolution of monitor (1680x1050) not supported in screen preferences (attached screenshot1.png)
- (VGA output) selecting any higher resolution than 1024x768 results in distorted image
- (DVI output) native resolution of monitor is supported in screen preferences, but Haiku auto selects 1024x768 on first boot. (attached screenshot2.png)
- (DVI output) selecting native monitor resolution (1680x1050) works OK. There are red vertical lines across the desktop. (attached screenshot3.png)
ASUS A8N-VM CSM motherboard
AMD Opteron 180 incorrectly identified in "About this system" and "Pulse" as a AMD Athlon 64.
(see attached screenshot)
Latest ffmpeg update seems to have broken something in out MediaKit.
In particular, using MediaTrack::WriteFrames produces some warnings/errors on stdout:
AVFrame.width or height is not set
AVFrame.format is not set
This is reproducible using BeScreenCapture, but also MediaConverter doesn't work anymore.
I think Haiku supports only 16 and 32 bits, but not 24. Let's close the ticket and let this old hardware this way, I think we can say "good enough" for now?
The lack of bootscreen and failure to use VESA/FailSafe video is caused by an uncompatible VESA BIOS. We could work around it but it would need lots of efforts and there's not much point now that we have a native driver.
Building with DEBUG=1 on MacOS-X yields an error;
... Undefined symbols for architecture x86_64: "_printchar", referenced from: _print_fastmap in regex.o _print_partial_compiled_pattern in regex.o _print_double_string in regex.o _regex_compile in regex.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) ...
This is because the host build-targets are requiring "gnuregex" and this library has debug code that looks for a "printchar" function which is not defined.
This patch adds a definition of this function for the purposes of sating the build process.