T2 IRC Log: 2010-07-31

This is the log as captured by an IRC bot in the channel. The statements are those of the individual people and might not neccessarily reflect the policy and legal rules as set forth by the T2 SDE Project.

« prev | next »

--- Log opened Sat Jul 31 00:00:49 2010
03:19 -!- uid9909 [~uid9099@2001:470:9a41:107:2043:3e57:ca55:d2c3] has joined #t2
05:26 -!- uid9909 [~uid9099@2001:470:9a41:107:2043:3e57:ca55:d2c3] has quit [Quit: ChatZilla 0.9.86 [Firefox 3.6.8/20100722155716]]
06:41 -!- Netsplit *.net <-> *.split quits: koan
06:41 -!- koan_ [~koan@unaffiliated/koan] has joined #t2
07:47 < rogermason> Hello. I seem to have a broken build. When I run ./scripts/Build-Target -cfg syslinux_minimal I get a lot of output with lines like: Searching for old lingering files ...
07:47 < rogermason> !> build/syslinux_minimal-9.0-trunk-generic-x86-i686-linux/TOOLCHAIN/pkgs/boehm-gc-7.1.tar.bz2 should not be present (now in src/invalid-files.lst)!
07:48 < rogermason> Running ./scripts/Create-ISO withX syslinux_minimal
07:49 < rogermason> results in Not a valid build:
07:49 < rogermason> syslinux_minimal
07:49 < rogermason> build/syslinux_minimal-9.0-trunk-generic-x86-i686-linux/TOOLCHAIN/isofs.txt
07:49 < rogermason> must exist.
07:50 < rogermason> I hope I don't have to abandon this build and start again. I've been working on it since Jul 23rd.
08:51 -!- mjungwirth2 [~mjungwirt@213.174.252.112] has joined #t2
09:44 -!- koan_ is now known as koan
10:55 -!- rogermason [~user@gem.esd.mun.ca] has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
11:00 -!- rogermason [~user@gem.esd.mun.ca] has joined #t2
11:02 < rogermason> Hello. When I try to build an iso image I get this message: Not a valid build: syslinux_minimal
11:03 < rogermason> build/syslinux_minimal-9.0-trunk-generic-x86-i686-linux/TOOLCHAIN/isofs.txt must exist.
14:05 -!- uid9909 [~uid9099@2001:470:9a41:107:2001:b9b9:1eeb:9896] has joined #t2
15:13 <@rxr> re
15:51 < rogermason> I'm trying to find out why isofs.txt isn't being written but I can't find which script is responsible for writing it.
16:43 <@rxr> at the end of a _successful_ build
16:44 <@rxr> target/share/{install,livecd}/build.sh et al.
16:54 < rogermason> What does successful mean? No failures? No failures of critical packages? How do I figure out what stopped build.sh et al from running?
16:55 <@rxr> packages failures don't matter
16:55 <@rxr> but if there is some error (in any tool) at the end of the build doing the post-processing, then the scripts may drop out with an error before the isofs.txt is written
17:01 < rogermason> Is there a way to find out which tool errored out?
17:02 <@rxr> do you see an error at the end of Build-Target?
17:02 <@rxr> may you changed the output setting to initrd or none? only install and live outputs get the isofs stuff
17:07 < rogermason> The output setting is install CD. I _have_ turned it on and off while messing around. I''l send output from Build-Target to the mailing list.
21:25 -!- uid9909 [~uid9099@2001:470:9a41:107:2001:b9b9:1eeb:9896] has quit [Quit: ChatZilla 0.9.86 [Firefox 3.6.8/20100722155716]]
--- Log closed Sun Aug 01 00:00:49 2010