9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: Ruby port
Date: Thu, 15 Nov 2007 18:12:38 -0500	[thread overview]
Message-ID: <0F2096E1-510E-44A4-AC46-AAE91D62FE36@mac.com> (raw)
In-Reply-To: <13426df10711141322t3eb56f10uea8cba2b23f45f03@mail.gmail.com>


On Nov 14, 2007, at 4:22 PM, ron minnich wrote:

> On Nov 14, 2007 11:25 AM, erik quanstrom <quanstro@coraid.com> wrote:
>
>> a good percentage of the stuff configured is not required.  configure
>> spends a lot of energy looking for spiffy optimizations that can  
>> safely
>> be skipped.

Configure also screws us up when it's needed. Especially when I'm  
having problems compiling software because I'm missing a library I  
don't want to take the time to install! DON'T DYNAMICALLY LINK. Good  
thing Plan 9 don't (as far as I know).

It also introduces a complication. How automated is autotools when  
you have this: see /n/sources/contrib/pietro/Autotools.png
It's how autotools works. The circles are programs you run to get a  
configure file! It should be called a portability nightmare!

And how about this in the category of pointless:

	Checking for C compiler...

Is that even necessary? Do you think someone compiling a program  
written in C would have a C compiler on them? Oh, and when you find  
out it's gcc, why does it go on to check whether or not it has  
specific flags and header files - especially standard header files,  
because I don't think you would need to ensure you have standard  
header files anyway anymore because everyone who uses anything made  
after 1990 (pretty much 99.024% of the population) use Standard C?  
Why not just assume those flags and headers are there?

I once tried to contribute to AbiWord. But Compilation using  
autotools held me back. And then I discovered troff, and that's what  
I'm using from now on (although I might make a mm to AbiWord  
converter one day). Oh how the mighty GNU have fallen.


  parent reply	other threads:[~2007-11-15 23:12 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11 20:44 [9fans] " Christopher Nielsen
2007-11-11 20:54 ` Pietro Gagliardi
2007-11-12  5:28 ` ron minnich
2007-11-12 14:19   ` David Leimbach
2007-11-12 15:40   ` [9fans] " prem
2007-11-12 19:01     ` ron minnich
2007-11-12 19:39       ` Steve Simon
2007-11-12 21:39         ` Aki Nyrhinen
2007-11-12 22:39           ` Pietro Gagliardi
2007-11-12 23:21             ` Steve Simon
2007-11-12 23:32             ` William Josephson
2007-11-12 23:55               ` Charles Forsyth
2007-11-12 23:52                 ` Pietro Gagliardi
2007-11-13  0:00                 ` William K. Josephson
2007-11-13  0:53                 ` Joel C. Salomon
2007-11-13  0:57                   ` Pietro Gagliardi
2007-11-13  1:32                     ` [9fans] Re: Ruby port ( off topic ) fernanbolando
2007-11-14 21:50                 ` [9fans] Re: Ruby port y i y u s
2007-11-13  0:27             ` Aki Nyrhinen
2007-11-13  0:33             ` David Leimbach
2007-11-13  0:35             ` Aki Nyrhinen
2007-11-13  0:50             ` [9fans] Fortran Lyndon Nerenberg
2007-11-13  0:52               ` erik quanstrom
2007-11-13  1:08                 ` Lyndon Nerenberg
2007-11-13  1:08                 ` Pietro Gagliardi
2007-11-13  1:48                   ` erik quanstrom
2007-11-13  1:12                 ` [9fans] Money, guns, and lawyers Lyndon Nerenberg
2007-11-13  1:41                   ` erik quanstrom
2007-11-13  1:59                     ` Lyndon Nerenberg
2007-11-13  2:02                       ` erik quanstrom
2007-11-14 16:55                 ` [9fans] Fortran plan9
2007-11-14 17:05                   ` erik quanstrom
2007-11-14 19:45                   ` Pietro Gagliardi
2007-11-14 20:04                     ` Uriel
2007-11-14 20:09                       ` William K. Josephson
2007-11-13  0:59         ` [9fans] Re: Ruby port Lyndon Nerenberg
2007-11-13  1:23           ` Hagen Paul Pfeifer
2007-11-13  1:25           ` Pietro Gagliardi
2007-11-14 19:05         ` ron minnich
2007-11-14 19:14           ` Latchesar Ionkov
2007-11-14 19:19             ` ron minnich
2007-11-14 19:25               ` erik quanstrom
2007-11-14 19:53                 ` Charles Forsyth
2007-11-14 20:43                   ` Robert William Fuller
2007-11-14 21:15                     ` Charles Forsyth
2007-11-14 21:22                 ` ron minnich
2007-11-14 23:04                   ` erik quanstrom
2007-11-15 23:12                   ` Pietro Gagliardi [this message]
2007-11-14 19:36               ` Bakul Shah
2007-11-14 19:45                 ` Latchesar Ionkov
2007-11-14 20:16                   ` Bakul Shah
2007-11-14 21:00                     ` Latchesar Ionkov
2007-11-14 21:12                     ` Pietro Gagliardi
2007-11-14 23:12                     ` erik quanstrom
2007-11-14 19:37               ` Federico G. Benavento
2007-11-18  3:32                 ` Pietro Gagliardi
2007-11-18 23:28                   ` Federico G. Benavento
2007-12-02 22:55 ` [9fans] " Kim Shrier
2007-12-02 23:12   ` Federico G. Benavento
2007-12-03  5:11     ` Charles Forsyth
2007-12-03  5:13       ` lucio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0F2096E1-510E-44A4-AC46-AAE91D62FE36@mac.com \
    --to=pietro10@mac.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).