[klibc] several messages
tg at mirbsd.de
Tue Aug 16 15:28:07 PDT 2011
maximilian attems dixit:
>> It’s probably incomplete – when building mksh on m68k with
>> it, I noticed that some tests still fail. But it’s a good
>> start. Plus it needs some assembly glue since klibc reverted
>> back to Undefined Behaviour in C which breaks here.
>You mean the variadic unfix of open(), well this was noted to
>need an m68k specific workaround, will note on the todo section.
Yes, but I think that may be not all.
>> No answer from the porters that I am aware of.
>Indeed didn't see anything yet, which is quite some time ago.
>Now that m68k troubles in linux 3.X got sorted, could you please
>repost it with a link to latest klibc git, so that they might try
Yes, will do, after FrOSCon though.
>Equally great would be a repost of that mkstemp(), afair it had
>a second round of review already.
Similarily, I’ll review, rebase and repost it after FrOSCon.
What do you prefer, “better” entropy or smaller code? I’m
tending towards the latter for klibc at the moment, unless
you really want a global RNG-like function…
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting all the prepositions
in English text in bold font. -- Rob Pike in "Notes on Programming in C"
More information about the klibc