It stopped during the orbit2 build. According to the error messages, I can make some modifications to the build parameters and continue.
I can change ORBIT_CFLAGS and ORBIT_LIBS, but the info to do this is in man pkg-config groff was one of those packages that had problems originally. This is needed to display the man pages. The build of groff (after Download) is hung with no messages yet on compiling font.cpp. I will wait a while longer.. The other package which compile messages have complained about is python. Will install that later too. Still waiting for font.cpp --- below sent previously 2 ---- My build stopped during the glib.c compile with an error: pcre_compile.c:3194 internal compiler error Segmentation Fault This looked like it might be a memory constraint problem, so I killed off the ssh session which was hanging around and then did 'cron.run' before restarting the ./scripts/Build-Target Sure enough, the build got through that step. It is still moving. It is nice that Build-Target picked up from where it left off - cleaning out the glibc .err file in the log directory, and moving on. ----- below sent previously --- I had the same problems with missing perl and missing pieces of pam (cracklib) and missing sshd user. The missing sshd user was fixed by just doing adduser (or is it useradd) for the missing user. The missing perl was a problem because perl is used in many scripts. Doing ./scripts/Emerge-Pkg perl immediately ended for some reason (this is my 2nd day with T2). I did a ls scripts and saw Build-Pkg, so I tried ./scripts/Build-Pkg perl and this also failed, but the diagnostic recommended using ./scripts/Download perl This worked and following with ./scripts/Build-Pkg perl was then also successful. I had listed out the directory /lib/security and noticed that pam_cracklib and pam_console (previously noted in some diagnostics) were missing. I did the Download and Build-Pkg on pam and that was successful, although there isn't any pam_console yet. I am now doing a ./scripts/Build-Target This seems to be building everything - starting with Tools. My host system is an old laptop from my sister with less than 300MB of memory, so I don't anticipate finishing any time soon. But, things are still moving on the screen. Perhaps I will read more of the documentation.. logging in using ssh from another system on my network, I see: r...@susie:~# uname -a Linux susie 2.6.31.4-dist #1 SMP Fri Oct 16 19:14:11 CEST 2009 i686 GNU/Linux r...@susie:~# How can I get the build number? (This is added to this message after I noticed that it originally had not been posted to the list, but just to Rebe.) The build number can be obtained (I think) by looking in: r...@susie:/usr/local/src/t2-trunk/.svn# more all-wcprops The line /t2/!svn/ver/34575/trunk seems to indicate that it is build 34575 (end of addition) ----- My initial success in using this tool (T2), I'm thinking about getting another system to dedicate to T2 development. Are there any recommendations for a fast, cheap, low electrical power system? I am partial to Asus motherboards although will do others if strongly recommended. Bob G On Sun, 2009-10-18 at 13:20 +0200, René Rebe wrote: > Hello again, > > Mika Pesu wrote: > > Hi René and T2 team, > > > > I did quick tests and so far i encountered these: > > when starting sshd service, got 'Privilege separation user sshd does > > not exist', can be solved by adding sshd user or by editing > > sshd_config, look for line UsePrivilegeSeparation. > Should be fixed by also building the user and group lists for cross builds: > > Committed revision 34577. > > > when trying to change password, passwd:module is unknown, this look > > likes its caused by missing pam_cracklib.so file > > > > also perl install is somewhat broken, Can't locate File/Glob.pm > > > > -Mika > > > > René Rebe kirjoitti: > >> > >> Hi all, > >> > >> yes, I know, it's been some time since the last T2 binary release. > >> First the university mirror shuffling out T2 binaries at TB scale was > >> to be removed, and then we just kept being very, very, ueber busy. I > >> even got married in the meantime: > >> > >> http://rene.rebe.name/just-married > >> > >> :-) > >> > >> Another good thing is, T2 progress always was rock solid, as our > >> impressive commit graph does show: > >> > >> http://svn.exactcode.de/big.png > >> > >> ChangeLog: > >> > >> http://svn.exactcode.de/ChangeLog-t2 > >> > >> > >> I now started seeding 8.0-rc ISOs for i486, x86-64, ppc, and ppc64. > >> They should show up on mirrors, soon. > >> > >> The sparc64 result has hickups with SILO being not properly loaded by > >> the OpenFirmware, that's being under review. The sparc64 iso fill > >> follow as soon as this ahs been fixed (oh, and the ppc32 ISO is not > >> yet tested, will do on my home Apple Cube tonight, but I do not > >> expect much troube). > >> > >> On a side note: the minimal builds have slightly changed. They are > >> now *all-cross-built*. Thanks to the most advanced cross compile > >> support out there that T2 does offer. This is mostly to avoid waiting > >> a week for my last, aging UltraSPARC @360MHz to build thru it, ... > >> and delaying releases anymore. > >> > >> Another side note: we're going to only release minimal binary builds > >> in the future for multiple reasons: one is that most people only need > >> parts of the X.org, KDE, GNOME etc. bits, and so everyone can build > >> the rest and save traffic, another is to cut on release cycles: we'll > >> be going to have minimal ISO builds on a regular, dependable basis, > >> just like (for example) OpenBSD. > >> > >> Have fun and a good weekend, > >> > >> Yours (truly), > >> René > >> > > > > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
