**** BEGIN LOGGING AT Mon Apr 02 02:59:58 2012 Apr 02 12:36:25 when I try to install libc6:armel (on my x86_64-install) it says it depends on tzdata:armel. there is only tzdata:all, and it seems not being able to install because of this. to install libc and other libraries for cross compilation to ARM, is there other way of doing it? using xapt keeps forcing me to apt-get -f install removing g++ so not sure how to move forward with that tool Apr 02 13:43:06 lool, Morning, heard that you might know something about valgrind on ARM? :-) Apr 02 13:43:24 lool, We've got it failing to link on the dbusmenu build and I'm trying to figure out what's up. Apr 02 13:43:27 https://launchpadlibrarian.net/98928961/buildlog_ubuntu-precise-armhf.libdbusmenu_0.5.96-0ubuntu1_FAILEDTOBUILD.txt.gz Apr 02 13:45:51 lool, Sorry, xchat crashed. If you responded, I missed it :-/ Apr 02 13:54:24 tedg: he didn't Apr 02 13:58:17 tedg: oy Apr 02 13:58:38 lool, Heh, might thoughts exactly :-) Apr 02 13:58:56 my Apr 02 14:01:08 tedg: I find it weird that it's mentioning /usr/lib/debug/usr/lib/arm-linux-gnueabihf Apr 02 14:01:23 ld shouldn't be poking there?! Apr 02 14:01:48 lool, Could it be something funky with the pc file? Do you have an ARM system handy? Apr 02 14:02:12 Here's the x86 pkg-config Apr 02 14:02:13 $ pkg-config --cflags --libs valgrind Apr 02 14:02:13 -I/usr/include/valgrind -L/usr/lib/valgrind -lcoregrind-amd64-linux -lvex-amd64-linux -lgcc Apr 02 14:02:14 tedg: Why do you actually need to link to valgrind? Apr 02 14:02:30 I dont see any valgrind include in the testapp Apr 02 14:02:34 lool, It has a couple macros so that the startup/shutdown doesn't end up in the output. Apr 02 14:03:19 lool, It's just including callgrind.h which is all one lib Apr 02 14:04:31 tedg: I'm not familiar with linking to valgrind, but from what I can tell, the build is failing to link tools/testapp/ which doesn't include callgrind.h or any valgrind header Apr 02 14:04:51 I've only run valgrind as a standalone tool myself Apr 02 14:05:14 lool, Well, it sets up the pkgconfig setup for all the tests, they aren't done independently. Apr 02 14:05:47 lool, So one of the tests uses it, but all of them get the link because the configure.ac is lazy (or it's authors, perhaps :-) ) Apr 02 14:05:48 ah Apr 02 14:06:49 tedg: It's widespread practice to define the libs only once and then have all objects linked to them; it means you get superfluous lib deps on your binaries which get cleaned up after the fact by --as-needed; but that's unrelated, I guess this works on x86 and you expect it to work on ARM Apr 02 14:07:43 lool, If it's helpful, the C file that uses the lib is test-json-server.c Apr 02 14:07:48 tedg: You could open a bug against valgrind in Ubuntu and/or upstream with a reduced testcase and poke linaro-toolchain@lists.linaro.org about it; the main upstream maintainer of valgrind is also on IRC and did the ARMv7 port himself, maybe we will help Apr 02 14:08:23 tedg: "sewardj"; I see he is connected to another IRC network at the moment Apr 02 14:09:28 tedg: I don't think the problem is with the use of valgrind that you have; it seems to be with valgrind object files on ARM when used for useless linking with random binaries (testapp doesn't use any valgrind foo) Apr 02 14:09:33 lool, Okay, I'm just worried about hard freeze at this point. I need to figure out if we need to drop the test in the packaging or we can fix it. Apr 02 14:10:50 tedg: You could try building the testcase and see whether *that* passes, if it does a workaround is to split valgrind CFLAGS and LIBS into their own VALGRIND_CFLAGS and VALGRIND_LIBS and only list them in LIBADD/LDADD where it actually matters (test-json-server.c) Apr 02 14:12:22 tedg: Or if you don't have time to try that out, make valgrind optional and don't list that test and that package on ARM (detect valgrind availability and pass --disable-valgrind if DEB_HOST_GNU_CPU is arm) Apr 02 14:12:58 tedg: I don't have good understanding of ELF on ARM or other valgrind subtelties to resolve this, but linaro-toolchain@ would likely be able to advise Apr 02 14:12:59 lool, What's the name of the arm porter box? Do we still have one? Apr 02 14:13:12 lool, I can try a couple things there. Apr 02 14:13:14 tedg: We do have one; I believe there are now DNS aliases to connect to them Apr 02 14:13:48 tedg: porter-armhf.canonical.com Apr 02 14:16:36 tedg: it seems down though, ping IS? I can telnet other porter boxes on port 22, but not the armel/armhf ones Apr 02 14:19:55 lool, Okay, I will, sewardj might have a fix here... Apr 02 18:18:57 GrueMaster: you around? Apr 02 18:19:18 For the rest of the week. sup? Apr 02 18:19:43 GrueMaster: cool, wait, i have a kernel for you Apr 02 18:19:54 For...what platform? Apr 02 18:20:00 panda Apr 02 18:20:26 I'm not actively testing panda any more. Apr 02 18:20:36 ah Apr 02 18:21:03 My focus atm is arm server only. Apr 02 18:21:13 k Apr 02 18:21:26 (and I'm not sure how much longer that will be). Apr 02 18:22:26 GrueMaster: but is you panda connected? i need a boot only test Apr 02 18:22:48 GrueMaster: or can you tell me if anyone is doing any testing at all on panda? Apr 02 18:23:36 ppisati: I was told all arm QA was being taken over by the QA team. ask them. Apr 02 20:16:54 Has anyone seen David Mandala in the last day? Apr 02 20:19:58 Martyn: Try "ping davidm". **** BEGIN LOGGING AT Mon Apr 02 20:24:03 2012 **** ENDING LOGGING AT Tue Apr 03 02:59:58 2012