On Nov 14, 2010, at 1:26, Russ Cox r...@swtch.com wrote:
[a bunch of very reasonable stuff]
I clearly didn't write that well because Russ just disagreed with me by saying
exactly what I was trying to say: the approaches ask and answer different
questions. My main interest was to point out that
Hi Erik et. al,
Thanks for the feedback, all.
On 14 Nov 2010, at 13:24, erik quanstrom wrote:
You may well be right that there's too much momentum behind
autoconf/automake to change GNU. But that doesn't mean it's the right
thing to do, or something sensible people ought to choose to
Hello,
On Sun, Nov 14, 2010 at 09:17:46AM +0700, Gary V. Vaughan wrote:
[[resent from my subscribed email address after the mailing list rejected the
original]]
[...]
AFAICT, without rewriting the entire GNU build system from the ground
up (and there is far too much momentum behind it to
On 14 Nov 2010, at 16:10, tlaro...@polynum.com wrote:
Hello,
Hi Thierry,
On Sun, Nov 14, 2010 at 09:17:46AM +0700, Gary V. Vaughan wrote:
[[resent from my subscribed email address after the mailing list rejected
the original]]
[...]
AFAICT, without rewriting the entire GNU build system
I have been working on some improvments to webfs which I shall push out very
soon.
Webfs is good as far as it goes, but it is missing some things, different
content
encodings (gzip etc) and persistent sessions are the most obvious ones.
Basicially it is an http 1.0 client which has some 1.1
Hello Gary,
On Sun, Nov 14, 2010 at 04:32:34PM +0700, Gary V. Vaughan wrote:
[...]
Does your build system work correctly with shared libraries in Mingw,
cygwin, AIX, HP-UX (to name just a few of the more awkward under-
featured shared library implementations I care about) under various
On 14.11.2010 10:10, tlaro...@polynum.com wrote:
Furthermore, the auto* and libtool were typically made
for trying to do something working to some extend with a chaotic
source. They typically manage to compile things written by
programmers who have been encouraged to look at the finger
GNU awk is a nice piece of software. The core of
GNU grep is very well written even if the surrounding
utility has been embellished a bit too much. Groff is
when mike wrote it, gnu grep was the best thing one
could get if one wasn't at the labs. since brucee started
this, i was in the room
The full standard c library isn't included in a statically linked
executable. Only what's needed is, at least on plan 9, i have no idea what
gcc does.
On Nov 14, 2010 3:14 AM, Gary V. Vaughan g...@vaughan.pe wrote:
Hi Erik et. al,
Thanks for the feedback, all.
On 14 Nov 2010, at 13:24, erik
On Sun, Nov 14, 2010 at 7:56 AM, Jacob Todd jaketodd...@gmail.com wrote:
The full standard c library isn't included in a statically linked
executable. Only what's needed is, at least on plan 9, i have no idea what
gcc does.
To emphasize this comment: Plan 9 has always done the equivalent of
unfortunately, the last i checked, gnu grep mallocs
for each byte of input when using a utf-8 locale.
that bug was fixed in gnu grep years ago,
probably before you found and reported it.
unfortunately, linux distributions were for
many years not updating their copies of
gnu grep to the latest
Hi list!
I've been trying to install plan9 today, on a qemu vm. When trying to
install from local the installer seems unable to find quite a few files in
plan9's src directory. It seems there's some problem with the cdimage. I
tried booting from the floppy image, but got stuck at the point where
Hoping Andrey does not mind me attaching this...
Seriously, why to seek for a different boot source when cdboot works?
Boot it, run it, learn it...
2010/11/14 Eugene Gorodinsky e.gorodin...@gmail.com:
Hi list!
I've been trying to install plan9 today, on a qemu vm. When trying to
install from
IIRC, the net install thing hasn't worked for quite a while, since
almost everybody installs from a CDROM these days. Maybe try
downloading the image again? I think sometimes the image gets messed
up for a day, then the next daily rebuild fixes it. Maybe I'll try to
install on a VM later today.
I have successfully avoided using autoconf and similar stuff in my
projects by adhering to strict C99, but in an ironic twist of fate, Plan
9 will be the OS that forces me to use something like autoconf due to
the limited C99 support.
the list of unimplemented items in /sys/src/cmd/cc/c99* is:
Compound literal support is unimplemented for arrays. Also, most c99
headers are missing, even the simple ones like stdint.h. It seems most of
the work to fix that would be teaching OSTRUCT to work with arrays in
com.c
*dives back into schoolwork*
On Sun, 14 Nov 2010 21:44:07 +, Charles
unfortunately, the last i checked, gnu grep mallocs
for each byte of input when using a utf-8 locale.
that bug was fixed in gnu grep years ago,
probably before you found and reported it.
unfortunately, linux distributions were for
many years not updating their copies of
gnu grep to the
* Gary V. Vaughan g...@gnu.org wrote:
People like to beat on GNU Libtool, and in some cases that criticism is
not undeserved... but in my experience, many critics of the tool come
from a perspective of building on a single architecture.
Actually, I'm building for lots of different archs
On Nov 13, 2010, at 5:14 PM, David Leimbach wrote:
Isn't this what Apple does recommend you do with application bundles? Ship
the whole directory (.app) with all requisite frameworks and libs?
That's the recommended approach for certain types of distributions. The
alternative approach is
hi,
I am wondering what you think about the capabilities of 9p compared to
http/1.1. Perhaps this seems like an odd comparison, but I think 9p and http
are broadly similar in purpose and functionality. While writing a simple
webserver, I got to thinking that http is really a very capable
and it will be an unaswered question. o fortuna, velut luna, statu variabilis.
brucee
On Mon, Nov 15, 2010 at 1:31 PM, Jeff Sickel j...@corpus-callosum.com wrote:
On Nov 13, 2010, at 5:14 PM, David Leimbach wrote:
Isn't this what Apple does recommend you do with application bundles? Ship
Please see lsub's Op and my Streaming talk at the most recent IWP9.
Also, regarding 'cat', the behavior of many basic tools is that,
barring any file arguments, they take stdin as input and output to
stdout, so cat's behavior makes sense to me.
On Sun, Nov 14, 2010 at 10:25 PM, Sam Watkins
i'm with john
On Mon, Nov 15, 2010 at 3:20 PM, John Floren slawmas...@gmail.com wrote:
Please see lsub's Op and my Streaming talk at the most recent IWP9.
Also, regarding 'cat', the behavior of many basic tools is that,
barring any file arguments, they take stdin as input and output to
On 14 Nov 2010, at 17:50, Carl-Daniel Hailfinger wrote:
On 14.11.2010 10:10, tlaro...@polynum.com wrote:
Furthermore, the auto* and libtool were typically made
for trying to do something working to some extend with a chaotic
source. They typically manage to compile things written by
On 15.11.2010 05:29, Gary V. Vaughan wrote:
On 14 Nov 2010, at 17:50, Carl-Daniel Hailfinger wrote:
On 14.11.2010 10:10, tlaro...@polynum.com wrote:
Furthermore, the auto* and libtool were typically made
for trying to do something working to some extend with a chaotic
source. They
On Sun, Nov 14, 2010 at 11:20:00PM -0500, John Floren wrote:
Please see lsub's Op and my Streaming talk at the most recent IWP9.
Ok, thanks. I did not know that 9p has latency problems even when reading a
single file. I was talking about pipelining, where you can ask the server to
send a dozen
On Mon, Nov 15, 2010 at 12:16 AM, Sam Watkins s...@nipl.net wrote:
On Sun, Nov 14, 2010 at 11:20:00PM -0500, John Floren wrote:
Please see lsub's Op and my Streaming talk at the most recent IWP9.
Ok, thanks. I did not know that 9p has latency problems even when reading a
single file. I was
27 matches
Mail list logo
