**** BEGIN LOGGING AT Sat Feb 05 19:33:03 2005 Feb 05 19:37:32 me too. Feb 05 19:37:40 but it sure took forever. Feb 05 19:37:52 I'm timing my build to see how much of a diff it makes. Feb 05 19:38:25 unfortunately it didn't fix my oe build problem Feb 05 19:38:34 what problem is that again? Feb 05 19:39:58 i seem to be the only person who has it Feb 05 19:40:08 it seems to have fixed mine anyways. libtool completed. Feb 05 19:40:14 but it's not over yet! Feb 05 19:40:14 cool Feb 05 19:40:36 What's your problem? Feb 05 19:40:45 (with OE) Feb 05 19:40:55 well that was not fun Feb 05 19:41:27 quilt isn't working right Feb 05 19:42:37 really? I had some problems with that originally when they started using it. Feb 05 19:42:58 one one machine it works fine, on the other it always fails Feb 05 19:43:11 chmod: cannot access `patches/*': No such file or directory Feb 05 19:43:19 cp: cannot create regular file `patches/fix-ipkg-link': Permission denied Feb 05 19:43:47 odd. Feb 05 19:44:21 I noticed i had permission denied errors when wiping my tmp folder lately. It forces me to become root to do it. Feb 05 19:44:37 Are the perms on those folder/files the same? Feb 05 19:45:15 the problem is that the patches dir is never created Feb 05 19:46:27 did you mention it to kergoth? Feb 05 19:46:37 yes Feb 05 19:48:00 did he have any leads? Feb 05 19:48:06 no Feb 05 19:48:27 damn. that sucks when even kergoth doesn't have a clue. Feb 05 19:48:45 that machine's down for the count. every week or so I clear all the caches, install the latest bb, etc, and try again Feb 05 19:48:48 I would try reinstalling the whole thing. Feb 05 19:48:57 the whole what thing? Feb 05 19:49:06 I already recloned oe Feb 05 19:49:10 I meant the OE stuff and related apps. Feb 05 19:49:16 but I'm sure you alrady did that Feb 05 19:49:19 redownloaded quilt cvs about 10 times Feb 05 19:50:12 totally cleared sources dir Feb 05 19:50:53 There has to be a reason. Perhaps you can try to isolate the file that calls quilt and then put some debug echos everywhere . Feb 05 19:51:13 Then again, I have no clue what I'm talking about. Feb 05 20:03:22 03garpinc * 10unslung/ (3 files in 2 dirs): OpenNap Plugin for giFT Feb 05 20:13:43 jacques: if you cant get quilt working on that machien with oe, dont use quilt. inherit the bbclass that switches you from quilt to patcher. **** ENDING LOGGING AT Sat Feb 05 20:14:00 2005 **** BEGIN LOGGING AT Sat Feb 05 20:15:04 2005 Feb 05 20:15:29 03garpinc * 10unslung/Makefile: Added gift-opennap for testing Feb 05 20:41:53 03djf * 10unslung/Makefile: added gettext to NATIVE_AND_CROSS_PACKAGES_READY_FOR_TESTING Feb 05 21:02:26 wow! My "fat" openslug build now completes in 74minutes!! Feb 05 21:03:44 NOT having the ccache folder on an nfs drive (by accident) helps! ;) Feb 05 21:05:05 hey randy Feb 05 21:05:29 hi, thanks Feb 05 21:10:11 heading to bed... later all Feb 05 21:28:21 03djf * 10unslung/make/irssi.mk: initial checkin - does not build yet - working on it Feb 05 22:00:18 Anybody seen that boot messge with the newer openslug? : INIT: VERBOSE=no requested, but /proc/progress not available. Feb 05 22:30:22 another $25 just rolled in .... Feb 05 22:42:34 VoodooZ_home: that likely has to do with the work mickeyl has done with the linux progress patch stuff. ask him. Feb 05 22:45:41 ok. thanks. Feb 05 22:46:15 progess patch? Feb 05 22:47:29 ~lpp Feb 05 22:47:30 it has been said that lpp is The Linux Progress Patch. It gives you graphical boot screens while booting the kernel. Like MSWindows. http://lpp.freelords.org/ Feb 05 22:47:48 hmm Feb 05 22:47:49 he was playing around with that or a related project on his zaurus running 2.6 Feb 05 22:47:55 dont recall the details Feb 05 22:52:28 cool. thanks. I'll look it up. Feb 05 22:53:48 I also discovered a new problem with udev under openslug.It seems the links.conf created extra nodes (leds and buzzer are not detected automatically) never make it. Feb 05 22:54:22 when I manuall restart udev after logging it though it creates them no problem. as if the ramfs is mounted on top of them or something. Feb 05 22:55:15 ramfs is mounted before udevstart gets run Feb 05 22:55:18 * kergoth`bbl shrugs Feb 05 22:55:47 I know. but I can't seem to see why they never get created like before. Oh well. Feb 05 22:56:02 I might remove udev anyways. It doesn't give me anything more really. Feb 05 22:57:39 for something with more or less fixed hardware like a robot there's no big advantage. Feb 05 22:57:48 anyways. good night. It's 2am here so... Feb 05 22:58:33 nod, its more useful when you're actually hotplugging things. Feb 05 22:59:11 yeah. It might happen with the bot but rarely so we'll see. Feb 05 22:59:14 take care, Feb 05 23:30:45 hmm - pkgconfig fails on cross on builds ... Feb 05 23:31:04 Can't exec "aclocal": No such file or directory at /usr/bin/autoreconf line 176. Feb 05 23:32:19 ah - builds was missing automake Feb 05 23:47:47 03rwhitby * 10unslung/Makefile: Promoted gettext and pkgconfig Feb 05 23:50:31 hi ho Feb 05 23:50:37 hmm - maybe gettext is failing native Feb 05 23:50:38 irssi on slug Feb 05 23:50:47 jacques: how did you get gettext to compile native? Feb 05 23:50:54 hmm? shouldn't - what error? Feb 05 23:51:16 grep: /home/slug/packages/toolchain/armv5b-softfloat-linux/gcc-3.3.5-glibc-2.2.5/armv5b-softfloat-linux/lib/./libstdc++.la: No such file or directory Feb 05 23:51:16 libtool: link: `/home/slug/packages/toolchain/armv5b-softfloat-linux/gcc-3.3.5-glibc-2.2.5/armv5b-softfloat-linux/lib/./libstdc++.la' is not a valid libtool archive Feb 05 23:51:16 make[5]: *** [libasprintf.la] Error 1 Feb 05 23:51:36 yeah you have .la files somewhere Feb 05 23:51:44 .la files with those paths in them Feb 05 23:51:56 either in /opt/lib or in the toolchain lib dir Feb 05 23:52:35 those can cause build problems for more than just gettext Feb 05 23:54:06 for now at least it looks like we will have another native-only - irssi - don't try it yet tho Feb 05 23:54:23 do you think ppl will want ipv6 support in irssi? Feb 05 23:54:40 is anybody actually using it? Feb 05 23:57:52 ipv6 ? Feb 05 23:58:11 freenode supports it. I've seen lots of ppl signed into freenode with ipv6 addresses Feb 06 00:06:12 jacques: any idea which packages would be erroneously installing those .la's ? And how come you don't have them - another manual change which hasn't been reflected in an ipk correction yet? Feb 06 00:09:06 03djf * 10unslung/sources/irssi/control: initial checkin Feb 06 00:10:25 rwhitby-away, I remove some manually, and others I have the makefile remove when it makes the ipk Feb 06 00:10:34 and some dont seem to cause any problems Feb 06 00:10:58 and pretty much any package which installs libs and uses libtool will install .la's Feb 06 00:11:35 the libstdc++ ones seem to cause the most problems, but I have had problems with others Feb 06 00:31:02 re Feb 06 00:31:23 so should we outlaw .a's and .la's from /opt/lib ? Feb 06 00:32:49 hmm - pkgconfig fails cross too Feb 06 00:32:59 strip: Unable to recognise the format of the input file /home/unslung/packages/builds/pkgconfig-0.15.0-ipk/opt/bin/pkg-config Feb 06 00:33:32 i think it failed much earlier than tat for me on cross Feb 06 00:33:43 that's an easy fix Feb 06 00:34:05 it just means stupid install is trying to use the host strip instead of cross-strip Feb 06 00:34:25 for me cross failed on some auto* stuff Feb 06 00:34:28 native worked tho Feb 06 00:35:01 gentoo installs all known versions of autoconf and automake and then uses a wrapper with env vars to select between them Feb 06 00:35:22 since they are not backward nor forward compatible (yay auto* devs) Feb 06 00:45:07 so should we outlaw .a's and .la's from /opt/lib ? Feb 06 00:49:14 .la's : for now, I would say yes - we aren't deriving any benefits from them as long as them have incorrect info in them Feb 06 00:49:45 .a's : where a .so exists I would say yes, but some packages on'y make .a's (I think I noticed some like this anyway) Feb 06 00:50:15 I think libpcap is an example of a package that only makes a static lib Feb 06 00:50:35 we shouldn't be putting .a's in /opt/lib - we want shared libraries on a small memory slug Feb 06 00:51:01 if a package needs a .a, it can get it from staging. Feb 06 00:51:11 ok Feb 06 00:51:27 bbiab Feb 06 01:01:19 I merged the 3.18 unslung-standard-rootfs into 4.x bumping the 4.x PR to 50. (from 41) Feb 06 01:10:13 03djf * 10unslung/make/irssi.mk: builds native, not cross - ready for testing Feb 06 02:01:06 03rwhitby * 10unslung/Makefile: Moved gettext and pkgconfig to cross only. Feb 06 02:32:33 03rwhitby * 10unslung/Makefile: Demoted pkgconfig to NEEDS_TO_BE_FIXED. Feb 06 02:33:28 reports of pkgconfig working were greatly exaggerated :-) Feb 06 02:33:38 no they arent Feb 06 02:33:44 I said it worked for me native and it did Feb 06 02:33:50 that's not exagerration Feb 06 02:34:15 not disputing that, but it doesn't work on a standard native compilation environment (as per the wiki page) Feb 06 02:34:40 so your success can't be reproduced automatically in a regular build Feb 06 02:35:27 it would help if I knew what the error was Feb 06 02:36:23 jacques: no need to get defensive - it's the .la error. It's not pkgconfig's fault, it's all the other packages that install .la's. But it doesn't change the fact that I can't automatically build it right now, hence it gets demoted. Feb 06 02:37:52 so what's the plan? leave the affected packages out of the builds until "someone" fixes all the packages that install .la's ? Feb 06 02:38:40 yep Feb 06 02:39:17 unfortunately, the last package looses until the others are fixed, cause I can't really remove packages from the feed which have been working for people for weeks Feb 06 02:39:32 so the one transitioning from testing draws the short straw Feb 06 02:39:54 also for pkgconfig cross it is trying to strip a non-binary. Feb 06 02:40:02 (as I reported earlier) Feb 06 02:40:32 yeah and it doesn't get nearly that far cross for me, for the reasons I gave Feb 06 02:40:56 I have to wonder if jp30 tested pkgconfig-ipk, or whether he figured that just getting a binary is enough ... Feb 06 02:41:36 I dunno, but lack of pkgconfig is going to block a lot of stuff Feb 06 02:41:40 like irssi Feb 06 02:42:14 well, getting it to work cross should be easy if it's just a strip error when cross-compiled on builds. Feb 06 02:42:50 it just needs to be explicitly stripped, not install --strip or install-strip whatever it's doing now Feb 06 02:42:57 agreed Feb 06 02:43:06 DIdnt I mention that a few months ago? Feb 06 02:43:25 something along the lines of "install-strip is broke, dont do that" ? Feb 06 02:43:57 it's not always broken, some packages use it and it works - install --strip (or -s I always forget) will always be broken on cross Feb 06 02:43:57 yep, but we have new developers every day, so unless it's on the packaging best practises page, then it gets forgotten Feb 06 02:44:01 which is why a bunch of mk files I touched are ugly in that they are stripping millions of binaries. Feb 06 02:44:32 http://www.nslu2-linux.org/wiki/Unslung/PackagingBestPractices Feb 06 02:44:40 it really depentds how the install-strip target is defined in the individual Makefile Feb 06 02:45:17 but I think install [-s, --strip] will always fail Feb 06 02:45:28 * dyoung nod Feb 06 02:45:51 I was making a over generalized observation because almost everything I touched didnt work. Feb 06 02:46:13 not that way it was expected to at least. Feb 06 02:46:29 can we fix install instead? Feb 06 02:46:33 for a large package with a properly written Makefile, install-strip can save a lot of work, which is why I'm trying to avoid making a rule against using it Feb 06 02:46:59 I think it should be up to the packager to decide whether or not it works. Feb 06 02:47:35 well, it seems that pkgconfig is an automake generated Makefile, and it does: Feb 06 02:47:37 I see nothing in the install man page to tell it to use anything other than the host strip command Feb 06 02:47:44 install-strip: Feb 06 02:47:44 $(MAKE) $(AM_MAKEFLAGS) AM_INSTALL_PROGRAM_FLAGS=-s install Feb 06 02:47:52 ouch Feb 06 02:48:03 so you're saying that automake generated makefiles will always fail install-strip Feb 06 02:48:10 who said that? Feb 06 02:48:38 s/you're/we're/ Feb 06 02:48:47 I don't think so Feb 06 02:48:51 I have to wonder if thats automake version dependant. Feb 06 02:49:00 jacques, what version of automake do you use usually? Feb 06 02:49:01 it's nearly impossible to make generalizations about auto* generated stuff Feb 06 02:49:05 # Makefile.in generated automatically by automake 1.4-p4 from Makefile.am Feb 06 02:49:25 I'm generally using 2.59 Feb 06 02:49:30 Makefile.am contains nothing special about strip Feb 06 02:49:40 because of all the different versions and the various ways they can be used in the .am/.ac/.in whatever files Feb 06 02:49:49 And in general it doesnt do the right thing for me. But I might not be licking it right either. Feb 06 02:50:27 because the auto* stuff is so screwed up and not compatible with itself, gentoo has to install all known versions and uses a wrapper which chooses versions based on an env var Feb 06 02:50:54 so I have about 5 versions of autoconf and 6 of automake installed on my gentoo systems Feb 06 02:51:04 * dyoung head spins Feb 06 02:51:30 as far as I can see, the version of autoconf and automake on builds.nslu2-linux.org, with the most basic Makefile.am (with no specific stuff for stripping) will always generated a Makefile with a install-strip target which fails on cross compiles. Feb 06 02:51:35 if you have a gentoo system, look at the .ebuild's for those sometime - scary Feb 06 02:53:27 2.59 is on builds. Feb 06 02:53:40 I find it disgusting that the auto* stuff, which is supposed to make cross-compiling easier, would do that Feb 06 02:54:01 but not in the least bit surprising, since I have used it for a long time Feb 06 02:54:24 I ran into 2.older not working for some things, and it told me something like "hey upgrade to 2.59 to make this work!" Feb 06 02:54:39 yeah the them soma packages only work with the older versions Feb 06 02:54:49 hence the gentoo approach Feb 06 02:55:22 not too long ago it was a stupid game, upgrade autoconf to build pacakge A, now package B no longer builds Feb 06 02:55:57 like libtool, sometimes it seems to cause more problems than it's worth Feb 06 02:56:37 I ran into that .la / .a stuff too. So I was generally blowing them away. Feb 06 02:57:17 Libtool just seems evil. Feb 06 02:57:24 unless we get a libtool expert, I don;t see us having any other way to deal with it Feb 06 02:57:46 any package built against libs in staging (cross or native) will have bad info in the .la's AFAICT Feb 06 02:58:03 nod Feb 06 02:58:04 only ones that dont are built native against libs in their final installed locations Feb 06 02:58:24 now, I suppose we could edit all the .la's, but currently I don't see the point Feb 06 02:58:35 I would have to understand the benefits of the .la's for that Feb 06 02:58:58 quicker parsing maybe? Feb 06 02:59:09 Dunno... Feb 06 02:59:22 some fuzzy thing about being able to find libs that other libs need or something Feb 06 02:59:46 How is this handled for OE built packages? Feb 06 02:59:59 and all the build processes warn about needing to do libtool --finish or something which we never do Feb 06 03:00:07 that would have to be done in postinst Feb 06 03:00:25 dyoung that would be useful to know Feb 06 03:00:56 oh and ever do man libtool ? Feb 06 03:01:23 none of my systems have a man page for it Feb 06 03:01:33 theres a manpage on builds Feb 06 03:01:44 but it... well.. It SUCKS. Feb 06 03:05:51 anyway, I don't have the time tonight to deal with it. Feb 06 03:06:49 but if someone wants to remove all .a's and .la's from packages that want to install them in /opt/lib, and bump the ipk versions for those packages, then I'll be happy to try compiling pkgconfig and gettext again on builds and prodslug tomorrow. Feb 06 03:07:40 until then, they stay out of the feeds (unless another solution is found). it's unfair on those packages, but that's life. Feb 06 03:08:47 unfortunately, native toolchain is going to be one of them Feb 06 03:09:03 or is it already removing the .la's ? Feb 06 03:09:58 looks like it's not, so lets start there. Feb 06 03:10:36 . -bash-2.05b$ ls /opt/lib/*.{a,la} Feb 06 03:10:36 . /opt/lib/libMagick++.a /opt/lib/libbz2.a /opt/lib/libltdl.la /opt/lib/libncurses_g.a /opt/lib/libpng12.la Feb 06 03:10:36 . /opt/lib/libMagick++.la /opt/lib/libfl.a /opt/lib/libmagic.a /opt/lib/libpanel.a /opt/lib/libpopt.a Feb 06 03:10:36 . /opt/lib/libMagick.a /opt/lib/libform.a /opt/lib/libmagic.la /opt/lib/libpanel_g.a /opt/lib/libpopt.la Feb 06 03:10:37 . /opt/lib/libMagick.la /opt/lib/libform_g.a /opt/lib/libmenu.a /opt/lib/libpng.a /opt/lib/libtermcap.a Feb 06 03:10:40 . /opt/lib/libWand.a /opt/lib/libjpeg.a /opt/lib/libmenu_g.a /opt/lib/libpng.la /opt/lib/libtiff.a Feb 06 03:10:43 . /opt/lib/libWand.la /opt/lib/libltdl.a /opt/lib/libncurses.a /opt/lib/libpng12.a /opt/lib/libtiff.la Feb 06 03:10:48 There's the hit-list on prodslug for native compiles Feb 06 03:11:32 once again for the record, not *all* .a files are bad Feb 06 03:12:09 right, but ones in /opt/lib are Feb 06 03:12:20 . -bash-2.05b$ ls /opt/armeb/armv5b-softfloat-linux/lib/*.la Feb 06 03:12:20 . /opt/armeb/armv5b-softfloat-linux/lib/libstdc++.la /opt/armeb/armv5b-softfloat-linux/lib/libsupc++.la Feb 06 03:12:27 those need to go Feb 06 03:12:27 There's the hit-list for crosstool-native. Feb 06 03:12:39 but for example, /opt/lib/libpcap.a Feb 06 03:12:46 there is no libpcap.so Feb 06 03:13:21 libtermcap.a - same Feb 06 03:13:22 right, but packages that need that can get it from staging Feb 06 03:13:34 oh right we did say that Feb 06 03:14:10 if that works, then we can add those rules to the packaging best practises page. Feb 06 03:14:31 night all Feb 06 03:14:35 `night Feb 06 03:15:53 hmm there is a downside to that policy tho Feb 06 03:15:59 But I still don't know how jp30 got it to build an ipk on cross-compile (cause he specifically added pkgconfig to cross-and-native ready for testing) Feb 06 03:16:19 what about ppl who want to do native devel not using unslung cvs ? Feb 06 03:16:30 for them, staging doesn't exist Feb 06 03:16:33 unfortunately, we don't support that. Feb 06 03:16:43 they're on their own. Feb 06 03:16:59 we have to draw a line somewhere. Feb 06 03:17:15 seems a bit harsh when all we need to do is be sure we don't move .a's from /opt/lib when there is no equivalent .so Feb 06 03:18:08 we can start with .la's Feb 06 03:18:10 ok, let's go with that compromise and see how many times we get back into this situation again with new developers Feb 06 03:18:23 just blow away .la's for the moment Feb 06 03:18:30 I think the la's are the big offender. Feb 06 03:18:40 nod Feb 06 03:18:45 I'm not sure if I've had a serious .a show-stopping incident. Feb 06 03:18:49 even .la's and the huge .a's with equivalent .so's I'm fine with Feb 06 03:18:59 some of those static libs are huge Feb 06 03:19:01 yep, me too Feb 06 03:19:08 Agreed. Feb 06 03:19:11 done Feb 06 03:19:15 night Feb 06 03:19:21 me too. Feb 06 03:19:24 I hope nobody notices the huge libperl.a Feb 06 03:19:26 :-) Feb 06 03:19:38 since we are building perl static for performance Feb 06 03:19:44 I'm kind of wondering how libmagick++ got it in there. Feb 06 03:20:01 I thought I specifically didnt compile that stuff in. Feb 06 03:20:09 15% performance decrease when using libperl.so Feb 06 03:20:15 Wow. Feb 06 03:20:26 Thats a pretty hefty penalty. Feb 06 03:20:34 but I understand why gentoo builds two perl packages - one is just to get the shared libperl, and the other is to get the fast perl binary Feb 06 03:20:59 it's real. I remember benchmarking Feb 06 03:21:04 but the 15% is in the docs Feb 06 03:21:18 don't jsut take my word for it :-) Feb 06 05:29:11 hi all Feb 06 05:32:05 03caplink811 * 10unslung/sources/openldap/ (postinst prerm rc.openldap): initial checkin Feb 06 05:33:09 Insomnia is Evil. Feb 06 05:34:40 03caplink811 * 10unslung/sources/openldap/control: add depencies Feb 06 05:37:37 03caplink811 * 10unslung/make/openldap.mk: add stages, checked ipk build **** ENDING LOGGING AT Sun Feb 06 05:39:56 2005