Re: why the c99 mandate?
I thought if was true, it was, make world, no.
Just the kernel, and the compiler, and compiler tools.
C O M P U T E R S C I E NC E
DECLARES
*Arch* = *Machine* + *Compiler*
And, while I'm here, it's, really, C89, C*BETWEEN*, and C99
I remember that from college, but I don't remember, how it
was explained in college.
I do know, that C89 means NO,
YOU DO NOT TO PAY 1000 dollars to read
some *shameful* literature. You can,
hang 2 braces, anywhere, you want.
PERIOD.
For some reason, I feel the need to go, on.
This is is not necessary in C89, see _Coding_Horror_, the
book, or the franchise, there of.
if ( 1 != 0 ) {
int xtmpxintfoo = 10;
char * giveme = argv[2];
if ( 0.1 != 1 )
{
void * ptr;
ptr= somethingthing(&xtmpxintoo, "C89NOW");
giveme= ptr+argv[1];
}
/* yeah the compiler might take that out if I don't do this*/
/* comment moved, by author */
}
And lastly, the custom of the subculture,
that is the, the mass cultural *normalism*,
imperative movement, of the late 80's
and the 90s was to, always,
maintain that C is, always,
crippled, even though,
once, one has C89, it is not.
[pkgsrc] wine-dev: freetype2 needs patching
Hello, I'm on NetBSD 8.0 amd64, and using pkgsrc-2019Q4. wine doesn't compile for amd64 so I'm trying wine-devel. But it chokes about courier.ttf, because of a bug in freetype2 introduced after 2.8. The offending bit is explained here: https://bugs.winehq.org/show_bug.cgi?id=43716 Modifying freetype2:src/sfnt/sfobjs.c and installing this reverted patched version of freetype2-2.10.1 allows to compile wine-devel. FWIW, -- Thierry Laronde http://www.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: Problems with 9.0 on x230
> On my x230, after waking up I have to switch back to the TTY on which X > is running with Ctrl + F. Somehow this seems to reset due to the state > of sleep. Try it - maybe you are lucky and it will help you too. Unfortunately, no dice. I just end up typing characters on the screen. Btw, it's kinda weird, I used to run -current a year ago (before branching 9.0) and suspend worked perfectly there. Something screwed up along the way, I guess. > Did you use WAPBL (mount option log) on the 500/1000 GB drives and not > on the 2000 GB drive? Then the difference could be due to journaling. 20 > minutes fsck does not seem to me as long for a 2 TB FFS partition, > depending on how full it is. I don't remember what I used then, but it's really long regardless of the log setting. If don't have fs checking disabled for that partition, I end up waiting 20 minutes for the Thinkpad to boot. Log or no log makes no difference.
Re: Problems with 9.0 on x230
Hello, On 12.04.20 10:35, strt32 wrote: Hi! So I installed 9.0 on my Thinkpad x230 yesterday and encountered a few problems I hope you can help me with: - somewhat broken suspend - sometimes after waking up there are random letters all over the place in the framebuffer (uncleared bits of vram?) and waking up while in X doesn't bring it up at all, I'm stuck with an empty framebuffer to play with On my x230, after waking up I have to switch back to the TTY on which X is running with Ctrl + F. Somehow this seems to reset due to the state of sleep. Try it - maybe you are lucky and it will help you too. - long fsck - I dunno why, but for some reason it takes fsck ~20 minutes to go over my 2TB drive. Maybe it's normal, but it was always almost instant for me (when working with 500GB and 1TB drives) Did you use WAPBL (mount option log) on the 500/1000 GB drives and not on the 2000 GB drive? Then the difference could be due to journaling. 20 minutes fsck does not seem to me as long for a 2 TB FFS partition, depending on how full it is. Kind regards Matthias
Problems with 9.0 on x230
Hi! So I installed 9.0 on my Thinkpad x230 yesterday and encountered a few problems I hope you can help me with: - somewhat broken suspend - sometimes after waking up there are random letters all over the place in the framebuffer (uncleared bits of vram?) and waking up while in X doesn't bring it up at all, I'm stuck with an empty framebuffer to play with - long fsck - I dunno why, but for some reason it takes fsck ~20 minutes to go over my 2TB drive. Maybe it's normal, but it was always almost instant for me (when working with 500GB and 1TB drives) - no keyfile in cgd - this is more of a question than a problem, does cgd support loading keys from keyfiles? Well, is there anything that can be done? My dmesg: https://dmesgd.nycbug.org/index.cgi?do=view&id=5452
Re: NetBeans Unexpected error: the trustAnchors parameter must be non-empty
https://packages.ubuntu.com/bionic/misc/ca-certificates-java - Reply to message - Subject: Re: NetBeans Unexpected error: the trustAnchors parameter must be non-empty Date: Wed, 8 Apr 2020, 16:17 From: Benny Siegert To: Greg Troxel > On Wed, Apr 8, 2020 at 2:45 PM Greg Troxel wrote: > > Given the Ubuntu package is > > called java-cet, I would guess that it does something to configure the > > jre. > John, could you provide more information on the Ubuntu package? I was > unable to find a trace of this package on packages.ubuntu.com. > -- Benny
