From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] a quick and simple minded study of configure.
Date: Fri, 15 Jun 2007 14:15:48 -0700 [thread overview]
Message-ID: <13426df10706151415s3f523d95x7256f098bdab9a7@mail.gmail.com> (raw)
Plan 9 ports is portable to many systems. I did the following very
stupid command:
wc `find . -print | egrep
'Darwin|freebsd|FreeBSD|linux|Linux|power|386|NetBSD|OpenBSD|SunOS'`
I.e. just wc all the files that have a name that looks in any way os
or architecture dependent.
Note how unfair this is. It may count the same file twice, it counts
CVS, and so on. Very, very unfair.
Sum:
11219 34549 240528 total
Now, two popular MPIs:
first, LAM
rminnich@xcpu lam-7.1.3]$ wc ./configure
45815 164201 1362823 ./configure
Yes, that is not a typo: 45KLOC. The configure script is about 4x the
size of ALL the portability support in p9p. Makefiles are around 1029
lines. Most of that is configure goo.
For openmpi, a popular mpi:
[rminnich@xcpu openmpi-1.2.2]$ wc configure
152939 581569 5028307 configure
[rminnich@xcpu openmpi-1.2.2]$ wc Makefile
1541 5368 62023 Makefile
[rminnich@xcpu openmpi-1.2.2]$
Yes, 153KLOC of shell script for the configure. A factor of 3 growth
over the one done four years ago for LAM.
Yow. The generated makefiles average about 1500 lines. The configure
scripts take about 5 minutes to run.
I know we have some faculty on this list. Please talk to your students :-)
This is nuts.
ron
next reply other threads:[~2007-06-15 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 21:15 ron minnich [this message]
2007-06-15 21:18 ` Francisco J Ballesteros
2007-06-15 21:23 ` Rob Pike
2007-06-16 1:18 ` David Leimbach
2007-06-16 4:39 ` Skip Tavakkolian
2007-06-16 5:58 ` Bruce Ellis
2007-06-16 15:34 ` David Leimbach
2007-06-17 7:06 ` Martin Neubauer
2007-06-17 23:58 ` Uriel
2007-06-18 2:25 ` David Leimbach
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=13426df10706151415s3f523d95x7256f098bdab9a7@mail.gmail.com \
--to=rminnich@gmail.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).