From: Kris Van Hees <kvanhees@quarterleaf.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Silly porting fun
Date: Fri, 14 Jul 2000 09:19:49 +0000 [thread overview]
Message-ID: <slrn8mt2or.4uc.kvanhees@dev0.intra-quarterleaf.com> (raw)
In-Reply-To: <200007130836.EAA20995@cse.psu.edu>
In article <200007130836.EAA20995@cse.psu.edu>, forsyth@caldo.demon.co.uk wrote:
>>>I sometimes think so too and yet...it works so very very well and
>>>there is just so much software that uses it. I don't think I've ever
>>>seen a configure script fail in a released program.
>
>i have, frequently, on Unix systems, not Plan 9.
One example is trying to compile CVS (ironically, since it already got ported
to Plan9 without much trouble - and not using configure) on Solaris 7. At
least on all Solaris 7 machines I tried it detects that GSSAPI is available,
and then during the compilation it complains because the libraries are not
there. I believe it must be a case of Sun shipping the C include files but
not the library or something.
Anyway, it indicates how fragile configure is, even on one of the very common
Unix flavours. Another thing I truly *hate* about configure is that its small
components like the infamous config.guess script to create a identifier for the
architecture/platform it runs on cannot be used under non-GPL distribution
terms unless it is bundled with a program that contains a GNU configure script
that was generated with Autoconf. Quite a ridiculous stand for people that
claim to promote 'free' software, I think. Anyway, that widely off topic.
What I'd like to see... mk for Unix :) Anyone here who has attempted to port
it over (along with rc of course)?
Kris
next prev parent reply other threads:[~2000-07-14 9:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 8:36 forsyth
2000-07-13 16:01 ` Greg Hudson
2000-07-14 9:15 ` peter huang
2000-07-14 9:19 ` Kris Van Hees [this message]
2000-07-14 14:56 ` Douglas A. Gwyn
2000-07-17 9:11 ` [9fans] Silly porting fun (RC for Unix) Steve Simon
2000-07-17 9:11 ` [9fans] Silly porting fun Christopher Browne
-- strict thread matches above, loose matches on Subject: below --
2000-07-14 18:42 dhog
2000-07-14 14:53 Russ Cox
2000-07-14 14:04 bobf
2000-07-14 9:58 forsyth
2000-07-16 16:04 ` Lucio De Re
2000-07-14 4:18 pip
2000-07-13 23:58 rob pike
2000-07-14 9:18 ` Douglas A. Gwyn
2000-07-13 20:32 Russ Cox
2000-07-13 0:31 Russ Cox
2000-07-13 5:21 ` Randolph Fritz
2000-07-13 0:23 Russ Cox
2000-07-13 0:33 ` Christopher Nielsen
2000-07-12 23:30 forsyth
2000-07-12 23:46 ` Christopher Nielsen
2000-07-13 5:19 ` Randolph Fritz
2000-07-12 21:16 Randolph Fritz
2000-07-12 21:44 ` Latchesar Ionkov
2000-07-13 9:59 ` Douglas A. Gwyn
2000-07-13 0:38 ` arisawa
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=slrn8mt2or.4uc.kvanhees@dev0.intra-quarterleaf.com \
--to=kvanhees@quarterleaf.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).