Activity for Peter J. Mello
-
Peter J. Mello posted a comment on ticket #309
Excellent catch, that was indeed the issue, and your suggestions both moved me past the failure. It sucks that GNU didn't agree on a remediation approach in time for the v14.2 release; it's now pushed back to v15 provided they can arrive at some consensus. I'm much obliged to you all the same, though.
-
AdvanceCOMP fails to build from source using GCC v14
-
-
*Gene Wilder yell from Young Frankenstein* It's alive!!!!!!!!!!!!!!! Hallelujah, someone way smarter than me was able to sniff out the root of this evil! I was so thrilled when mouse support was added and similarly crushed when it was broken in such an insidious way that movement either up or to the left worked, but caused the cursor to disappear if in the other two cardinal directions. Now that I know it was an integer size issue it makes perfect sense that movement which requires incrementing either...
-
Update to dh compat level 10
-
Update to dh compat level 10
-
*Gene Wilder yell from Young Frankenstein* It's alive!!!!!!!!!!!!!!! Hallelujah, someone way smarter than me was able to sniff out the root of this evil! I was so thrilled when mouse support was added and similarly crushed when it was broken in such an insidious way that movement either up or to the left worked, but caused the cursor to disappear if in the other two cardinal directions. Now that I know it was and integer size issue it makes perfect sense that movement which requires incrementing...
-
*Gene Wilder yell from Young Frankenstein* It's alive!!!!!!!!!!!!!!! Hallelujah, someone way smarter than me was able to sniff out the root of this evil! I was so thrilled when mouse support was added and similarly crushed when it was broken in such an insidious way that movement either up or to the left worked, but caused the cursor to disappear if in the other two cardinal directions. Now that I know it was and integer size issue it makes perfect sense that movement which requires incrementing...
-
This is a complete shot in the dark without knowing precisely which chipset it has, but I believe at least part of the solution is going to involve pressing the 'e' key on the GRUB menu entry you're using and adding pci=nomsi to the end of the kernel boot parameters line. If that alone doesn't alleviate your problem, then you'll likely need to append one of the anti-APIC parameters to it as well, either noapic, nolapic or nox2apic (the last one has always been my ace-in-the-hole, honestly). Make...
-
Create project hierarchy prior to importing frontline source code
-
Publish script in Files tab
1