fortunes: ./configure CFLAGS="-I$HOME/source/harvey/ape/amd64/include -I$HOME/source/harvey/ape/include -mno-red-zone -ffreestanding -fno-builtin -nostdlib -trigraphs -D_SUSV2_SOURCE -D_POSIX_SOURCE -D_LIMITS_EXTENSION -D_BSD_SOURCE -D_BSD_EXTENSION -DHAVE_SOCK_OPTS -DHARVEY -DPlan9" LDFLAGS="-static $HOME/source/harvey/ape/amd64/lib/crt1.o $HOME/source/harvey/ape/amd64/lib/crti.o $HOME/source/harvey/ape/amd64/lib/crtn.o -L$HOME/source/harvey/ape/amd64/lib -L$HOME/source/harvey/amd64/lib" LIBS="-lbsd -lap -lc" LIBM="" --prefix=$HOME/source/harvey/ape/ports *--host=x86_64-linux-gnu --build=x86_64-harvey *--enable-shared=no

This commit is contained in:
stanley lieber 2016-02-08 20:07:56 -05:00
parent 3d20565a78
commit 9c3de0c87a
5 changed files with 103 additions and 0 deletions

14
lib/rsc
View file

@ -205,3 +205,17 @@ Thank you for writing a 3rd party tool.
It's true that there are no plans yet, but I think it's also true that we need to start planning.
Yes, that's confusing.
Please do not spend time on this.
Maybe this is true, but I haven't seen it.
The fundamental design question here is whether the benefit outweighs the complexity being added.
Enough with the religion. Please.
It should just work.
Sorry for not replying earlier. I don't really know.
Great.
This seems OK.
Let's take our time and do it right (whatever that is).
Really we're just behind on triaging bugs.
I'll dig the code up and post it somewhere. I never made it truly usable.
Will follow up off list.
Wait a second.
I think it's always been this way.
I would wait until there's a more established pattern of a problem before introducing additional mechanisms.