ibotlog2html for #crosstool-ng

<< Previous 2014-05-30 Next >>

# 00:36:05 aboutGod joins #crosstool-ng
# 00:37:15 blueness quits : Ping timeout: 276 seconds
# 00:41:12 aboutGod parts #crosstool-ng
# 00:50:07 blueness joins #crosstool-ng
# 00:50:15 blueness quits : Changing host
# 00:50:15 blueness joins #crosstool-ng
# 01:29:03 sh[4]rm4 joins #crosstool-ng
# 01:33:17 sh4rm4 quits : Ping timeout: 252 seconds
# 03:15:03 djerome joins #crosstool-ng
# 04:14:32 alan_o quits : Quit: Leaving
# 04:52:35 djerome quits : Remote host closed the connection
# 07:21:58 sh[4]rm4 is now known as: sh4rm4
# 07:57:17 dalias quits : Ping timeout: 264 seconds
# 08:02:57 dalias joins #crosstool-ng
# 08:40:37 guillaume_ joins #crosstool-ng
# 09:16:20 guillaume_ quits : Ping timeout: 265 seconds
# 09:22:42 guillaume_ joins #crosstool-ng
# 10:20:51 y_morin joins #crosstool-ng
# 11:01:50 guillaume_ quits : Ping timeout: 252 seconds
# 12:53:32 guillaume__ joins #crosstool-ng
# 13:45:45 guillaume__ quits : Remote host closed the connection
# 16:51:51 GrantK joins #crosstool-ng
# 16:55:39 GrantK Hi. I'm building a ct for RaspberryPi. It's intended to be used on a Debian/Wheezy/64 instance. Building, I understand that I specify the TARGET. Does it matter which *host* I build the compiler on? I.e., can I exec the 'ct-ng build' on an Opensuse/64 box, and then simply copy the binaries to the Debian host? Or do I have to build the compiler on the host it'll be executed/used on?
# 16:57:18 y_morin GrantK: Your best bet to be sure is to build a statically-linked toolchain
# 16:57:39 y_morin GrantK: This means gcc, ld, ar (and so on...) are all statically linked.
# 16:58:02 y_morin GrantK: This way, you can move it to virtually any host.
# 16:58:38 GrantK y_morin: hi. so that's statically link all 'from' the opensuse build env, right? that'll exec on a debian env?
# 16:59:49 y_morin GrantK: Yes.
# 17:00:10 GrantK y_morin: this error (building on Debian host, atm) tells me to build shared libs: http://pastebin.com/csncdsH5
# 17:00:59 y_morin GrantK: No, the error is about "Could not retrieve 'eglibc-2_18'"
# 17:01:09 y_morin Read the error mesage. Line 8.
# 17:01:58 y_morin GrantK: And do *not* pass any make argument to ct-ng. Not even -d or -j.
# 17:02:53 y_morin GrantK: -d would give you debugging info _about_ the ct-ng script. If you want debugging info about the build, see the resulting build.log file.
# 17:03:36 y_morin GrantK: And -j will be passed only to the ct-ng script (which is inherently *not* parallel.) If you want parallel build, go in the menuconfig, there's an entry to set the number of parallel jobs to use.
# 17:04:16 GrantK re: args, ok. re: eglibc -- dunno what to do abt that, then.
# 17:04:33 y_morin GrantK: Look at the build.log file.
# 17:04:58 y_morin GrantK: It contains the full log.
# 17:05:54 y_morin GrantK: Pastebin the last 100-or-so lines of build.log.
# 17:07:43 GrantK y_morin: missing 'svn' (this Debian env is a 'minimal' VM ...). fixing...
# 17:14:17 GrantK y_morin: humming along. thanks!
# 17:15:00 y_morin GrantK: Cheers! :-)
# 17:44:00 GrantK quits : Quit: GrantK
# 20:20:40 philenot1ound joins #crosstool-ng
# 20:21:33 philenotfound quits : Write error: Broken pipe
# 20:34:13 smartin_ joins #crosstool-ng
# 21:24:27 smartin_ quits : Quit: leaving
# 23:34:58 loide quits : Quit: Saindo
# 23:39:06 y_morin quits : Quit: Nighty Night!

Generated by ibotlog2html by Yann E. MORIN