This may set a new record for slow builds but it works just fine despite
the really really low end embedded style hardware.

$ pwd
/export/build/20090127/log
$ ls -lap
total 12
drwxr-xr-x   3 dclarke  csw            3 Feb  3 02:29 ./
drwxr-xr-x   8 dclarke  csw           12 Feb  2 20:13 ../
drwxr-xr-x   2 dclarke  csw            5 Feb  3 02:29 log.2009-02-03.02:29/
$ cd log.2009-02-03.02:29/
$ ls -lap
total 179977
drwxr-xr-x   2 dclarke  csw            5 Feb  3 02:29 ./
drwxr-xr-x   3 dclarke  csw            3 Feb  3 02:29 ../
-rw-r--r--   1 dclarke  csw         2223 Feb  3 02:29 mail_msg
-rw-r--r--   1 dclarke  csw      90881187 Feb  3 02:29 nightly.log
-rw-r--r--   1 dclarke  csw      1949637 Feb  2 20:17 proto_list_i386

$ cat mail_msg

==== Nightly distributed build started:   Sun Feb  1 23:27:14 EST 2009 ====
==== Nightly distributed build completed: Tue Feb  3 02:29:51 EST 2009 ====

==== Total build time ====

real    27:02:37

==== Build environment ====

/usr/bin/uname
SunOS aequitas 5.11 snv_106 i86pc i386 i86pc

/opt/onbld/bin/nightly ./opensolaris.sh
   PKGINST:  SUNWonbld
   VERSION:  11.11,REV=2009.01.28.18.13
    PSTAMP:  elpaso20090128181400

/opt/SUNWspro/bin/dmake
dmake: Sun Distributed Make 7.8 SunOS_i386 Patch 126504-01 2007/07/19
number of concurrent jobs = 4

32-bit compiler
/opt/onbld/bin/i386/cw -_cc
cw version 1.27
primary: /opt/SUNWspro/bin/cc
cc: Sun C 5.9 SunOS_i386 Patch 124868-08 2008/11/25
shadow: /usr/sfw/bin/gcc
gcc (GCC) 3.4.3 (csl-sol210-3_4-20050802)

64-bit compiler
/opt/onbld/bin/i386/cw -_cc
cw version 1.27
primary: /opt/SUNWspro/bin/cc
cc: Sun C 5.9 SunOS_i386 Patch 124868-08 2008/11/25
shadow: /usr/sfw/bin/gcc
gcc (GCC) 3.4.3 (csl-sol210-3_4-20050802)

/usr/java/bin/javac
java full version "1.6.0_11-b03"

/usr/ccs/bin/as
as: Sun Compiler Common 12 SunOS_i386 snv_106 12/24/2008

/usr/ccs/bin/ld
ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1639

Build project:  default
Build taskid:   99

==== Nightly argument issues ====

Warning: the N option (do not run protocmp) is set; it probably shouldn't be


==== Build version ====

Blastwave

==== Make clobber ERRORS ====


==== Make tools clobber ERRORS ====


==== Tools build errors ====


==== Build errors (DEBUG) ====


==== Build warnings (DEBUG) ====


==== Elapsed build time (DEBUG) ====

real 20:20:49.9
user 14:19:38.7
sys   3:23:22.4

==== Build noise differences (DEBUG) ====


==== Check ELF runtime attributes ====

./lib/svc/method/mmsmm: unused search path=/usr/sfw/lib  (RUNPATH/RPATH
from file /usr/postgres/8.3/lib/libpq.so.5)     <remove search path?>

==== Diff ELF runtime attributes (since last build) ====


==== 'dmake lint' of src ERRORS ====


==== Elapsed time of 'dmake lint' of src ====

real  5:46:24.5
user  4:10:56.2
sys     55:40.1

==== lint warnings src ====


==== lint noise differences src ====


==== cstyle/hdrchk errors ====


==== Find core files ====


==== Impact on file permissions ====


Why 27 hours ?  Because that ZFS filesystem had "copies" set to 2 and then
there is this :

Last login: Tue Feb  3 10:33:12 2009 from 192.168.35.44
Sun Microsystems Inc.   SunOS 5.11      Blastwave       Feb. 02, 2009
SunOS Internal Development:  dclarke 2009-02-02 [20090127]
bfu'ed from /export/build/20090127/archives/i386/nightly on 2009-02-03
Sun Microsystems Inc.   SunOS 5.11      snv_106 November 2008
You have mail.
$
$ psrinfo -pv
The physical processor has 1 virtual processor (0)
  x86 (CentaurHauls 6A9 family 6 model 10 step 9 clock 1200 MHz)
        VIA Esther processor 1200MHz
$ isalist -v
i486 i386 i86

$ su -
Password:
Sun Microsystems Inc.   SunOS 5.11      Blastwave       Feb. 02, 2009
SunOS Internal Development:  dclarke 2009-02-02 [20090127]
bfu'ed from /export/build/20090127/archives/i386/nightly on 2009-02-03
Sun Microsystems Inc.   SunOS 5.11      snv_106 November 2008
# echo "cpuid_info0::print" | mdb -k
{
    cpi_pass = 0x4
    cpi_maxeax = 0x1
    cpi_vendorstr = [ "CentaurHauls" ]
    cpi_vendor = 0x6
    cpi_family = 0x6
    cpi_model = 0xa
    cpi_step = 0x9
    cpi_chipid = 0xffffffff
    cpi_brandid = 0
    cpi_clogid = 0
cpi_ncpu_per_chip = 0x1
cpi_cacheinfo = [ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ]
cpi_ncache = 0
cpi_ncpu_shr_last_cache = 0x1
cpi_last_lvl_cacheid = 0
cpi_std_4_size = 0
cpi_std_4 = 0
cpi_std = [
{
cp_eax = 0x1
cp_ebx = 0x746e6543
cp_ecx = 0x736c7561
cp_edx = 0x48727561
}
{
cp_eax = 0x6a9
cp_ebx = 0x10800
cp_ecx = 0
cp_edx = 0xa7c9bbff
}
{
cp_eax = 0
cp_ebx = 0
cp_ecx = 0
cp_edx = 0
}
{
cp_eax = 0
cp_ebx = 0
cp_ecx = 0
cp_edx = 0
}
{
cp_eax = 0
cp_ebx = 0
cp_ecx = 0
cp_edx = 0
}
{
cp_eax = 0
cp_ebx = 0
cp_ecx = 0
cp_edx = 0
}
]
cpi_xmaxeax = 0x80000006
cpi_brandstr = [ "VIA Esther processor 1200MHz" ]
cpi_pabits = 0x24
cpi_vabits = 0x20
cpi_extd = [
{
cp_eax = 0x80000006
cp_ebx = 0
cp_ecx = 0
cp_edx = 0
}
{
cp_eax = 0
cp_ebx = 0
cp_ecx = 0
cp_edx = 0
}
{
cp_eax = 0x20202020
cp_ebx = 0x20202020
cp_ecx = 0x20202020
cp_edx = 0x20202020
}
{
cp_eax = 0x56202020
cp_ebx = 0x45204149
cp_ecx = 0x65687473
cp_edx = 0x72702072
}
{
cp_eax = 0x7365636f
cp_ebx = 0x20726f73
cp_ecx = 0x30303231
cp_edx = 0x7a484d
}
        {
            cp_eax = 0
            cp_ebx = 0x8800880
            cp_ecx = 0x40040140
            cp_edx = 0x40040140
        }
        {
            cp_eax = 0
            cp_ebx = 0
            cp_ecx = 0x80a140
            cp_edx = 0
        }
        {
            cp_eax = 0
            cp_ebx = 0
            cp_ecx = 0
            cp_edx = 0
        }
        {
            cp_eax = 0
            cp_ebx = 0
            cp_ecx = 0
            cp_edx = 0
        }
    ]
    cpi_coreid = 0
    cpi_pkgcoreid = 0
    cpi_ncore_per_chip = 0x1
    cpi_support = [ 0xa7c9bbff, 0, 0, 0, 0 ]
    cpi_chiprev = 0
    cpi_chiprevstr = 0xfe8e3a18 "Unknown"
    cpi_socket = 0
    cpi_mwait = {
        mon_min = 0
        mon_max = 0
        size_actual = 0
        buf_actual = 0
        support = 0
    }
    cpi_apicid = 0
}

I think that one could build the whole shebang on a toaster if there was a
little ram and a proc of some sort. :-)

Dennis


_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to