ibotlog2html for #crosstool-ng

<< Previous 2012-08-02 Next >>

# 00:22:12 codyps quits : Ping timeout: 244 seconds
# 00:44:16 imMute joins #crosstool-ng
# 00:45:16 imMute quits : Client Quit
# 00:45:33 imMute joins #crosstool-ng
# 00:45:35 imMute quits : Changing host
# 00:45:35 imMute joins #crosstool-ng
# 01:04:47 codyps joins #crosstool-ng
# 02:01:27 ssspiff joins #crosstool-ng
# 02:02:28 sspiff quits : Ping timeout: 248 seconds
# 02:03:07 alan_o quits : Quit: Leaving
# 02:33:02 ChanServ quits : *.net *.split
# 02:44:36 codyps quits : Ping timeout: 248 seconds
# 02:47:15 codyps joins #crosstool-ng
# 02:50:45 ChanServ joins #crosstool-ng
# 05:50:06 codyps quits : Quit: Leaving.
# 05:53:39 codyps joins #crosstool-ng
# 05:57:13 codyps quits : Remote host closed the connection
# 05:58:04 codyps joins #crosstool-ng
# 06:01:15 codyps quits : Remote host closed the connection
# 06:01:34 codyps joins #crosstool-ng
# 06:54:08 smartin joins #crosstool-ng
# 07:12:45 sspiff joins #crosstool-ng
# 07:12:45 sspiff quits : Changing host
# 07:12:45 sspiff joins #crosstool-ng
# 07:14:15 ssspiff quits : Ping timeout: 240 seconds
# 07:57:55 sspiff quits : Ping timeout: 240 seconds
# 08:03:33 sspiff joins #crosstool-ng
# 09:09:22 ChanServ quits : *.net *.split
# 09:27:09 ChanServ joins #crosstool-ng
# 09:30:12 ctngbot joins #crosstool-ng
# 16:17:25 codyps quits : Quit: Leaving.
# 16:40:30 y_morin joins #crosstool-ng
# 16:59:08 codyps joins #crosstool-ng
# 17:27:07 smartin y_morin: hi
# 17:32:20 smartin about redistributing self-contained mac cross-toolchain (adding lib{gcc_s.*,sdtc++.*}.dylib to the toolchain and tweaking rpath), i cannot remember what you told me about legal issue... :/
# 19:22:06 y_morin smartin: was it on this channel?
# 19:22:10 y_morin (Hello!)
# 19:22:34 y_morin smartin: because if so, you can search the logs.
# 19:23:37 y_morin smartin: I'll be back ~22:00 GMT+2
# 19:35:06 smartin y_morin: back in 30 to 45min.
# 19:38:49 smartin quits : Quit: leaving
# 19:45:58 alan_o joins #crosstool-ng
# 20:19:53 smartin joins #crosstool-ng
# 20:53:38 smartin y_morin: ping?
# 21:16:36 y_morin smartin: pong
# 21:23:08 smartin i come back about mac "self-contained" toolchains
# 21:23:58 y_morin smartin: IIRC, that's not really possible on Mac, as static linking is not possible on OS-X
# 21:24:35 y_morin At least, that's what usual Mac users told me; I have no experience about MacOS
# 21:24:39 smartin in which i add lib{gcc_s,stdc++}*.dylib and tweak rpath to make it self-contained
# 21:26:49 smartin yep, this not possible (or hard and at least not so much documented)... what a pity
# 21:27:49 y_morin smartin: OK. So, you copy NEEDED libs in the lib/ dir, and with your rpath trick, you have a self-contained toolchain, right?
# 21:27:56 smartin the 2 libs I added come from gcc package from macport
# 21:28:08 smartin yes
# 21:28:12 y_morin Right, so, what's the issue?
# 21:29:10 smartin do I have to do/add something when redistributing it?
# 21:30:50 y_morin smartin: IANAL, but you have to respect all the licenses, that is, in this this case, probably provide the source code of those libs, as well as there build script.
# 21:31:05 y_morin s/there/their/
# 21:32:36 smartin provide the source code even for gcc from macport?
# 21:33:32 y_morin smartin: well, the source for the libs you copied.
# 21:34:17 y_morin smartin: literrally, yes, that is what the license requires. You provide a binary built from GPL or LGPL code, you have to provide a way to rebuild that binary.
# 21:34:59 y_morin smartin: Now, that a literal interpretation of the license. And IANAL.
# 21:35:23 y_morin smartin: the best bet would be *not* to provide those libs.
# 21:36:04 y_morin smartin: Aren't Macports widely available, that requiring the use to install the pre-requisites from macports too cumbersome?
# 21:36:46 y_morin smartin: I mean, in the install procedure of the toolchain, you could document to install gcc from macports, and you're done.
# 21:37:04 y_morin What's so difficult about this?
# 21:37:41 y_morin won't say what he thinks about MacOS.
# 21:40:11 smartin to use ct-ng, we need to use a gcc from macport, unfortunately, using the built toolchain on another Mac host without this gcc package installed fails...
# 21:40:43 smartin not really user-friendly...
# 21:42:21 y_morin smartin: what is it that is so difficult to require that the gcc _runtime_ be instaleld from Macports on the other co;puter)s)?
# 21:42:30 y_morin *computer(s)
# 21:44:42 y_morin smartin: after all, if I want to pass a pre-built toolchain on Linux, there will also be packages to install on the other computer(s) to run this toolchain.
# 21:45:00 y_morin (But on Linux, we do have static linking, although it is sub-optimal.)
# 21:46:29 alan_o quits : Quit: Leaving
# 21:47:44 smartin well, not really *noob*-friendly, most of the time poeple doesn't care how it works, they just want to install the software they paid for and use it
# 21:48:08 smartin preferably with no additional actions required...
# 21:49:33 smartin Not all platform take care of developers ;)
# 21:49:37 y_morin smartin: then I would say a "noob" (that's your word! ;-) ) has nothing to do with cross-compilation.
# 21:50:23 y_morin smartin: but the basic rule for gpl/lgpl covered code is: you provide a binary, you must provide means to rebuild them (and replace them for v3)
# 21:51:40 smartin but when you want to do cross-platform software and/or cross-toolchain, you have to deal with it...
# 21:53:31 smartin ok, now I know what i have to do to redistribute it
# 21:53:39 smartin thanks
# 21:53:59 y_morin Cheers!
# 21:58:11 y_morin smartin: By the way, re-readings my answers, I may seem a bit harsh. That was not my intention.
# 21:58:50 smartin y_morin: it's ok ;)
# 22:23:22 y_morin just build all 40 samples: ~90GiB for the build dirs, plus another ~8GiB for the toolchain dirs, and 6h of intensive heat disipation...
# 22:36:36 y_morin quits : Quit: Night!
# 22:40:12 smartin quits : Quit: leaving

Generated by ibotlog2html by Yann E. MORIN