ibotlog2html for #crosstool-ng

<< Previous 2016-06-07 Next >>

# 02:56:59 enunes quits : Ping timeout: 250 seconds
# 03:31:24 blueness quits : Quit: blueness
# 03:53:16 blueness joins #crosstool-ng
# 03:58:06 fenugrec is now known as: fenugrec_
# 04:28:25 fenugrec_ quits : Ping timeout: 250 seconds
# 05:56:47 diorcety joins #crosstool-ng
# 06:11:01 diorcety quits : Read error: Connection reset by peer
# 06:19:16 lundmar joins #crosstool-ng
# 06:23:02 dummys quits : Ping timeout: 260 seconds
# 06:25:37 dummys joins #crosstool-ng
# 06:54:19 ghostbsdun quits : Remote host closed the connection
# 07:44:36 ghostbsdun joins #crosstool-ng
# 08:15:09 caveat quits : Ping timeout: 276 seconds
# 08:28:35 Elimin8er quits : Quit: http://lightningbolt.flashserv.net
# 08:28:51 Elimin8er joins #crosstool-ng
# 10:11:21 Elimin8er quits : Ping timeout: 240 seconds
# 10:31:42 ragedragon joins #crosstool-ng
# 12:19:03 caveat- joins #crosstool-ng
# 13:35:16 ragedragon quits : Ping timeout: 264 seconds
# 13:56:43 Elimin8er joins #crosstool-ng
# 14:01:01 Elimin8er quits : Ping timeout: 240 seconds
# 14:05:00 JakeSays quits : Read error: Connection reset by peer
# 14:07:23 fenugrec_ joins #crosstool-ng
# 14:08:43 JakeSays joins #crosstool-ng
# 14:15:43 Elimin8er joins #crosstool-ng
# 14:16:10 JakeSays quits : Read error: Connection reset by peer
# 14:18:43 JakeSays joins #crosstool-ng
# 14:43:31 fenugrec_ is now known as: fenugrec
# 17:34:39 blueness quits : Quit: blueness
# 17:41:12 blueness joins #crosstool-ng
# 17:44:36 ragedragon joins #crosstool-ng
# 18:00:55 blueness quits : Quit: blueness
# 18:05:30 blueness joins #crosstool-ng
# 18:53:57 enunes joins #crosstool-ng
# 19:06:48 y_morin joins #crosstool-ng
# 20:37:52 fenugrec quits : Quit: Leaving
# 20:57:43 fenugrec joins #crosstool-ng
# 20:59:33 fenugrec what I never understood is why there are 2 or 3 duplicate binaries in a toolchain - 3 copies of gcc / cc, 2 copies of objdump, 3 copies of ld, etc...
# 20:59:56 y_morin fenugrec: They are not copies; they are hard-links.
# 21:04:19 fenugrec hi y_morin ; interesting, I hadn't noticed but I still find strange that such a thing would be required. It seems we're always using some kind of build system to locate the compiler binaries anyway, so why have all those different names. (plus, on win*, I don't think the concept of hardlink is applicable and so a toolchain would actually have duplicate binarires taking up space)
# 21:05:06 y_morin fenugrec: It's gcc doing the install in different locations.
# 21:05:44 y_morin fenugrec: And Windows (since at least windows NT) does support hardlinks.
# 21:05:53 y_morin (Well, NTFS does)
# 21:06:53 fenugrec IIRC the NTFS semantics of hardlinks are not the same, I always assumed they were quite different. Plus, if one downloads the typical gcc-embedded-arm toolchain .zip , I don't think it's possible to have hardlinks in a zip archive
# 21:06:57 y_morin fenugrec: The only binaries of interest are the ones in bin/ that are prefixed with the tuple; the others are purely internal to gcc.
# 21:07:30 y_morin fenugrec: Wrong, ZIP does support hardlinks. And if it did not, it's not really a problem. You jsut get duplicate files.
# 21:07:51 y_morin fenugrec: And the semantics of hardlinks on NTFS are about just the same as on a UNIX FS.
# 21:09:21 fenugrec hmm
# 21:11:12 y_morin fenugrec: Don't get confused by symlinks, for which there is nothing similar in Windows. Cygwin (for example) emulates symlinks with "shortcuts" (but it has limitations).
# 21:11:38 y_morin Also, on NTFS, it is posible to have hardlinks to a directory (aka folder), although I'd recommnd against using them.
# 21:11:51 fenugrec I must be thinking of symlinks vs win* "mklink" which can't really do the same thing... in any case this has been enlightening
# 21:12:29 y_morin ;-)
# 21:12:47 fenugrec and gcc-arm on win* doesn't seem to use hardlinks, and really takes up >200MB
# 21:51:38 enunes quits : Quit: leaving
# 21:51:58 enunes joins #crosstool-ng
# 21:56:42 y_morin quits : Quit: Nighty Night! :-)
# 22:09:22 fenugrec quits : Remote host closed the connection
# 22:09:40 fenugrec joins #crosstool-ng
# 22:26:25 fenugrec quits : Remote host closed the connection
# 22:26:45 fenugrec joins #crosstool-ng
# 22:28:46 enunes quits : Ping timeout: 272 seconds
# 22:30:21 enunes joins #crosstool-ng
# 23:03:26 fenugrec quits : Remote host closed the connection
# 23:03:45 fenugrec joins #crosstool-ng
# 23:56:26 fenugrec quits : Remote host closed the connection
# 23:56:43 fenugrec joins #crosstool-ng

Generated by ibotlog2html by Yann E. MORIN