ibotlog2html for #crosstool-ng

<< Previous 2014-09-27 Next >>

# 01:10:19 enunes quits : Quit: Lost terminal
# 01:18:35 djerome joins #crosstool-ng
# 01:34:20 enunes joins #crosstool-ng
# 01:51:57 djerome quits : Remote host closed the connection
# 04:54:47 xrl joins #crosstool-ng
# 04:59:24 b_rare joins #crosstool-ng
# 05:15:45 enunes quits : Quit: Lost terminal
# 05:54:02 perr joins #crosstool-ng
# 05:54:02 perr quits : Changing host
# 05:54:02 perr joins #crosstool-ng
# 07:25:48 wycats quits : K-Lined
# 07:25:50 xrl quits : K-Lined
# 07:25:54 ovf quits : K-Lined
# 08:31:03 smartin_ joins #crosstool-ng
# 08:38:48 y_morin joins #crosstool-ng
# 09:10:39 perr quits : Quit: Leaving
# 09:10:50 perr joins #crosstool-ng
# 10:42:51 ovf joins #crosstool-ng
# 11:02:49 mingwandroid joins #crosstool-ng
# 12:49:47 perr quits : Ping timeout: 272 seconds
# 15:42:34 Bilge joins #crosstool-ng
# 15:42:41 Bilge Hello crosstool mans
# 15:43:34 Bilge Despite getting crosstool to build one of the samples normally I cannot get it to build using a modified uClibc config
# 15:44:07 Bilge [EXTRA] Extracting 'uClibc-0.9.33.2'
# 15:44:07 Bilge [WARN ] Don't know how to handle 'uClibc-0.9.33.2': unknown extension
# 15:44:27 Bilge [ERROR] >> Build failed in step 'Extracting and patching toolchain components'
# 15:44:44 Bilge [ERROR] >> Error happened in: do_libc_extract[scripts/build/libc/uClibc.sh@963]
# 15:44:56 Bilge Does anyone know why this might happen just because I point crostool to my own uClibc config file?
# 15:46:45 y_morin Bilge: Care to share your .config (ct-ng one, not uClibc one)
# 15:46:47 y_morin ?
# 15:54:18 Bilge OK sure
# 15:54:51 Bilge Is there a way you prefer me to share it?
# 16:02:03 y_morin Bilge: Yes, a pastebin site.
# 16:02:15 y_morin Bilge: For example: code.bulix.org
# 16:03:18 Bilge https://gist.github.com/Bilge/5a3e1a288220b0090a0e
# 16:04:09 y_morin Bilge: OK, lemme test that...
# 16:05:27 Bilge :)
# 16:08:51 y_morin Bilge: Weird... It works for me here...
# 16:09:36 y_morin Bilge: Can you also post the biuild.log file, please?
# 16:09:41 y_morin build.log <--
# 16:10:53 Bilge OK
# 16:16:51 Bilge https://gist.github.com/Bilge/667747c714d6b4b9d3c8
# 16:18:09 y_morin Bilge: OK, lemme have a look...
# 16:20:54 Bilge It's quite big considering it failed on the start
# 16:23:29 y_morin Bilge: It's big because it contains all the files being extracted from the archives.
# 16:24:17 y_morin Bilge: Also, it is really a *bad* idea to run as root.
# 16:24:33 Bilge It's running in a docker container so I really don't care
# 16:26:00 Bilge I can share the docker file if you want to replicate the environment also
# 16:26:52 y_morin Bilge: No, I don't use docker. But thanks!
# 16:27:16 y_morin Bilge: Can you see if you have a file named uClibc-0.9.33.2 in your home?
# 16:27:28 y_morin Bilge: The home of root in your docker instance, that is.
# 16:27:35 Bilge I don't, it's a directory
# 16:27:51 Bilge drwxrwxr-x 20 root root 4096 Sep 27 13:23 uClibc-0.9.33.2/
# 16:28:02 y_morin Bilge: Ah, that's the reason.
# 16:28:07 Bilge I extracted uClibc there so I could configure it
# 16:28:17 y_morin Bilge: OK, so here's why it fails:
# 16:28:19 Bilge Then symlinked the config file to /etc/ct-ng/uclibc.conf
# 16:28:52 y_morin Bilge: You set CT_LOCAL_TARBALLS_DIR="${HOME}"
# 16:29:11 y_morin Bilge: So ct-ng will try to find an archive of each component in there
# 16:29:14 Bilge I thought tarballs only got made at the end?
# 16:29:27 y_morin Bilge: ct-ng tries a few common extensions, and no extension at all.
# 16:29:46 y_morin Bilge: No, the tarballs from the components are downloaded: linux, uClibc...
# 16:29:53 y_morin Bilge: ct-ng creates no tarball.
# 16:30:15 Bilge Oh, so that setting is for something else... I didn't understand what it was used for
# 16:30:26 Bilge Also I thought ${HOME} was the CT-NG build directory
# 16:30:30 y_morin Bilge: So, ct-ng tries all those extensions, then with no extension, and finds that ${CT_LOCAL_TARBALLS_DIR}/uClibc-0.9.33.2 exists, so it believes it exists.
# 16:30:34 Bilge Is there a list of config variables somewhere?
# 16:30:48 y_morin Bilge: Well, how did you configure ct-ng ?
# 16:31:05 y_morin Bilge: The standard way is by running: ct-ng menuconfig
# 16:31:08 Bilge I used that
# 16:31:17 y_morin Bilge: Editing the .config file by hand is not supported, and a bad idea.
# 16:31:19 y_morin OK
# 16:32:00 y_morin Bilge: Bilge There is no list, but htere is an help entry in the menuconfig for each item in the menu
# 16:32:33 Bilge It seems like a variable reference would be helpful :)
# 16:33:09 Bilge If CT-NG doesn't build tarballs why does the man page say: "As of today (20140927), building tarballs is broken."
# 16:33:17 Bilge Doesn't that mean it is supposed to build them?
# 16:34:11 y_morin Bilge: Well, it used to work a long time ago. It no longer works, and I should have removed that.
# 16:34:47 y_morin Bilge: http://ymorin.is-a-geek.org/download/tmp/Screenshot%20from%202014-09-27%2018:32:31.png
# 16:34:56 Bilge I don't understand the reason it gives for it not working. I can just run tar on the output and make a tarball... what's so difficult?
# 16:34:57 y_morin Bilge: You can see the "Help" button
# 16:35:12 y_morin Bilge: Because that's not what it was meant to do.
# 16:35:45 y_morin Bilge: It was meant to do: 1) a tarball of the generated toolchain, 2) a tarball of each patched component, 3) a tarball of the ct-ng source tree.
# 16:36:29 y_morin Bilge: But because ct-ng can be installed like any other package, it is no longer possible to make a tarball of the ct-ng source tree, so "generatign the tarballs" is broken, and can not be made to work.
# 16:36:51 y_morin Bilge: The reason to make such tarballs was to make it easy to reproduce the toolchain later on.
# 16:38:15 Bilge I think I already have that benefit by virtue of using containers
# 16:38:28 Bilge I just want to tar the toolchain so I can use it with buildroot
# 16:39:12 Bilge I'm not sure what the minimum necessary files are to do that though so I just tar the whole x-tool/{target} directory
# 16:40:07 y_morin Bilge: Yes, that's what you want to tar; it's the entire toolchain.
# 16:40:34 Bilge Sweet :)
# 16:40:53 Bilge I know it works, I was just concerned there might be some garbage in there I didn't really need
# 16:41:42 y_morin Bilge: No, it only contains the toolchain, nothing more.
# 16:42:37 Bilge My container contains CT-NG and uClibc and it seems CT-NG has support for using preinstalled sources such as uClibc tarballs like you just explained to me
# 16:42:53 Bilge However can it also use the uClibc source I've already extracted or does it only look for tarballs?
# 16:43:46 Bilge I think it would be nice to preinstall as many sources as possible because if I let CT-NG download the components it takes more than 5 minutes for some reason
# 16:43:57 Bilge [INFO ] Retrieving needed toolchain components' tarballs: done in 377.76s (at 06:19)
# 16:44:59 y_morin Bilge: Well, once it's downloaded, you do not need to re-download them: set CT_LOCAL_TARBALLS_DIR="/path/to/a/cache/directory" and CT_SAVE_TARBALLS=y
# 16:45:17 y_morin Bilge: Next time you re-configure ct-ng, pint it to the same location, and it will not re-downl.oad.
# 16:45:31 y_morin s/pint/point/
# 16:46:09 y_morin GTG. back later...
# 16:46:16 Bilge Thanks for your help :)
# 16:46:21 y_morin Cheers! ;-)
# 16:58:58 djerome joins #crosstool-ng
# 17:24:23 smartin_ quits : Quit: leaving
# 17:31:08 maxime quits : Ping timeout: 245 seconds
# 17:37:42 mingwandroid quits : *.net *.split
# 17:37:46 gonzzor quits : *.net *.split
# 17:37:46 blargh quits : *.net *.split
# 17:37:50 iugrina quits : *.net *.split
# 17:46:41 maxime_ joins #crosstool-ng
# 17:46:42 mingwandroid joins #crosstool-ng
# 17:46:42 gonzzor joins #crosstool-ng
# 17:46:42 blargh joins #crosstool-ng
# 17:46:42 iugrina joins #crosstool-ng
# 18:46:56 xrl joins #crosstool-ng
# 18:53:23 mingwandroid quits : Ping timeout: 240 seconds
# 19:48:24 x56 quits : Quit: Peace
# 19:49:22 x56 joins #crosstool-ng
# 20:34:24 HobGoblin joins #crosstool-ng
# 20:34:48 HobGoblin is now known as: Guest94465
# 20:36:53 y_morin_ joins #crosstool-ng
# 20:37:45 wycats joins #crosstool-ng
# 20:44:09 y_morin quits : Ping timeout: 260 seconds
# 20:44:10 smartin quits : Ping timeout: 260 seconds
# 20:44:11 UukGoblin quits : Ping timeout: 260 seconds
# 20:44:17 smartin joins #crosstool-ng
# 20:44:17 Bilge y_morin_: I want to know if I can get CT-NG to recognise my extracted files for uClibc
# 20:44:21 RushPL_ joins #crosstool-ng
# 20:44:21 Bilge If I extract to .build/src and touch .build/src/.uClibc-0.9.33.2.extracted will it work?
# 20:44:28 kos_tom quits : Write error: Connection reset by peer
# 20:44:37 kos_tom joins #crosstool-ng
# 20:45:04 y_morin_ Bilge: You can enable the EXPeRIMENTAL features. Then, set the uClibc version choice to "Custom uClibc", and then point it to your uClibc sources.
# 20:45:18 y_morin_ Bilge: But there is absolutely no reason to do so if you use a released version.
# 20:45:35 y_morin_ Bilge: That's meant for developpers that want to use a modified source tree.
# 20:45:57 Bilge I am using a released version
# 20:47:17 Bilge In my container I have CT-NG and uClibc extracted. I don't want to keep uClibc tar'd up because I need it extraced to configure it. So I want CT-NG to pick up and reuse the extracted source instead of redownloading it if possible
# 20:48:50 RushPL quits : Ping timeout: 272 seconds
# 22:20:28 enunes joins #crosstool-ng
# 22:26:16 xrl quits : Quit: Connection closed for inactivity
# 22:40:41 enunes quits : Read error: Connection reset by peer
# 22:45:54 enunes joins #crosstool-ng
# 23:03:36 y_morin_ quits : Quit: Nighty Night!
# 23:05:06 xrl joins #crosstool-ng