T2 IRC Log: 2009-06-04
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.
--- Log opened Thu Jun 04 00:00:33 2009
00:52 -!- the_rainbow [n=ee@41.209.167.146] has left #t2 []
03:10 -!- mqueiros [n=mqueiros@217.70.71.7] has joined #t2
08:49 -!- Negher [n=negher@217.12.176.10] has joined #T2
16:47 -!- the_rainbow [i=ee@41.209.167.149] has joined #t2
17:10 -!- Negher [n=negher@217.12.176.10] has quit ["Vado."]
17:38 -!- kfries [n=kfries@71.216.94.233] has joined #t2
17:39 < kfries> Hey, I think I found my build problem from yesterday, got a T2 build going on right now, thanks for all the help, the problem was in a kludge that was done to make an LFS build work
17:40 < kfries> New Question: My new build is based on minimal embedded -- how can I make that build with Upstart instead of SysV Init?
18:17 -!- synchris_ [n=synchris@athedsl-200650.home.otenet.gr] has joined #t2
18:18 < kfries> My new build is based on minimal embedded -- how can I make that build with Upstart instead of SysV Init?
18:23 < koan> hm I don't know if upstart is already in T2
18:24 < kfries> It claims to be, but it does not show up in the configuration.
18:24 < kfries> www.t2-project.org/packages/upstart.html
18:27 < koan> hm I suppose noone has tried it in T2 :)
18:28 < koan> rxr can surely tell you how to do it, but he seems to be in taipei now
18:29 < kfries> SJR has claimed Linux boots in as little as 8.5 seconds from cold... I am building an embedded router, and would love to have that type of startup speed. I just don't know how to get T2 to include it instead of SysV
18:31 < kfries> DAMN! my T2 build died again, this time on uclibc it claims errors, but only warnings are getting logged! errrrrr!!!!
18:33 -!- synchris [n=synchris@pdpc/supporter/professional/synchris] has quit [Read error: 110 (Connection timed out)]
18:34 < kfries> Though it does say "You should not call uname during the build!" could that be why its failing? Its not marked as an error, but nothing is, so can I assume it is counting this as an error?
18:39 < koan> hm I have seen this warning countless times without giving problems
18:43 < the_rainbow> yes, I confirm that this warning has nothing to do with the errors you're getting
18:45 < mqueiros> kfries: what kind of hardware are you using for your embedded router project? It's something I would like to try to do myself...
18:46 < kfries> All I know is that no errors are getting printed, this message is showing up 16 times, and my compile fails with "Due to previous errors.--- BUILD ERROR ---"
18:47 < kfries> mqueiros: We are using this for prototype http://www.seco.it/en/item/secocq7-pitx/
18:48 < mqueiros> nice
18:50 < kfries> mqueiros: Then for the wireless, we are using http://www.unex.com.tw/product/dnma-92
18:50 < kfries> It runs on the Atheros 9x chipset
18:52 < mqueiros> atheros usally as some great chipsets
18:52 < kfries> oops, picked the wrong link, the chip we have is http://www.unex.com.tw/product/dnxa-95
18:53 < kfries> Similar
18:59 < kfries> Any hints on what I can try to figure out why uclibc does not compile?
19:01 < mqueiros> did you checked the logs ?
19:01 < kfries> sudo grep -i error build/default-8.0-trunk-embedded-minimal-x86-i486-cross/var/adm/logs/1-uclibc.err
19:01 < kfries> CC libc/sysdeps/linux/i386/__syscall_error.os
19:01 < kfries> CC libc/misc/error/err.os
19:01 < kfries> CC libc/misc/error/error.os
19:01 < kfries> CC libc/stdio/perror.os
19:01 < kfries> CC libc/stdio/ferror.os
19:01 < kfries> CC libc/stdio/ferror_unlocked.os
19:01 < kfries> CC libc/string/__glibc_strerror_r.os
19:01 < kfries> CC libc/string/__xpg_strerror_r.os
19:01 < kfries> CC libc/string/strerror.os
19:01 < kfries> CC libc/inet/rpc/clnt_perror.os
19:01 < kfries> CC libc/inet/herror.os
19:02 < kfries> CC libc/inet/gai_strerror.os
19:02 < kfries> usr/include/error.h: glibc uclibc
19:02 < kfries> Due to previous errors.
19:02 < kfries> --- BUILD ERROR ---
19:02 < kfries> Yep, no help
19:02 < mqueiros> there should be some more verbose log file under /var/adm/log
19:05 < mqueiros> sorry... you where already looking at it...
19:07 < kfries> Yea, and they are not showing any errors, which makes this a cruel came of guess the bug, lol
19:10 < kfries> Funny thing is that this is failing not the first time, but on recompile, on the second compilation. makes me think there is another package actually at fault, but it should still throw an error indicating what this package is missing
19:12 < mqueiros> did you added any new package between the two compilations ?
19:16 < kfries> No, the first compile is used to establish a clean environment, the second compile is to build the real version that will get installed on the target device. The two compiles come from the same Build-Target command
19:18 < mqueiros> ok. use something like pastebin and paste the full log of 1-uclibc.err Maybe you missed something...
19:22 < kfries> OK, hopefully you are right and I am just brain dead, here is the log http://pastebin.com/m7c3b9265
19:35 < kfries> I keep at it, and..... nothing, I just don't see the error. Not sure what to do to fix
19:37 < mqueiros> just a couple of warnings, but no error...
19:39 < kfries> Yep, except for that big one at the end that says I won't continue because I'm hallucinating non-existent errors
19:40 < mqueiros> yes... but no error before that one
19:47 < kfries> OK, think I need to walk down and get some lunch to clear my head and less my frustration... thanks for the help
19:48 < mqueiros> ok! later!
22:30 -!- synchris_ is now known as synchris
23:13 -!- the_rainbow [i=ee@41.209.167.149] has quit [Remote closed the connection]
23:54 -!- kfries [n=kfries@71.216.94.233] has quit [Remote closed the connection]
--- Log closed Fri Jun 05 00:00:33 2009
00:52 -!- the_rainbow [n=ee@41.209.167.146] has left #t2 []
03:10 -!- mqueiros [n=mqueiros@217.70.71.7] has joined #t2
08:49 -!- Negher [n=negher@217.12.176.10] has joined #T2
16:47 -!- the_rainbow [i=ee@41.209.167.149] has joined #t2
17:10 -!- Negher [n=negher@217.12.176.10] has quit ["Vado."]
17:38 -!- kfries [n=kfries@71.216.94.233] has joined #t2
17:39 < kfries> Hey, I think I found my build problem from yesterday, got a T2 build going on right now, thanks for all the help, the problem was in a kludge that was done to make an LFS build work
17:40 < kfries> New Question: My new build is based on minimal embedded -- how can I make that build with Upstart instead of SysV Init?
18:17 -!- synchris_ [n=synchris@athedsl-200650.home.otenet.gr] has joined #t2
18:18 < kfries> My new build is based on minimal embedded -- how can I make that build with Upstart instead of SysV Init?
18:23 < koan> hm I don't know if upstart is already in T2
18:24 < kfries> It claims to be, but it does not show up in the configuration.
18:24 < kfries> www.t2-project.org/packages/upstart.html
18:27 < koan> hm I suppose noone has tried it in T2 :)
18:28 < koan> rxr can surely tell you how to do it, but he seems to be in taipei now
18:29 < kfries> SJR has claimed Linux boots in as little as 8.5 seconds from cold... I am building an embedded router, and would love to have that type of startup speed. I just don't know how to get T2 to include it instead of SysV
18:31 < kfries> DAMN! my T2 build died again, this time on uclibc it claims errors, but only warnings are getting logged! errrrrr!!!!
18:33 -!- synchris [n=synchris@pdpc/supporter/professional/synchris] has quit [Read error: 110 (Connection timed out)]
18:34 < kfries> Though it does say "You should not call uname during the build!" could that be why its failing? Its not marked as an error, but nothing is, so can I assume it is counting this as an error?
18:39 < koan> hm I have seen this warning countless times without giving problems
18:43 < the_rainbow> yes, I confirm that this warning has nothing to do with the errors you're getting
18:45 < mqueiros> kfries: what kind of hardware are you using for your embedded router project? It's something I would like to try to do myself...
18:46 < kfries> All I know is that no errors are getting printed, this message is showing up 16 times, and my compile fails with "Due to previous errors.--- BUILD ERROR ---"
18:47 < kfries> mqueiros: We are using this for prototype http://www.seco.it/en/item/secocq7-pitx/
18:48 < mqueiros> nice
18:50 < kfries> mqueiros: Then for the wireless, we are using http://www.unex.com.tw/product/dnma-92
18:50 < kfries> It runs on the Atheros 9x chipset
18:52 < mqueiros> atheros usally as some great chipsets
18:52 < kfries> oops, picked the wrong link, the chip we have is http://www.unex.com.tw/product/dnxa-95
18:53 < kfries> Similar
18:59 < kfries> Any hints on what I can try to figure out why uclibc does not compile?
19:01 < mqueiros> did you checked the logs ?
19:01 < kfries> sudo grep -i error build/default-8.0-trunk-embedded-minimal-x86-i486-cross/var/adm/logs/1-uclibc.err
19:01 < kfries> CC libc/sysdeps/linux/i386/__syscall_error.os
19:01 < kfries> CC libc/misc/error/err.os
19:01 < kfries> CC libc/misc/error/error.os
19:01 < kfries> CC libc/stdio/perror.os
19:01 < kfries> CC libc/stdio/ferror.os
19:01 < kfries> CC libc/stdio/ferror_unlocked.os
19:01 < kfries> CC libc/string/__glibc_strerror_r.os
19:01 < kfries> CC libc/string/__xpg_strerror_r.os
19:01 < kfries> CC libc/string/strerror.os
19:01 < kfries> CC libc/inet/rpc/clnt_perror.os
19:01 < kfries> CC libc/inet/herror.os
19:02 < kfries> CC libc/inet/gai_strerror.os
19:02 < kfries> usr/include/error.h: glibc uclibc
19:02 < kfries> Due to previous errors.
19:02 < kfries> --- BUILD ERROR ---
19:02 < kfries> Yep, no help
19:02 < mqueiros> there should be some more verbose log file under /var/adm/log
19:05 < mqueiros> sorry... you where already looking at it...
19:07 < kfries> Yea, and they are not showing any errors, which makes this a cruel came of guess the bug, lol
19:10 < kfries> Funny thing is that this is failing not the first time, but on recompile, on the second compilation. makes me think there is another package actually at fault, but it should still throw an error indicating what this package is missing
19:12 < mqueiros> did you added any new package between the two compilations ?
19:16 < kfries> No, the first compile is used to establish a clean environment, the second compile is to build the real version that will get installed on the target device. The two compiles come from the same Build-Target command
19:18 < mqueiros> ok. use something like pastebin and paste the full log of 1-uclibc.err Maybe you missed something...
19:22 < kfries> OK, hopefully you are right and I am just brain dead, here is the log http://pastebin.com/m7c3b9265
19:35 < kfries> I keep at it, and..... nothing, I just don't see the error. Not sure what to do to fix
19:37 < mqueiros> just a couple of warnings, but no error...
19:39 < kfries> Yep, except for that big one at the end that says I won't continue because I'm hallucinating non-existent errors
19:40 < mqueiros> yes... but no error before that one
19:47 < kfries> OK, think I need to walk down and get some lunch to clear my head and less my frustration... thanks for the help
19:48 < mqueiros> ok! later!
22:30 -!- synchris_ is now known as synchris
23:13 -!- the_rainbow [i=ee@41.209.167.149] has quit [Remote closed the connection]
23:54 -!- kfries [n=kfries@71.216.94.233] has quit [Remote closed the connection]
--- Log closed Fri Jun 05 00:00:33 2009