rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: culliton@srg.af.mil (Tom Culliton x2278)
To: cks@hawkwind.utcs.toronto.edu, rc@archone.tamu.edu
Subject: Re: configuration parameters
Date: Fri, 14 Feb 1992 13:01:30 -0600	[thread overview]
Message-ID: <9202141401.aa10658@ceres.srg.af.mil> (raw)

>>  Can someone describe the GNU configure tool? Does it fall down on
>> strange machines? Does it force you to answer lots of chatty questions?
>> 
>> 	- cks

I've had many problems porting "Auto-configuring" GNU (etc.) stuff to
SCO Unix.  To the best of my knowledge their configure stuff is very
similar (if not identical to) Larry Wall's which also has problems with
SCO.  Admittedly SCO Unix is a bastard cross between a bull bitch and a
window shutter, (don't ask me what that means it's just something my
father used to say) and has various bugs, mis-features and down right
stupidity built in for our enjoyment, but there's a lot of it out here
in the real world.

For example... most auto-config packages deduce that SCO has a working
POSIX rename function.  BZZZZT!  Just try to use it on a NFS mounted
file system and watch the fun.

Hand editing make files usually works much better unless the number of
configuration options is about three or four times what rc has now.

Tom


             reply	other threads:[~1992-02-14 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-02-14 19:01 Tom Culliton x2278 [this message]
  -- strict thread matches above, loose matches on Subject: below --
1992-02-16 19:58 Alan Hargreaves
1992-02-17 15:35 ` jew
1992-02-14 23:20 rjc
1992-02-14 18:25 Tom Culliton x2278
1992-02-14 14:15 Rich Salz
1992-02-14  5:19 Byron Rakitzis
1992-02-14  5:33 ` Chris Siebenmann
1992-02-14 17:41   ` Brendan Kehoe
1992-02-14 18:24     ` Chris Siebenmann

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=9202141401.aa10658@ceres.srg.af.mil \
    --to=culliton@srg.af.mil \
    --cc=cks@hawkwind.utcs.toronto.edu \
    --cc=rc@archone.tamu.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).