# Format for this file: # Epoch Channel Nickname Action Message # # All separated with a single space, empty values are replaced with a dash '-' # except messages which are kept empty. # Lines starting with '#' are comments; comments are not allowed except as the only content of the line # 1395192214 #crosstool-ng djerome join 1395200225 - djerome quit Remote host closed the connection 1395201218 - alan_o quit Remote host closed the connection 1395209498 - sh4rm4 quit Ping timeout: 252 seconds 1395210019 #crosstool-ng sh4rm4 join 1395216698 #crosstool-ng aalv join 1395221576 - sh4rm4 quit Ping timeout: 252 seconds 1395223219 #crosstool-ng sh4rm4 join 1395224414 - sh4rm4 quit Ping timeout: 252 seconds 1395233626 #crosstool-ng sh4rm4 join 1395234545 - sh4rm4 quit Ping timeout: 252 seconds 1395235387 #crosstool-ng alan_o join 1395235908 #crosstool-ng sh4rm4 join 1395238703 - sh4rm4 quit Ping timeout: 252 seconds 1395240949 #crosstool-ng sh4rm4 join 1395241419 - sh4rm4 quit Remote host closed the connection 1395241576 #crosstool-ng sh4rm4 join 1395245473 - aalv quit Remote host closed the connection 1395253787 #crosstool-ng y_morin join 1395253806 - xrl_____ quit Ping timeout: 264 seconds 1395253957 #crosstool-ng xrl_____ join 1395254515 - tlwoerner quit Quit: Leaving 1395254727 #crosstool-ng tlwoerner join 1395255870 #crosstool-ng smartin_ join 1395255870 - tlwoerner quit Quit: Leaving 1395255905 #crosstool-ng tlwoerner join 1395258304 #crosstool-ng alan_o say Does anyone understand this problem: http://stackoverflow.com/questions/14207189/crosstools-ng-cant-find-pthread-so 1395258317 #crosstool-ng alan_o say Everything I find says "change in the .so." Seems wrong. 1395258483 #crosstool-ng bhundven say alan_o: what version of crosstool-ng are you using? 1395258498 #crosstool-ng dalias say the answer looks correct to me 1395258498 #crosstool-ng bhundven say are you using the 1.19.0 release or tip from hg? 1395258505 #crosstool-ng dalias say having hard-coded paths in that file does not make sense 1395258519 #crosstool-ng bhundven say dalias: right 1395258541 #crosstool-ng bhundven say how did the hardcoded paths get there? 1395258550 #crosstool-ng alan_o say I'm actually using one from codesourcery, but since the SO post mentioned ct-ng I thought you might have information on the general issue. 1395258563 #crosstool-ng bhundven say oh 1395258564 #crosstool-ng alan_o say Sorry to be "that guy" :( 1395258564 #crosstool-ng bhundven say nm 1395258566 #crosstool-ng dalias say :) 1395258577 #crosstool-ng alan_o say So you think hardcoded paths should not be there? 1395258590 #crosstool-ng alan_o say let me check my ct-ng toolchain 1395258601 #crosstool-ng bhundven say did the toolchain come that way? 1395258617 #crosstool-ng alan_o say yes. It buildroot downloaded it 1395258647 #crosstool-ng bhundven say I'm still drinking first cup of coffee 1395258688 #crosstool-ng alan_o say my ct-ng toolchain has the same 1395258695 #crosstool-ng bhundven say I'm kind of like starting up a diesel engine, the glow plugs are still warming up... 1395258714 #crosstool-ng dalias say :) 1395258722 #crosstool-ng alan_o say but the difference is, my ct-ng toolchain is for arm, so maybe something detected the arch difference and didn't try to use it. 1395258788 #crosstool-ng bhundven say it's gcc's job to figure out the paths for files, the linker script should just be saying the names of the libraries to link in. 1395258892 #crosstool-ng alan_o say hmm 1395259027 #crosstool-ng bhundven say (technically, collect2) 1395259057 #crosstool-ng bhundven say but you don't invoke that directly, gcc handles that through the driver interface (specs) 1395259237 #crosstool-ng alan_o say hmm, after modifying the .so file, I get similar with libc 1395259242 #crosstool-ng alan_o say http://dpaste.com/1746356/ 1395259261 #crosstool-ng alan_o say ^ trying to cross-build boost (which is enough of a nightmare by itself) 1395259296 #crosstool-ng bhundven say hrm, maybe I'm confused. 1395259315 #crosstool-ng bhundven say that is without the paths? 1395259341 #crosstool-ng alan_o say I took the hard-coded paths out of libpthread.so but now I'm getting the same error on libc 1395259359 #crosstool-ng alan_o say and yes, that paste is without the libpthread.so hard-coded paths 1395259485 #crosstool-ng alan_o say does the compiler somehow not know it's cross-compiling? 1395259534 #crosstool-ng bhundven say no 1395259548 #crosstool-ng bhundven say what is your host platform/os? 1395259589 #crosstool-ng bhundven say your ct-ng toolchain, what version are you using? 1395259599 #crosstool-ng bhundven say version of ct-ng, that is. 1395259614 - smartin_ quit Write error: Broken pipe 1395259630 #crosstool-ng bhundven say I know there are fixes for armeabihf in hg not in the 1.19.0 release 1395259687 #crosstool-ng alan_o say Well the paste is not from the ct-ng one. My ct-ng one is for arm. This is a host of x86_64 building for i686 1395259723 #crosstool-ng alan_o say ct-ng one is pretty old. Could build up a new one for i686. 1395259764 #crosstool-ng bhundven say ok, I don't mess with build/host x86_64 target i686 much. 1395259808 #crosstool-ng bhundven say brb... need more caffeine. 1395259810 #crosstool-ng alan_o say yeah, it's "kind-of cross." The issue may be related to that. 1395259935 #crosstool-ng smartin_ join 1395260899 #crosstool-ng alan_o say In my test program, it looks like the problem starts when I set the library path to point to the buildroot-built library directory. I bet that directory has stuff that was built with the native compiler (because I was screwing with it). 1395261162 #crosstool-ng bhundven say problem: screwing with it :D 1395261390 #crosstool-ng alan_o say could be.... doing a clean on buildroot now and making sure it's building with the right tools. It'd be nice to be able to disable all your local (native) build tools temporarily (headers, libs, compilers, etc). 1395261996 #crosstool-ng bhundven say oh 1395262054 #crosstool-ng bhundven say coffee helped 1395262060 #crosstool-ng bhundven say now I see the problem you posted 1395262089 #crosstool-ng bhundven say /lib/arm... is wrong 1395262095 #crosstool-ng bhundven say but /lib/... is right 1395262103 #crosstool-ng bhundven say the paths are relative to the sysroot 1395262137 #crosstool-ng bhundven say so, you need the paths, but not the /lib/arm-linux-gnueabihf... and /usr/lib/arm-linux-gnueabihf 1395262151 #crosstool-ng bhundven say >.< #awakenow 1395262298 #crosstool-ng alan_o say ok, interesting 1395263063 #crosstool-ng bhundven say https://sourceware.org/binutils/docs-2.24/ld/File-Commands.html#File-Commands 1395263072 #crosstool-ng bhundven say See definitions for INPUT and GROUP 1395263088 #crosstool-ng bhundven say "In case a sysroot prefix is configured, and the filename starts with the `/' character, and the script being processed was located inside the sysroot prefix, the filename will be looked for in the sysroot prefix. Otherwise, the linker will try to open the file in the current directory. If it is not found, the linker will search through the archive library 1395263088 #crosstool-ng bhundven say search path. See the description of `-L' in Command Line Options." 1395263575 #crosstool-ng bhundven say updated on stackoverflow 1395264489 #crosstool-ng alan_o say hmm. thanks 1395264497 #crosstool-ng alan_o say So maybe it's confused about where its sysroot is. 1395264553 #crosstool-ng bhundven say you can find out with gcc -print-sysroot 1395264730 #crosstool-ng alan_o say yeah, it points into the toolchain. If I give it --sysroot=/my/buildroot/stuff/.../sysroot/ then it works. 1395264906 #crosstool-ng bhundven say strangeness, maybe old ct-ng/buildroot? 1395264986 #crosstool-ng bhundven say try ct-ng from hg: hg clone http://crosstool-ng.org/hg/crosstool-ng 1395265010 #crosstool-ng bhundven say or you can get the bz2 of tip: http://crosstool-ng.org/hg/crosstool-ng/archive/tip.tar.bz2 1395265333 #crosstool-ng y_morin say alan_o: So, you're not using a crostool-NG toolchain? 1395265404 #crosstool-ng y_morin say alan_o: We can try to help on other side issues, but we are mostly focused on crosstool-NG. 1395265405 #crosstool-ng alan_o say y_morin: not on this particular problem. It's x86 so I let buildroot grab one for me. My ct-ng's are on ARM. 1395265427 #crosstool-ng y_morin say alan_o: So, if it is a buildroot isue, you should ask on #buildroot. 1395265481 #crosstool-ng alan_o say y_morin: absolutely. I didn't intend on getting this much support actually. I thought I could get a quick answer on whether the stackoverflow answer (which cited ct-ng) was correct/necessary, and it turns out it wasn't. 1395265551 #crosstool-ng alan_o say y_morin: the toolchain in this case Buildroot downloaded from from CodeSourcery. 1395265591 #crosstool-ng y_morin say alan_o: So, it is a problem with a codesourcery toolchain. First, I fint it odd there's a problem with these toolchains: they get pretty much tested in Buildroot. 1395265607 #crosstool-ng alan_o say I'm not sure there's a problem. 1395265623 #crosstool-ng y_morin say alan_o: Second, if (and that's a big 'if') there is a problem with that toolchain, you should bug CodeSourcery. 1395265643 #crosstool-ng alan_o say Indeed. 1395265681 #crosstool-ng y_morin say alan_o: Sorry, I'm lost: why do you ask about http://stackoverflow.com/questions/14207189/crosstools-ng-cant-find-pthread-so if that's not a problem for you? 1395265701 #crosstool-ng alan_o say y_morin: I'm having that same problem. 1395265734 #crosstool-ng alan_o say Where it's telling me it can't find /lib/libpthread.so, which lead to the discussion about whether that was an absolute path or not. 1395265752 #crosstool-ng y_morin say alan_o: OK. Then, maybe bug #buildroot with a comprehensive problem report (eg. can't build package FOO with toolchain BLA). 1395265757 #crosstool-ng bhundven say sounds to me like an environment/setup issue, not related to ct-ng, buildroot, codesourcery, or boost. ;) 1395265776 #crosstool-ng alan_o say ^^ yes, I think it's that 1395265806 #crosstool-ng y_morin say bhundven: Maybe. But it is really strange. And anyway, the best place to ask is not here, I'm afraid. :-( 1395265817 #crosstool-ng bhundven say y_morin: agreed 1395265920 #crosstool-ng y_morin say alan_o: And by the way, the content of libpthread.so is correct. 1395265923 #crosstool-ng alan_o say Yeah, now that I know more about what it's supposed to do. I think the next step is to ask over in #buildroot whether I should have to use --sysroot. 1395265938 #crosstool-ng y_morin say alan_o: Switching over there, then. 1395265996 #crosstool-ng bhundven say alan_o: should also un-site crosstool-ng in the question 1395266106 #crosstool-ng bhundven say *cite 1395266192 #crosstool-ng y_morin say bhundven: Turns out, alan_o's post on #buildroot is very explicit about the issue! 1395266204 #crosstool-ng y_morin say bhundven: Which is indeed a purely Buildroot-related issue. 1395266216 #crosstool-ng bhundven say y_morin: well, there ya go. 1395266218 #crosstool-ng bhundven say :D 1395266250 #crosstool-ng alan_o say y_morin: well yes, but now I know more than I did when I started here, or well, I know more about what's relevant. 1395266277 #crosstool-ng y_morin say alan_o: Yep, which is OK. We all learn! ;-) 1395266278 #crosstool-ng alan_o say I often find that coming up with the right question is one of the harder parts 1395266281 #crosstool-ng alan_o say maybe that's just me :) 1395266304 #crosstool-ng y_morin say alan_o: No, you;re right: asking the right question is difficult. 1395266327 #crosstool-ng y_morin say alan_o: But trying to give random giuesses as to what the solution might be does not help. 1395266352 #crosstool-ng y_morin say alan_o: You should always just say: here's what I've done, here's what I expected, here's what I got. 1395266370 #crosstool-ng y_morin say alan_o: Then: either you expected wrong and the result is correct, and you get to learn why. 1395266393 #crosstool-ng y_morin say alan_o: Or the result is wrong and you expected correct, and we get to know the exact conditions so we have a starting point. 1395266574 #crosstool-ng alan_o say In hindsight it's all clear to me what I should have done, as usual :) 1395266591 #crosstool-ng alan_o say Thanks guys for your help. It is much appreciated 1395266614 #crosstool-ng bhundven say alan_o: no problem! 1395267747 - smartin_ quit Quit: good night 1395269038 #crosstool-ng bhundven tell learns about parallel processing in bash with xargs :D XP +2000 1395269105 #crosstool-ng bhundven say now the output of this script I'm hacking is ugly as hell :p 1395269199 #crosstool-ng y_morin say bhundven: achievement unlocked! :-) 1395269204 #crosstool-ng bhundven say seriously 1395269214 #crosstool-ng y_morin say bhundven: And you can use co-processes in bash 4.2+ 1395269226 #crosstool-ng bhundven say yea, I wanted backwards compatibility 1395269229 #crosstool-ng y_morin say bhundven: co-processes == multi-threads. 1395269235 #crosstool-ng y_morin say bhundven: Yep. 1395269328 #crosstool-ng bhundven say export -f mycustomfetch; find . -name '*\.git' -print0 | xargs -0 -i --max-args=1 --max-procs= bash -c 'mycustomfetch $@' _ {} 1395269401 #crosstool-ng y_morin say bhundven: I have 'update.me' that does exactly that! :-) 1395269422 #crosstool-ng bhundven say I keep a /mirrors directory 1395269428 #crosstool-ng y_morin say (ugly shell script that does git pull, hg pull --update, svn up, cvs update, and so on...) 1395269436 #crosstool-ng bhundven say full of git clone --mirror directories 1395269439 #crosstool-ng y_morin say bhundven: I have ~/cache for that! :-) 1395269443 #crosstool-ng bhundven say :D 1395269448 #crosstool-ng bhundven say great minds think alike 1395269452 #crosstool-ng y_morin say +! 1395269455 #crosstool-ng y_morin say +1 1395269490 #crosstool-ng y_morin say bhundven: Plus a 'git gc-all ~/cache' from time to time, to regain a bit of place... 1395269686 #crosstool-ng bhundven tell makes a note about gc-all 1395269711 #crosstool-ng y_morin say bhundven: I can share it if you want. 1395269775 #crosstool-ng bhundven say I think in mycustomfetch, I'll just add: git gc --auto & so that it just does it in the background if it is needed. 1395269869 #crosstool-ng bhundven say can you do: || & to do this or that in the background? 1395269900 #crosstool-ng bhundven say need to error out if gc fails 1395269933 #crosstool-ng y_morin say bhundven: In case it can help: http://code.bulix.org/101mf9-85875 1395269952 #crosstool-ng y_morin say bhundven: ( foo || bar ) & 1395269971 #crosstool-ng bhundven say y_morin: yup! thanks! subshell 1395269997 #crosstool-ng y_morin say bhundven: In my case, since update.me and git gc-all can run concurrently, I need to lock the repositories so they do not conflict. 1395270058 #crosstool-ng y_morin say Not to say my solution is better: it's been evolving organically over many years, and it is good enough so that I do not bother hacking more than fixing the odd bugs... 1395270182 #crosstool-ng bhundven say it's much more eloquent then my cruft :D Thanks y_morin! 1395270197 #crosstool-ng y_morin say bhundven: Want my update.me as well? 1395270302 #crosstool-ng y_morin say bhundven: http://code.bulix.org/ozv7ln-85876 1395270370 #crosstool-ng bhundven say do_it! 1395270381 #crosstool-ng y_morin say Yep! :-) 1395270427 #crosstool-ng y_morin say bhundven: Locking mechanisms are different (written at different point in time), but they are compatible. 1395270756 #crosstool-ng bhundven say ok, I'm out for a while. gotta do other stuff. Thanks for the new toys, y_morin! 1395272181 - y_morin quit Quit: Nighty Night!