| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Christopher Browne <cbbrowne(at)acm(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Buildfarm vs. Linux Distro classification |
| Date: | 2006-09-12 03:21:08 |
| Message-ID: | 20060912032108.GA8851@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Browne wrote:
> It seems to me that there is some value in putting together a script
> that tries to identify some of the interesting bits of the toolchain.
Yeah; but why not just a bunch of commands, some of which are expected
to work on any particular machine, and save the whole output as a single
string? It's not very clean, but should get the important details. To
support a "new machine," just add more commands to the script.
A simple version of this, based on your Mark 0, could be:
uname -a
$CC --version
$CC -V
$CC -v
ls -l /lib/libc.so*
No need to comment/uncomment anything.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-12 04:52:39 | Re: [HACKERS] Resurrecting per-page cleaner for btree |
| Previous Message | Tatsuo Ishii | 2006-09-12 01:06:33 | Re: pgbench is badly broken since July |