| 00:08.41 | *** join/#oe infobot (~infobot@rikers.org) |
| 00:08.41 | *** topic/#oe is OpenEmbedded Developer Lounge | Web: http://openembedded.org | Repositories: http://git.openembedded.org/ | Primary Repo Mirrors: https://github.com/openembedded | This is not a distro or machine support channel |
| 00:21.13 | *** join/#oe Vutral (ss@mirbsd/special/Vutral) |
| 00:31.32 | davor | nerdboy, I built yocto instead, thought that might work, but nope, when trying to boot rpi-basic-image, ACT lights up for a few seconds and that's it, no display output or anything. it's probably not booting given that the ethernet-related LEDs remain off even when powering up the RPi with a network cable attached |
| 00:42.59 | *** join/#oe Rootert (~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl) |
| 00:43.29 | *** join/#oe RagBal (~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl) |
| 01:07.16 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 01:21.52 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 01:28.55 | *** join/#oe liuyq (~liuyq0307@static-ip-225-98-134-202.rev.dyxnet.com) |
| 01:29.42 | *** join/#oe liuyq (~liuyq0307@static-ip-225-98-134-202.rev.dyxnet.com) |
| 01:40.17 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 01:46.13 | *** join/#oe johny_ (79321429@gateway/web/freenode/ip.121.50.20.41) |
| 01:46.17 | johny_ | hi |
| 01:50.09 | johny_ | i have build aminimal image and ogt rootfs, when i execute ldd <some .so file> it is showing that it is linking to some of system libraries... is it correct? for example |
| 01:50.41 | johny_ | ldd libsqlite3.so giving me this result |
| 01:50.42 | johny_ | <PROTECTED> |
| 01:51.03 | johny_ | why it is using my system libs? it should not happen as of my understanding.. |
| 01:51.11 | johny_ | any body has any idea on this.? |
| 01:55.56 | *** join/#oe slonsiki (~slonsiki@69-12-177-67.dsl.static.sonic.net) |
| 02:07.19 | *** join/#oe silviof1 (~silviof@ppp-93-104-14-226.dynamic.mnet-online.de) |
| 02:08.10 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 02:36.48 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 02:38.39 | johny_ | i have build aminimal image and ogt rootfs, when i execute ldd <some .so file> it is showing that it is linking to some of system libraries... is it correct? for example |
| 02:38.45 | johny_ | ldd libsqlite3.so giving me this result |
| 02:38.51 | johny_ | linux-gate.so.1 => (0xf76f1000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf76ca000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf76af000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7505000) /lib/ld-linux.so.2 (0xf76f2000) |
| 02:38.56 | johny_ | any body has any idea on this.? |
| 02:39.03 | *** join/#oe andre_d (~andre_d@82.220.1.204) |
| 02:49.02 | *** join/#oe liuyq (~liuyq0307@static-ip-225-98-134-202.rev.dyxnet.com) |
| 02:53.08 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 03:05.24 | *** join/#oe DJWillis (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginmedia.com) |
| 03:10.55 | *** join/#oe andyross (~andy@c-67-171-188-207.hsd1.or.comcast.net) |
| 03:49.19 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 04:22.04 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 04:35.43 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 05:06.14 | *** join/#oe ericben (~ebenard@pac33-3-88-170-243-169.fbx.proxad.net) |
| 05:17.34 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 05:21.51 | *** join/#oe zecke (~ich@91-65-247-193-dynip.superkabel.de) |
| 05:21.54 | *** join/#oe rsalveti (~rsalveti@unaffiliated/rsalveti) |
| 05:23.24 | *** join/#oe clio (~andrej@85.159.109.222) |
| 05:27.44 | *** join/#oe cbrake (~cbrake@oh-67-76-203-50.sta.embarqhsd.net) |
| 05:38.41 | *** join/#oe liuyq (~liuyq0307@static-ip-225-98-134-202.rev.dyxnet.com) |
| 05:48.23 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 05:51.39 | *** join/#oe tasslehoff (~tasslehof@77.40.182.98) |
| 05:53.29 | *** join/#oe mario_ (~mario@HSI-KBW-046-005-171-212.hsi8.kabel-badenwuerttemberg.de) |
| 06:02.03 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 06:16.47 | *** join/#oe liveforeverx (~Adium@2001:6f8:12d9:13:c96c:42a9:7f81:8407) |
| 06:21.09 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 06:27.18 | *** join/#oe mario_ (~mario@HSI-KBW-046-005-171-212.hsi8.kabel-badenwuerttemberg.de) |
| 06:35.50 | *** join/#oe blindvt (~brf@91-119-58-15.dynamic.xdsl-line.inode.at) |
| 06:57.31 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
| 06:59.43 | *** join/#oe dos11 (~dos@unaffiliated/dos1) |
| 07:01.03 | *** join/#oe mario_ (~mario@projekte.imos.net) |
| 07:08.45 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 07:18.27 | *** join/#oe DJWillis (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginmedia.com) |
| 07:26.21 | *** join/#oe darknighd (~darknight@nat-wv.mentorg.com) |
| 07:26.31 | *** join/#oe darknighte (~darknight@pdpc/supporter/professional/darknighte) |
| 07:31.28 | *** join/#oe stefan_schmidt_w (~stefan_sc@82.43.26.66) |
| 07:34.33 | *** join/#oe fgretief (~chatzilla@41.0.38.138) |
| 07:38.11 | *** join/#oe silvio_ (~silvio@93-57-17-124.ip162.fastwebnet.it) |
| 07:39.27 | *** join/#oe xmlich02 (~imlich@2001:67c:1220:80c:21c:c0ff:fe18:9398) |
| 07:40.37 | *** join/#oe BlindMan (~othmar@chello212017108125.6.11.vie.surfer.at) |
| 07:45.14 | *** join/#oe ant_work (~ant@host54-128-static.10-188-b.business.telecomitalia.it) |
| 07:47.28 | *** join/#oe panda84kde (~diego@static-217-133-170-65.clienti.tiscali.it) |
| 07:54.13 | *** join/#oe bluelightning (~paul@83.217.123.106) |
| 07:54.13 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 07:55.27 | *** join/#oe ao2 (~ao2@host5-148-dynamic.3-87-r.retail.telecomitalia.it) |
| 07:58.14 | bluelightning | morning all |
| 08:01.07 | silviof | hi morning bluelightning |
| 08:01.11 | silviof | morning #oe |
| 08:02.42 | bluelightning | morning silviof |
| 08:10.54 | silviof | I work on firefox-22 and have a license file with more than 10 licenses. How should I handle these? |
| 08:12.55 | bluelightning | silviof: if those are all of the licenses that apply they'll all need to be listed in LICENSE separated by & |
| 08:13.48 | silviof | bluelightning: okay |
| 08:13.57 | *** join/#oe ao2 (~ao2@87.13.159.77) |
| 08:15.49 | *** join/#oe florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 08:20.59 | silvio_ | morning all, hi bluelightning, hi silviof |
| 08:21.39 | bluelightning | hi silvio_ |
| 08:23.00 | silviof | hi silvio_ |
| 08:46.57 | *** join/#oe phdeswer_ (~phdeswer@a88-113-104-180.elisa-laajakaista.fi) |
| 08:58.34 | *** join/#oe blitz00 (~stefans@unaffiliated/blitz00) |
| 08:59.04 | *** join/#oe cbrake (~cbrake@oh-67-76-203-50.sta.embarqhsd.net) |
| 09:01.20 | *** join/#oe eren (~eren@unaffiliated/eren) |
| 09:01.28 | *** join/#oe ao2 (~ao2@host189-149-dynamic.6-87-r.retail.telecomitalia.it) |
| 09:13.57 | *** join/#oe BlindMan (~othmar@chello212017108125.6.11.vie.surfer.at) |
| 09:27.01 | eren | hi all |
| 09:27.39 | silviof | hi eren |
| 09:33.54 | bluelightning | hi eren |
| 09:35.13 | *** join/#oe ao2 (~ao2@host64-79-dynamic.57-82-r.retail.telecomitalia.it) |
| 09:40.15 | pb_ | morning all |
| 09:40.17 | *** join/#oe max (~max@host167-68-dynamic.54-79-r.retail.telecomitalia.it) |
| 09:40.52 | *** join/#oe pepermint (~pepermint@host167-68-dynamic.54-79-r.retail.telecomitalia.it) |
| 09:41.05 | eren | morning pb_ |
| 09:42.14 | bluelightning | hi pb_ |
| 09:44.16 | pb_ | hi eren, bluelightning |
| 09:44.58 | mckoan | good (late) morning |
| 09:49.43 | *** join/#oe liveforeverx (~Adium@2001:6f8:12d9:13:1c28:a977:6da8:42a5) |
| 10:07.02 | *** join/#oe ao2 (~ao2@host60-146-dynamic.6-87-r.retail.telecomitalia.it) |
| 10:09.49 | ant_work | pb_: I can imagine our rburton and bluelightning dazzled by the huge patchset |
| 10:11.12 | pb_ | ant_work: re the bluez thing, you mean? |
| 10:12.58 | ant_work | not specifically, this time seems harder than usual |
| 10:13.33 | eren | I'm lost on read-only-rootfs suppot |
| 10:13.38 | eren | will there be any documentation about it? |
| 10:13.50 | pb_ | it does seem as though Saul is having a bit of a hard time putting the right bits in his branch for some reason. |
| 10:14.01 | eren | I mean, in the technical side, how it is implemented, how it can be used, etc |
| 10:14.11 | pb_ | but, well, rburton and bluelightning are professionals, I'm sure they can cope. |
| 10:14.26 | eren | and we can help them :P |
| 10:14.44 | pb_ | eren: "how it can be used" is easy, it is for root filesystems that you can't write to (squashfs etc) |
| 10:15.02 | pb_ | it should just be a case of setting the appropriate IMAGE_FEATURE when you generate your rootfs. |
| 10:15.06 | eren | sure, I am wondering about the implementation actually |
| 10:15.16 | eren | it's hard to deduce from the commits |
| 10:16.38 | pb_ | well, there are various parts to it, but the basic idea is that any parts of the filesystem that need to be written to have a tmpfs bind-mounted on top of them. |
| 10:16.58 | pb_ | I'm not quite sure whether there is any plan to unify this with the unionfs stuff that's used for live images, or whether they will always remain separate. |
| 10:17.18 | pb_ | you can imagine that live images are, in some sense, just a special case of RoRs and possibly ought to be using the same mechanics. |
| 10:17.51 | ant_work | eren: I have tested one RO cramfs couple of months ago |
| 10:18.15 | ant_work | see, the NOR is locked and it was indeed RO ;) |
| 10:18.30 | ant_work | eren: it was just a core-image-base |
| 10:18.39 | eren | pb_: well, tmpfs bind-mounted on top of them? |
| 10:18.54 | *** join/#oe mrmcan (~mrcan@unaffiliated/mrcan) |
| 10:19.12 | ant_work | eren: wrt volatiles/tmpfs seems things have changed/are changing |
| 10:40.10 | *** join/#oe ao2 (~ao2@host143-140-dynamic.3-87-r.retail.telecomitalia.it) |
| 10:40.28 | ensc|w | ro nfs rootfs are really nasty to handle in userspace because the 'ro' flag is not exported by statvfs(). So systemd's ConditionPathIsReadWrite does not work and (unpatched) busybox 'test -w' fails too :( |
| 10:52.53 | *** join/#oe CMoH (~cipi@unaffiliated/c-moh) |
| 11:06.27 | *** join/#oe JaMa|Off (~martin@ip-62-24-80-145.net.upcbroadband.cz) |
| 11:07.58 | *** join/#oe liveforeverx (~Adium@2001:6f8:12d9:13:c8f0:5499:84a5:c9fc) |
| 11:14.18 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 11:40.06 | *** join/#oe ldnunes (~ldnunes_@187.23.155.55) |
| 11:40.47 | *** join/#oe DJW|Home (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginmedia.com) |
| 11:55.33 | *** join/#oe joeythesaint (~jjm@128.224.252.2) |
| 12:10.51 | *** join/#oe liveforeverx (~Adium@2001:6f8:12d9:13:b06f:462e:9398:2639) |
| 12:30.53 | *** join/#oe ao2 (~ao2@2001:1418:117::1) |
| 12:52.15 | *** join/#oe silviof1 (~silviof@ppp-188-174-179-148.dynamic.mnet-online.de) |
| 12:57.03 | *** join/#oe silviof2 (~silviof@ppp-188-174-147-50.dynamic.mnet-online.de) |
| 13:01.41 | *** join/#oe silviof3 (~silviof@ppp-93-104-168-44.dynamic.mnet-online.de) |
| 13:03.23 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 13:06.58 | *** join/#oe apelete_ (apelete@nat/intel/x-dkighsalselklrbq) |
| 13:08.20 | *** join/#oe silviof4 (~silviof@ppp-93-104-162-97.dynamic.mnet-online.de) |
| 13:10.08 | *** join/#oe silviof (~silviof@ppp-93-104-184-172.dynamic.mnet-online.de) |
| 13:18.02 | *** join/#oe mhnoyes (~mhnoyes@sourceforge/sitedocs/mhnoyes) |
| 13:29.03 | *** join/#oe silviof (~silviof@ppp-188-174-129-34.dynamic.mnet-online.de) |
| 13:42.36 | *** join/#oe Stygia (~gmpsaifi@0904ds6-noe.0.fullrate.dk) |
| 13:50.56 | *** join/#oe liveforeverx (~Adium@2001:6f8:12d9:13:a093:97d4:8c10:8555) |
| 14:03.11 | *** join/#oe ao2 (~ao2@2001:1418:117::1) |
| 14:14.50 | *** join/#oe flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 14:19.45 | *** join/#oe SoylentYellow (~SoylentYe@129.10.181.81) |
| 14:39.34 | *** join/#oe Crofton-bot (~supybot@pool-108-44-87-78.ronkva.east.verizon.net) |
| 14:39.42 | *** join/#oe Crofton|work (~balister@pool-108-44-87-78.ronkva.east.verizon.net) |
| 14:52.51 | *** join/#oe andyross (~andy@c-67-171-188-207.hsd1.or.comcast.net) |
| 14:59.40 | martiert | any ideas on why my kernel has its load address set differently when built through OE and manually using the OE built toolchain? |
| 14:59.40 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 15:00.23 | martiert | when building out of oe I get Load Address: 0x80008000, while in oe I get 0x00008000, which is strange |
| 15:00.26 | *** join/#oe hollisb (~hollisb@192.94.38.34) |
| 15:01.38 | martiert | same defconfig, same commit and no u-boot-mkimage relocation stuff |
| 15:01.47 | *** join/#oe dvhart (~dvhart@static-50-53-108-147.bvtn.or.frontiernet.net) |
| 15:03.03 | mckoan | bluelightning: is it time for TSC / Workgroup meeting? |
| 15:05.12 | bluelightning | mckoan: it's in 1 hour |
| 15:05.19 | bluelightning | mckoan: (well, 55 minutes) |
| 15:05.20 | Crofton|work | +1 |
| 15:05.27 | mckoan | so 18:00 CEST |
| 15:05.27 | Crofton|work | bluelightning, the bot should be good to go |
| 15:05.43 | *** join/#oe tomz2 (~trz@c-68-53-177-94.hsd1.in.comcast.net) |
| 15:05.55 | bluelightning | Crofton|work: great, I guess you'll be around to operate it? (since I don't know how...) |
| 15:06.06 | Crofton|work | ok |
| 15:06.08 | Crofton|work | I should be |
| 15:06.08 | mckoan | bluelightning: but in London now it's 16 (GMT) |
| 15:06.11 | bluelightning | s/guess/hope/ :) |
| 15:06.28 | Crofton|work | I got home late last night |
| 15:06.30 | bluelightning | mckoan: London is in BST now not GMT :) |
| 15:06.51 | mckoan | bluelightning: aha! now I understand, sorry |
| 15:07.57 | mckoan | http://www.worldtimebuddy.com/utc-to-bst-converter |
| 15:08.00 | *** join/#oe rburton (~rburton@35.106.2.81.in-addr.arpa) |
| 15:11.03 | *** join/#oe liveforeverx (~Adium@89.204.130.253) |
| 15:14.17 | *** join/#oe zenlinux (~sgarman@c-24-20-145-95.hsd1.or.comcast.net) |
| 15:36.06 | pb_ | martiert: I guess you should diff the linker scripts and the final link command line to see what's going on. |
| 15:42.45 | martiert | pb_: Which linker scripts are you thinking of? the ones in the kernel, or someone in oe? |
| 15:43.31 | pb_ | The ones in the kernel |
| 15:44.49 | martiert | yes, I can do that. Do you know if there are anyting in oe which is changing the way it's linked though? cause I though we were doing unset CFLAGS CXXFLAGS LDFLAGS when building the kernel |
| 15:47.03 | pb_ | I can't think of anything. But if it behaves differently, and you're using the same tools, then it stands to reason that there must be something. |
| 15:47.25 | martiert | true, but I'll try that, and see if the link line is weird |
| 15:47.47 | martiert | thansk |
| 15:49.11 | martiert | just thought it was so weird, so maybe someone had seen something similar. being that the only difference is the first 8, which is a lot of bytes, but still only one number:P |
| 15:55.40 | bluelightning | hey all, just a reminder: in about 5 minutes we'll be starting the public TSC meeting in this channel |
| 15:56.55 | bluelightning | http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg32103.html |
| 15:59.19 | *** join/#oe Jefro (~jefro@50-0-152-82.dedicated.static.sonic.net) |
| 16:00.47 | bluelightning | morning Jefro |
| 16:00.54 | fray | morning |
| 16:01.17 | Jefro | bluelightning good morning |
| 16:01.38 | Jefro | seems quiet here. too quiet... |
| 16:01.51 | sgw_ | Morning |
| 16:02.07 | mckoan | morning all |
| 16:02.58 | Crofton|work | bluelightning, let me know when you want to start |
| 16:03.02 | bluelightning | Jefro: probably a little bit late for me to be asking but do you have an agenda for this meeting? |
| 16:03.16 | bluelightning | Crofton|work: we should be starting now |
| 16:03.30 | Crofton|work | shall I start the bot then? |
| 16:03.49 | bluelightning | Crofton|work: yes please |
| 16:03.51 | Crofton|work | #startmeeting |
| 16:03.52 | Crofton-bot | Meeting started Tue Jul 30 16:03:52 2013 UTC. The chair is Crofton|work. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 16:03.52 | Crofton-bot | Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 16:04.01 | Crofton|work | the url has some docs |
| 16:04.19 | Crofton|work | you can use the topic command for agenda items |
| 16:04.41 | Jefro | bluelightning yes, in just a sec - poll for new issues and I'll put them on the agenda before posting |
| 16:04.54 | fray | Welcome.. Jefro is our normal TSC note taker.. he is just finishing up the base agenda items now.. |
| 16:04.56 | Crofton|work | give me an action item to work with ka6sox to find a way to upload minutes to the oe website |
| 16:05.01 | fray | but while he does so, new issues are welcome.. |
| 16:05.46 | fray | our normal first task is to identify the meeting chair.. So we should probably do that quickly.. |
| 16:06.16 | fray | koen msg'd me a couple of minutes ago that he'd be right back.. |
| 16:06.46 | fray | I believe Khem, Bluelightning and myself are here. |
| 16:06.51 | *** join/#oe NightMonkey (~NightrMon@pdpc/supporter/professional/nightmonkey) |
| 16:06.55 | fray | RP is on vacation |
| 16:08.03 | fray | while the others get setup. Let me explain what we're trying to do today. |
| 16:08.08 | fray | http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg32103.html |
| 16:08.38 | fray | As mentioned in the email from Paul (on behalf of the entire Technical Steering Committee) we want to work on evoling the role of the OE-TSC. |
| 16:09.12 | fray | We thought that starting to have at open meetings with the users (not just oe members) would be a good start. |
| 16:10.25 | mckoan | fray: I agree, but depends on how much users care about meetings ;-) |
| 16:10.29 | bluelightning | the idea is to get other folks in the community more involved in the "taskforce" type operations that the TSC have been taking on |
| 16:11.01 | fray | and that is one of the purposes of this meeting as well. Many people aren't going to care. So if after we're done it wasn't useful. We likely won't do it again.. (or at least not in this format) |
| 16:11.29 | Crofton|work | I feel this is a good habit to get into, and expect people to become more involved over time |
| 16:11.55 | darknighte | is monitoring the meeting |
| 16:12.03 | fray | The TSC needs to change it's role from being a group of people leading specific implementation/work products into an actual technical steering committee who can help the community at large... |
| 16:12.19 | *** join/#oe mr_science (~sarnold@net-cf9a4e91.cst.impulse.net) |
| 16:12.19 | *** join/#oe mr_science (~sarnold@gentoo/developer/nerdboy) |
| 16:13.18 | bluelightning | fray: so we're 13 mins in, I'd say you're probably chairing ;) |
| 16:13.28 | fray | sounds good to me. :) |
| 16:13.42 | *** join/#oe denix0 (~denys@192.94.92.11) |
| 16:13.46 | fray | We normally just allow someone to take the lead as the chair of the meeting.. so I guess it's my turn |
| 16:14.07 | denix0 | re |
| 16:14.07 | fray | while Jefro finishes up on the formal agenda. The first item in the list was to introduce some of the 'janitor' items. |
| 16:14.38 | fray | For a while the TSC has been seeing a list of items grow (and luckily shrink) that cover various cleanup and janitorial tasks. |
| 16:14.58 | fray | We're like to introduce a more formal way for people to find outstanding cleanup tasks and be able to work on them. |
| 16:15.02 | Crofton|work | fray, say #topic Janitor Items |
| 16:15.05 | Jefro | TSC agenda is here: http://pastebin.com/KMhtNHpC |
| 16:15.23 | fray | #topic Janitor items |
| 16:15.49 | fray | On the pasted agenda, there are two links referenced: |
| 16:15.54 | fray | http://openembedded.org/index.php/OpenEmbeddedJanitors |
| 16:16.10 | bluelightning | that page is kind of ancient ;) |
| 16:16.19 | fray | a wiki page started to help people idenfiy and discuss Janitorial work.. so far it's not been used much, but it also isn't well know.. |
| 16:16.24 | fray | and yes.. ancient in many ways.. |
| 16:16.52 | fray | and for those that pay attention to the Yocto Project bugzilla, various bugs get tagged with an owner, cc that contains 'janitor' to help identify future work. |
| 16:16.57 | fray | http://bit.ly/11sfn5Y |
| 16:17.16 | bluelightning | right, the Yocto Project has also been tracking janitor items: https://wiki.yoctoproject.org/wiki/Janitors |
| 16:17.24 | fray | bluelightning thanks, I missed that URL |
| 16:17.56 | bluelightning | I'll be honest though, that list has remained largely static for quite some time, so it's not really achieving much |
| 16:18.22 | eren | as a newly joined contributer, I want to make a comment on Janitor jobs |
| 16:18.27 | eren | is it possible? |
| 16:18.28 | bluelightning | i.e. usually "janitor" type items are a way of bringing new contributors up-to-speed on a project, but that hasn't really been happening |
| 16:18.35 | bluelightning | eren: certainly :) |
| 16:18.37 | fray | eren, please.. |
| 16:18.52 | eren | I didn't know about the url on OpenEmbedded wiki, which are more likely to be janitor jobs |
| 16:19.09 | eren | the jobs in Yocto page are a bit complex for newly joined people |
| 16:19.29 | bluelightning | the first item on the OE page is no longer valid, I'm about to remove it |
| 16:19.32 | eren | I would suggest chosing some mechanical jobs at first and collect them on wiki |
| 16:19.49 | fray | eren, I was assigned the task to start working on publicising janitorial tasks, but alas, the implementation side of my work has gotten in the way.. |
| 16:19.50 | eren | and add a link to how to contribute/send patches to ML :) |
| 16:20.22 | fray | So this is really the first opportunity for most people to see what we thing is a good way to get people involved and help those looking for something to do, with a possible list. |
| 16:20.45 | *** join/#oe hillct (~hillct@c-24-34-200-20.hsd1.ma.comcast.net) |
| 16:20.46 | fray | we also want ot make sure that if people find inconsistencies, things that need cleanup -- there is a way for them to post about them and add it to the list of future work |
| 16:21.07 | fray | eren, I agree.. |
| 16:21.14 | *** join/#oe soltys (soltys@84-10-244-33.dynamic.chello.pl) |
| 16:21.15 | eren | there was a page on how to send patches that bluelightning posted when I asked |
| 16:21.17 | fray | we'll add that to the todo |
| 16:21.20 | eren | but I cannot find it on wiki |
| 16:21.23 | bluelightning | eren: right, we should definitely do that, good idea... FYI this page is up-to-date: http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded |
| 16:21.33 | eren | I guess adding keywords would help |
| 16:21.43 | eren | bluelightning: ah! that's on OE then, I was looking at Yocto wiki |
| 16:22.12 | bluelightning | we should probably have back-links from the Yocto Project wiki to that page |
| 16:22.38 | eren | yeah, I guess so |
| 16:22.42 | bluelightning | and yes, mediawiki often requires explicit keywords because its searching is somewhat simplistic |
| 16:22.45 | mckoan | I didn't know janitor wiki page too |
| 16:22.45 | fray | this leads me to one of the janitor tasks that is sorely needed. We need help keeping the wiki up to date, along with making it easier for new users to find what they need.. |
| 16:23.01 | bluelightning | indeed |
| 16:23.05 | denix0 | +1 |
| 16:23.17 | fray | there is still a lot of oe-classic information that we need to ensure people understand is older.. |
| 16:23.41 | bluelightning | FWIW most of the outdated info is at least marked as such with a bold notice at the top of the page |
| 16:23.42 | mckoan | keep doc stuff up to date is definitely the first thing to do |
| 16:23.48 | bluelightning | but that's only step one of course :) |
| 16:23.48 | fray | yup |
| 16:24.18 | Jefro | #action Crofton_work talk with ka6sox about uplaoding to the website |
| 16:24.28 | eren | you can add old oe variables that we need to be careful about in Styleguide? |
| 16:24.31 | eren | or packaging guide? |
| 16:25.19 | fray | #action update janitor page with up-to-date information, make sure it's referenced on the main page |
| 16:25.50 | denix0 | Jefro: what exactly do you mean? do you mean loosening restrictions on wiki? |
| 16:26.08 | bluelightning | eren: hmm... we do maintain this, not sure if it helps in that regard: http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core |
| 16:26.26 | bluelightning | eren: we also have a migration section in the YP reference manual for releases |
| 16:26.46 | bluelightning | eren: that at least covers changes people need to make to their recipes/configuration |
| 16:27.20 | fray | looks at the clock.. is there more discussion on this or should we move on |
| 16:27.28 | eren | bluelightning: ah yep, that would definitely help |
| 16:27.28 | Crofton|work | denix, getting things setup so I can rsync the minutes directly yo a server |
| 16:27.50 | denix0 | Crofton|work: got it |
| 16:28.13 | bluelightning | fray: I think we should probably move on, but we should carry on thinking/working on the janitor list |
| 16:28.23 | *** join/#oe davest (Adium@nat/intel/x-dfynalpalbvmlore) |
| 16:28.35 | fray | yes please.. anyone has any suggestions contact the TSC and/or post on the oe list(s).. |
| 16:28.58 | fray | I would think that all of the oe items, wiki, oe-core, meta-oe could likely use something like this.. or even a common page divided by area.. |
| 16:29.03 | fray | ok.. on to the next thing.. |
| 16:29.18 | fray | 3a.. role of the TSC.. we already covered this a bit, and some may have seen the discussion on the oe-members list. |
| 16:29.32 | Crofton|work | fray, use #topic :) |
| 16:30.03 | fray | #topic 3a.. role of the TSC |
| 16:30.33 | fray | We want to work on transitioning from a group trying to figure out what is needed and working on getting us there.. to thinking about strategic direction and long term vision. |
| 16:30.42 | Jefro | wonders how he didn't know about meetbot before |
| 16:31.01 | fray | We're looking from feedback from both oe users and members on our role. |
| 16:31.40 | denix0 | Jefro: you were the bot! :) |
| 16:31.47 | *** join/#oe dos11 (~dos@unaffiliated/dos1) |
| 16:31.55 | fray | just to be clear our own plans for the TSC do not include meeting just for the sake of it. We do want to actually accomplish something. |
| 16:32.08 | Crofton|work | +1 |
| 16:32.09 | fray | feedback? |
| 16:32.10 | denix0 | Jefro: we didn't have you at the board meetings, so we needed to find something... :) |
| 16:32.53 | Crofton|work | otavio, made me figure it out :) |
| 16:32.59 | mckoan | fray: of course, but people not used to meet with TSC may need time to adapt to it |
| 16:34.45 | bluelightning | mckoan: right, this may take some time for us all to get used to :) |
| 16:34.52 | fray | ;) |
| 16:35.02 | *** join/#oe zenlinux (~sgarman@c-50-139-96-211.hsd1.or.comcast.net) |
| 16:35.40 | fray | I think many, if not all of the TSC members in the last couple of years had a vested interest in bootstrapping oe-core.. We are well beyond that point now.. so in my opinion, it's time for the group to evolve.. |
| 16:36.32 | fray | since I don't see much feedback, I'll ask this in another way.. does anyone -disagree- with the TSC changing it's role more toward a medium vision/long term vision, and technical dispute resolution group.. |
| 16:36.42 | fray | (we also help with some infrastructure decisions and issues as well..) |
| 16:36.49 | *** join/#oe challinan (~challinan@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net) |
| 16:37.18 | rburton | token statement to show some form of participation: no, i don't disagree with that. :) |
| 16:37.20 | kergoth | I'm 100% in favor of strategic direction and long term vision being a focus |
| 16:37.39 | Jefro | fray I had a question. The TSC also manages many technical projects. What happens to those? |
| 16:37.54 | fray | That was my next question.. :) |
| 16:38.45 | Crofton|work | what are these technical projects? |
| 16:39.39 | fray | in the past we've done some of the janitorial tasks, helped with the merge of code from meta-oe to oe-core... |
| 16:40.19 | fray | we had mentioned in past meetings that this type of work transition to more of a working group format. Which we may or may not be directly involved with... but which we -will- need community involvement |
| 16:40.47 | kergoth | from a user perspective (not being in the tsc in some time), one thing that's bugged me about how the tsc has been working is the fact that agenda items seem to stick around indefinitely without seeing any form of completion. maybe its mostly those projects, but it gives one an impression ofa lack of progress, reading the notes, imo |
| 16:41.23 | fray | in many cases, that is exactly it.. the items were on-going "projects" |
| 16:42.14 | Jefro | kergoth that may be partly my bug presentation-wise |
| 16:42.42 | Jefro | discussion points != projects. I can present it more as a project manager would if that helps. |
| 16:42.56 | bluelightning | kergoth: this is one of the reasons for us asking for wider involvement in those projects, since some of them have been difficult for us to make progress on on our own; usually it's not for lack of decisions, but lack of time to work through changes |
| 16:44.19 | mckoan | discussion points are often too synthetic |
| 16:45.02 | mckoan | who read them from outside of TSC oftern don't realize their actual purpose |
| 16:45.27 | mckoan | maybe a little lack of description/documentation |
| 16:45.44 | bluelightning | for instance, we've been struggling with trying to get the last few bbappends/overlayed recipes from meta-oe for some time now, and it's been *really* hard to get people to help with that |
| 16:45.47 | fray | yes.. and I think vision fits into a better way of doing what we have been (from the outside) while a working group would be better for actual 'work' and involvement |
| 16:46.43 | bluelightning | I'll admit that that particular thing is something I personally feel strongly about, perhaps it bothers others less |
| 16:49.13 | fray | (sorry my network is glitching here...) |
| 16:49.30 | fray | Is there an output of this discussion, at this point? |
| 16:50.26 | mckoan | the main problem with adopt these big changes is that there usually aren't guidelines, apart for those wrote by bluelightning (afaik) |
| 16:50.26 | *** join/#oe fray_ (~mhatle@206.144.70.9) |
| 16:50.41 | fray | we need to better convey the points as to their meaning, tsc role change is generally accepted, working groups (right approach, wrong or TBD?) |
| 16:50.50 | bluelightning | fray: we haven't stated as such, but if there are items that the TSC would normally take on, we need to get them identified and find a way of pulling in interested folks to get them resolved |
| 16:51.01 | fray | agreed |
| 16:51.08 | bluelightning | fray: TBD probably |
| 16:51.13 | fray | ok.. |
| 16:51.17 | kergoth | working groups seem like a decent approach to pursue the actual implementation of the decisions |
| 16:51.18 | Crofton|work | list conclusions as #info or #action |
| 16:51.19 | fray | we've got about 9 minutes left.. |
| 16:51.20 | kergoth | shrugs |
| 16:51.38 | fray | I'd like to continue and we can come back to this if there is time.. |
| 16:51.44 | fray | #topic 3b - eglibc |
| 16:51.54 | fray | This is more of an FYI topic to folks.. it's working that we need to continue to track. |
| 16:52.15 | fray_ | If you are not already aware, the eglibc work is being merged into the glibc proper. |
| 16:52.16 | fray_ | http://www.eglibc.org/archives/patches/msg01299.html |
| 16:52.26 | *** join/#oe dvhart (dvhart@nat/intel/x-wkyqcdmqvlkmbekr) |
| 16:52.30 | mckoan | this topic is freightening me, someone could give more information? |
| 16:52.42 | fray_ | This may affect us via the configuration of eglibc, mklibs phase out, etc.. |
| 16:52.45 | mckoan | why is this migration required? |
| 16:53.01 | fray_ | IF these items are needed by people, they will need to get involved with the upstream eglibc project.. express what they need and likely help maintain the work |
| 16:53.10 | khem | well nothing to worry about mckoan |
| 16:53.12 | fray_ | The migration is happening by the current maintainers of the eglibc project. |
| 16:53.25 | pb_ | mckoan: mostly because the original need for eglibc has basically evaporated, and maintaining two competing forks of the same code is a waste of time. |
| 16:53.26 | fray_ | All of the code that can be, is going to be merged into glibc itself.. |
| 16:53.28 | khem | we use certain features in OE which are less used |
| 16:53.30 | fray_ | pb_ exactly |
| 16:53.36 | eren | pb_: Ulrich? |
| 16:53.41 | khem | and therefore we either pick up maintaining them or they go away |
| 16:53.51 | fray_ | Ulrich is no longer the maintainer of glibc AFAIK |
| 16:53.52 | bluelightning | khem: I'm not completely clear, will this mean the items in DISTRO_FEATURES_LIBC cease to exist, or are reduced, or no change there? |
| 16:54.02 | eren | I guess that was *one of* the reasons behind eglibc fork |
| 16:54.10 | mckoan | fray: link catched thx, I'll read it later |
| 16:54.14 | khem | bluelightning: I will upstream the patches into glibc |
| 16:54.22 | khem | and maintain them ther e |
| 16:54.34 | fray_ | bluelightning at present, the items in the distro_features_libc, which correspond to their 'option group' support will be affected without someone coming in to maintain the work |
| 16:54.37 | denix0 | eren: Ulrich is gone long time ago |
| 16:54.53 | khem | however it would be better to have some sense of userbase |
| 16:54.55 | bluelightning | khem: excellent, thank you... so the impact on us should be relatively minor then? |
| 16:54.57 | fray_ | Option groups, in eglibc, are the way to disable functionality in order to save space. (Very much like how uclibc is configurable) |
| 16:55.08 | khem | if there are few use cases then it may not be worth the time |
| 16:55.29 | khem | bluelightning: yes impact to us is minor given we have prevelant usecases |
| 16:55.39 | khem | however this is an item for 2.19 release |
| 16:55.45 | fray_ | it's unclear at present how many people actual use the option groups, (our LIBC configuration). Based on previous responses to queries the numbers are small enough that the eglibc maintainers will be deprecating support over the next release or so.. (think 6-12 months) |
| 16:56.19 | darknighte | eren: fray_ : AFAIK, Ulrich's departure is part of what has opened the door to the merging of eglibc/glibc. |
| 16:56.24 | fray_ | we're trying to make sure this doesn't come as a surprise to anyone.. and if the functionality is absolutely needed, we (the OE project) will need to either take over maintenance and/or take the patches outselves.. |
| 16:56.26 | fray_ | darknighte correct |
| 16:56.28 | khem | fray_: yes if userbase is smaller then merging this into glibc might not be as appealing |
| 16:57.04 | khem | I think most impacted distro in OE universe would be poky tiny |
| 16:57.14 | fray_ | concerns/comments.. we should move to the oe-core list on this.... |
| 16:57.27 | bluelightning | right, it was raised there but there wasn't a lot of discussion IIRC |
| 16:57.32 | fray_ | khem, thats the one I know of at least.. my commercial distro may be affected as well.. |
| 16:57.44 | khem | fray_: I see. |
| 16:57.59 | fray_ | the hardest part in this is gauging usage.. if nobody cares then removing the functionality really shouldn't matter.. |
| 16:58.10 | khem | I will initiate an email thread on oe-core/oe-devel and seek feedback on this feature |
| 16:58.13 | fray_ | but we need to avoid removing it, and then having a huge backlash.. |
| 16:58.15 | pb_ | It's fairly hard to see why anybody would rationally care. |
| 16:58.42 | fray_ | pb_ there still are some memory constrained systems, but that is becoming significantly less 'normal' then it was evern 2 years ago |
| 16:58.43 | darknighte | pb_: there's always someone with their special case. |
| 16:58.43 | bluelightning | I was hoping for response from Darren since he dug into this in excruciating detail during his work on poky-tiny |
| 16:58.44 | khem | pb_: hard to say, I dont know what everybody uses |
| 16:58.50 | pb_ | I can imagine there are people using that feature due to inertia or "because it's there", but I find it fairly hard to believe there are many (perhaps even any) users whose lives would be seriously spoiled by not having it. |
| 16:59.01 | bluelightning | dvhart ^ |
| 16:59.02 | darknighte | pb_: question is how loud they scream and how hard it is to get them to work around it. |
| 16:59.10 | khem | then there is uclibc too |
| 16:59.11 | pb_ | fray_: well, right, but anybody with serious memory contraints is probably not using any form of glibc anyway. |
| 16:59.19 | khem | for smaller root file systems |
| 16:59.24 | khem | so I kind of agree |
| 16:59.26 | dvhart | bluelightning, hey |
| 16:59.29 | dvhart | just joined |
| 16:59.34 | dvhart | what am I looking for? |
| 16:59.36 | fray_ | I have customers who are.. they are able to pair glibc down to the size of a 'larger' uclibc system.. |
| 16:59.42 | khem | dvhart: poky tiny |
| 16:59.47 | darknighte | seems like it would make sense to drop it and see who screams. |
| 16:59.48 | bluelightning | dvhart: we've been discussing the potential removal of eglibc option groups and its possible impact on setups such as poky-tiny |
| 16:59.51 | fray | ok.. time check.. 1 minute to go on my clock |
| 16:59.55 | darknighte | with fair warning of course. |
| 16:59.56 | denix0 | eren: http://lwn.net/Articles/488847/ |
| 16:59.59 | khem | what impact will it have if we threw away LIBC_FEATURES |
| 17:00.23 | dvhart | right, so fray responded to that pretty well I thought |
| 17:00.30 | dvhart | those are core to poky-tiny |
| 17:00.35 | dvhart | without them we have two options |
| 17:00.35 | khem | can you consider uclibc instead ? |
| 17:00.38 | dvhart | 1 static linking |
| 17:00.40 | dvhart | 2 uclibc |
| 17:00.50 | fray_ | ok.. so we have remaing projects in progress status and infrastructure.. do we want to skip these or try to cover them quickly.. |
| 17:00.58 | khem | static linking with eglibc/glibc is more or less unsupported |
| 17:01.13 | khem | fray_: we can skip |
| 17:01.13 | bluelightning | fray_: let's cover them very quickly |
| 17:01.18 | fray_ | ya.. static linking also results in a (more then one binary) system using -more- memory |
| 17:01.18 | eren | denix0: thanks! |
| 17:01.19 | bluelightning | or skip :) |
| 17:01.29 | Crofton|work | let me know when you are done |
| 17:01.33 | *** join/#oe fgretief (~chatzilla@196-215-192-74.dynamic.isadsl.co.za) |
| 17:01.34 | dvhart | There is also this little gem :-) http://www.linuxjournal.com/article/5457 |
| 17:01.35 | fray_ | isn't a fan of uclibc in a commercial setting either |
| 17:02.04 | dvhart | fray, khem, I haven't done enough research to fully understand the impact/compatibility/etc of using uclibc |
| 17:02.06 | mckoan | uclibc should exist only as option |
| 17:02.20 | dvhart | I don't know where it breaks down, what it's lacking, which corners it cuts, etc |
| 17:02.23 | fray_ | ya.. the mklibs optimization may be impacted as well.. (likely won't be easy anymore) |
| 17:02.24 | bluelightning | dvhart: I didn't realise you'd been working on this angle over a longer time period ;) |
| 17:02.29 | dvhart | and frankly, the fact that I don't know, means I don't want to use it |
| 17:02.32 | dvhart | bluelightning, ;-) |
| 17:02.40 | khem | dvhart: this predates NPTL |
| 17:02.44 | fray_ | ok.. further discussion we can do off meeting.. we're past the hour |
| 17:03.01 | dvhart | it was an odd sort of project when IBM was dabbling in embedded |
| 17:03.04 | khem | and maintainer's dislike for static libc |
| 17:03.05 | fray_ | lets take two minutes to cover the project status and then call it done. |
| 17:03.06 | bluelightning | fray_: OK, thanks for chairing |
| 17:03.10 | fray_ | #topic 4a - oe-core release |
| 17:03.23 | dvhart | ok, I think I'm interrupting here |
| 17:03.36 | fray_ | We are currently aligning with the Yocto Project for the most part (and they are in turn aligning with us).. |
| 17:03.55 | fray_ | We're looking at roughly October for the next release, with a stablization period prior to release. |
| 17:04.15 | fray_ | I don't have further information, Richard is usually the one who has more detailed plans.. |
| 17:04.44 | darknighte | fray_: any significant changes expected? |
| 17:04.51 | fray_ | my personal expectations is a lot of the large churn should be done by late august |
| 17:05.06 | fray_ | darknighte not that I know of. The big changes (toolchain specifically) are already in place.. |
| 17:05.29 | darknighte | fray_: that's what I was hoping. |
| 17:05.31 | fray_ | I know there are some bitbake (webhob) and other changes in progress, but I don't think they will be terribly disruptive.. |
| 17:05.54 | fray | On to the next.. |
| 17:06.02 | fray | #topic 4b - meta-oe appends/overlay |
| 17:06.11 | fray | Bluelightning -- ? |
| 17:06.23 | bluelightning | no status change on that |
| 17:06.50 | fray_ | this is something I think we'd like to be a regular working group topic.. |
| 17:07.05 | fray_ | merging meta-oe to oe-core.. and working on places where there may be functional differences.. for alignment.. |
| 17:07.10 | fray_ | #topic 4c - python 3 |
| 17:07.33 | fray_ | there are two items here.. one is introducing python 3 into oe-core (as a recipe), which I believe Khem is currently sending to the list.. |
| 17:07.45 | darknighte | agrees with fray_ on the working group topic idea for meta-oe |
| 17:07.47 | fray_ | the other is eventually moving bitbake to python3. We've said that will not happen prior to the current release.. |
| 17:08.02 | fray_ | (october) but likely will be an issue for early in the next development cycle |
| 17:08.09 | fray_ | khem, anything to add? |
| 17:08.21 | pb_ | when you say "moving to", do you mean "working with" or "requiring"? |
| 17:08.37 | fray_ | moving to -- as the required python version for bitbake |
| 17:09.16 | fray | moving on.. |
| 17:09.24 | darknighte | There will almost certainly be significant pushback on the move to python 3. |
| 17:09.27 | kergoth | note that we might be able to keep supporting 2.x with 3to2 if need be |
| 17:09.55 | fray_ | darknighte we're aware of that.. we (oe) need to figure out if even next release is an appropriate time to do thsi |
| 17:09.58 | fray | #topic 4d - release status notification |
| 17:10.03 | bluelightning | kergoth: pb_: AFAIK RP's thinking was that it wouldn't be practical but I don't know if he was looking at 3to2 |
| 17:10.19 | darknighte | fray_: I agree. Just want to air the obvious... |
| 17:10.26 | fray | RP, prior to vacation was trying to provide regular status information to the list. We expect this to resume.. |
| 17:10.36 | fray | and I think that's it.. we're going to skip #5 |
| 17:11.27 | fray | final comments.. if people think this is useful.. we'd like to do something like it approx once a month.. (or if thats too often, once every other month) |
| 17:11.35 | Crofton|work | I think a lot of people will be on vacation over the next month btw |
| 17:12.07 | fray | ok.. meeting done! Thanks all |
| 17:12.20 | Crofton|work | #endmeeting |
| 17:12.21 | darknighte | As Crofton|work says, I think a lot of people will be out. |
| 17:12.21 | Crofton-bot | Meeting ended Tue Jul 30 17:12:21 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 17:12.21 | Crofton-bot | Minutes: oe/2013/oe.2013-07-30-16.03.html |
| 17:12.21 | Crofton-bot | Minutes (text): oe/2013/oe.2013-07-30-16.03.txt |
| 17:12.21 | Crofton-bot | Log: oe/2013/oe.2013-07-30-16.03.log.html |
| 17:12.24 | fray | 12 minutes over.. :/ we'll work on doing it better next time |
| 17:12.25 | bluelightning | thanks all |
| 17:12.34 | *** join/#oe tgall_foo (~tgall@linaro/tgall-foo) |
| 17:12.38 | darknighte | fray: almost a linear offset from when it got started, no? |
| 17:12.43 | fray_ | darknighte ya.. we might factor that into NOT doing it next month |
| 17:12.50 | fray_ | darknighte :) |
| 17:12.56 | darknighte | indeed ;) |
| 17:13.05 | mckoan | thanks all |
| 17:13.31 | mckoan | are you going to post minute on ML? |
| 17:13.49 | darknighte | mckoan: I think Crofton|work was planning to post them to the website... |
| 17:14.45 | mckoan | thanks |
| 17:14.49 | Crofton|work | I will send to Jefro and will work with ka6sox so I can rsync them somewhere |
| 17:15.17 | mckoan | Crofton|work: today worked as the meta-bot ;-) |
| 17:15.54 | denix0 | mckoan: that would be Crofton-bot... |
| 17:16.10 | dvhart | fray, are you subscribed to the eglibc mailing list? If so, would you mind replying to the thread on the libc option groups, adding me to Cc, with something like "Darren, how would this impact poky-tiny?" to give me an entry point into the discussion? |
| 17:16.31 | mckoan | denix0: yep :-D |
| 17:16.44 | darknighte | denix0: ahh, but Crofton|work is the meta-bot to take the Crofton-bot capture and post it via Jefro... |
| 17:16.55 | denix0 | dvhart: who needs an introduction? :) |
| 17:17.04 | fray_ | dvhart I have responded in the past.. you should be able to just jump in though.. |
| 17:17.06 | dvhart | denix0, I'm not subscribed |
| 17:17.11 | fray_ | I can find a few of them and point you to the list archive |
| 17:17.16 | dvhart | so I need a way to respond to the thread |
| 17:17.16 | denix0 | darknighte: it's a meta-world! |
| 17:17.29 | fray_ | http://www.eglibc.org/archives/patches/msg01299.html thats the current thread.. |
| 17:17.31 | dvhart | I don't see a way to do that from the archives... |
| 17:17.33 | eren | dvhart: you will probably miss some e-mails from people who do not reply to "all" |
| 17:17.44 | dvhart | eren, I *will* subscribe |
| 17:17.53 | eren | ah okkie :) |
| 17:17.54 | dvhart | but I was not subscribed when the thread started |
| 17:18.05 | eren | yeah, I guess someone needs to CC you in the thread |
| 17:18.10 | fray_ | http://www.eglibc.org/archives/patches/msg01274.html |
| 17:18.12 | dvhart | right, that :-) |
| 17:18.21 | eren | or you can get Thread-ID and inject that header to your mail :P |
| 17:18.44 | dvhart | I was looking for the Thread-ID and didn't find it |
| 17:18.46 | fray_ | my follow up to that last was sending the email to the oe-core list asking about eglibc usage |
| 17:18.47 | eren | sure, there is no Message-ID or Reply-To in web interface, better get CCed, hehe |
| 17:19.03 | dvhart | fray_, right, I figured I should respond directly to the eglibc list |
| 17:20.34 | mr_science | anybody currently building/using nginx? |
| 17:21.13 | mr_science | i could only find recipes in some oe-rascal repo (not even sure what a rascal is) |
| 17:21.42 | fray_ | darren, I forwarded you three emails from that original thread, complete with message id's |
| 17:21.58 | fray_ | ignore them if you've already figured out how |
| 17:22.05 | mr_science | of course it has its own funky configure setup and doesn't build at all in oe-classic... |
| 17:22.14 | dvhart | heh, OK, I'll see if I can find a mailer that will let me hand edit the thread-id.... |
| 17:22.25 | fray_ | make that 4.. ;) |
| 17:22.37 | mckoan | have a nice rest of the day |
| 17:22.38 | bluelightning | mr_science: hmm... haven't heard of anyone working on that at least discussion I've seen |
| 17:22.55 | bluelightning | mr_science: a recipe for it would be welcome in meta-webserver though FWIW |
| 17:23.38 | eren | building nginx should be straightforward, btw? |
| 17:24.08 | eren | depends on which modules you want to enable, which would include lots of PACKAGECONFIG variables, hehe |
| 17:25.33 | eren | is anyone packaging it? |
| 17:27.18 | bluelightning | bbl |
| 17:28.55 | mr_science | eren: i don't think so... |
| 17:29.41 | mr_science | building would be straightforward if it didn't use such a funky config setup full of oddball hardcoded paths |
| 17:30.11 | mr_science | so i'll need to patch a few things before i can say much more... |
| 17:31.09 | mr_science | just trying to make sure someone else hasn't already done it |
| 17:31.12 | eren | mr_science: well configure script seems to work |
| 17:37.54 | Crofton|work | Jefro, minutes are on the way |
| 17:38.39 | Jefro | ok, thanks |
| 17:39.03 | Crofton|work | hmm, topic did nothing |
| 17:40.11 | *** join/#oe martiert_ (~martin@59.37-191-128.fiber.lynet.no) |
| 17:43.03 | mr_science | eren: which version? |
| 17:43.52 | mr_science | i looked at 1.3.0 a little in oe-classic yesterday and it barfed on pretty much all the deps |
| 17:44.22 | mr_science | maybe the configure script was fixed in later versions? |
| 17:46.43 | *** join/#oe eFfeM (~frans@c73189.upc-c.chello.nl) |
| 17:47.12 | eren | mr_science: latest stable, 1.4.2 |
| 17:47.14 | eren | http://nginx.org/en/download.html |
| 17:47.50 | eren | and it has a little documentation on how to configure the source: http://nginx.org/en/docs/configure.html |
| 17:52.38 | mr_science | the version i used only looked in one standard place and a few oddball paths |
| 17:54.20 | mr_science | anyway, the combination of older bitbake/oe-classic was not a good match for the way nginx configure works |
| 17:54.45 | eren | I guess it needs to be re-packaged |
| 17:55.29 | mr_science | the --with-zlib=path options expect path to be the source tree |
| 17:56.36 | eren | oh |
| 17:56.43 | mr_science | you can fake it with --with-zlib=${STAGING_INCDIR) but then make wants to run configure again to force everything to build static |
| 17:57.05 | mr_science | brittle homegrown juju |
| 17:57.51 | mr_science | probably why nobody's done it yet... |
| 17:58.09 | mr_science | they think "oh that's simple" until they try it |
| 18:03.47 | eren | hm, I'm wondering how ubuntu did it |
| 18:04.23 | eren | hm. it's 1.2.6, raring release |
| 18:08.30 | eren | mr_science: there is nothing fancy on ubuntu package, btw |
| 18:11.25 | *** join/#oe martiert_ (~martin@59.37-191-128.fiber.lynet.no) |
| 18:12.58 | *** join/#oe liveforeverx (~Adium@p5B06DE81.dip0.t-ipconnect.de) |
| 18:14.20 | mr_science | both ubuntu and gentoo have their patches... for native builds |
| 18:14.23 | *** part/#oe davest (Adium@nat/intel/x-dfynalpalbvmlore) |
| 18:14.48 | mr_science | but it won't understand sysroot without some help |
| 18:19.29 | *** join/#oe flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 18:29.58 | *** join/#oe Jefro (~jefro@50-0-152-82.dedicated.static.sonic.net) |
| 18:30.30 | mr_science | eren: once i have something that builds i'll stick it on github |
| 18:31.01 | eren | mr_science: okkie |
| 18:31.54 | *** join/#oe liveforeverx (~Adium@p5B06DE81.dip0.t-ipconnect.de) |
| 18:33.30 | *** join/#oe NightMonkey (~NightrMon@pdpc/supporter/professional/nightmonkey) |
| 18:39.45 | andre_d | Hi, how can I see which package or recipe installed a certain file in my final image? (I'm interested in /etc/inittab, and in this case it's probably sysvinit-inittab, but am wondering if there is a generic way to find out?) |
| 18:41.39 | kergoth | looks into creating a systemd service for chen qi's r/o script(s) to try using those bits on a systemd image |
| 18:46.59 | *** join/#oe dijenerate (~dijenerat@65.48.221.118) |
| 18:48.56 | *** join/#oe ao2 (~ao2@2001:1418:117::1) |
| 19:09.29 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 19:12.19 | mr_science | andre_d: don't know of a way on the build side, just opkg search /path/to/file on the running system |
| 19:12.38 | mr_science | not that that question doesn't come up regularly... |
| 19:12.46 | *** join/#oe zecke_ (~ich@91-65-247-193-dynip.superkabel.de) |
| 19:23.03 | *** join/#oe KNERD (~KNERD@24.175.249.177) |
| 19:48.46 | martiert | I have just tried to figure out why oe sets load address to 00008000, while the same kernel sets load address 0x80008000 if built manually outside oe. I see the kernel links with zreladdr=00008000 inside oe |
| 19:48.51 | martiert | any ideas on where that flag is set? |
| 19:48.59 | martiert | tried git grep in oe-core, but found nothing:s |
| 19:49.52 | denix0 | martiert: <machine>.conf? |
| 19:52.00 | martiert | denix0: <machine>.conf only sets UBOOT_ENTRYPOINT and UBOOT_LOADADDRESS to 0x80008000 |
| 19:52.18 | martiert | but the u-boot-mkimage is not run, so there is no relocation going on |
| 19:57.44 | otavio | :-) |
| 19:57.46 | otavio | Hi folks |
| 19:58.02 | otavio | I had a day full of meetings, so I end missing the TSC one. I am sorry |
| 20:06.58 | mr_science | otavio: if you provide cookies, I won't tell... |
| 20:07.15 | otavio | mr_science: hehe |
| 20:13.11 | pb_ | martiert: check your run.do_compile for clues, I guess |
| 20:14.40 | martiert | pb_: I figured out the problem, but not the solution. I have appended linux-yocto_3.4 kernel, and in that append, I specify a sha sum for the git repo, as well as add a file://defconfig to the SRC_URI. The defconfig is copied over, but doesn't seem to be used |
| 20:16.43 | martiert | any idea why it's not used? |
| 20:18.24 | *** join/#oe aloril (~aloril@dsl-tkubrasgw3-54f97e-153.dhcp.inet.fi) |
| 20:19.56 | fray | otavio, we should have good notes from it.. and we expected people to be unable to join, so all feedback and comments to the oe list(s) are welcome |
| 20:20.20 | fray | (we did minutes a bit differently with this format of a meeting.. so Crofton|work was helping get them uploaded to Wiki) |
| 20:21.30 | otavio | ;-) |
| 20:21.42 | otavio | Appreciated :-) |
| 20:22.56 | mr_science | martiert: did it build the commit you specified? |
| 20:27.41 | *** join/#oe liveforeverx (~Adium@p5B06DE81.dip0.t-ipconnect.de) |
| 20:27.56 | *** join/#oe rcf (~rcf@178-117-146-93.access.telenet.be) |
| 20:34.55 | pb_ | martiert: oh, right. I think linux-yocto has some crazy special tooling, but I'm afraid I have no idea how it's meant to work. |
| 20:35.03 | pb_ | maybe ask the #yocto dudes |
| 20:35.03 | martiert | mr_science: yes, and it copies the correct defconfig file, but doesn't copy it into .config |
| 20:36.28 | martiert | pb_: ok, I'll ask them then |
| 20:40.54 | mr_science | martiert: looks like the linux-omap3.inc we're using does a "require" to pull in both those pieces |
| 20:41.13 | martiert | mr_science: from meta-ti? |
| 20:41.23 | mr_science | require recipes/linux/[setup|copy]-defconfig.inc |
| 20:41.44 | mr_science | no, this is arago/oe-classic |
| 20:42.39 | mr_science | i would hope current linux-yocto is a bit less klugey but i can't say i've looked at it yet |
| 20:43.10 | denix0 | mr_science: that's in meta-ti as well |
| 20:44.25 | martiert | mr_science: ok, do_configure in linux.bbclass does a cp ${WORKDIR}/defconfig ${B}/.config, so looks like it does what it should |
| 20:44.43 | denix0 | mr_science: although linux-omap3.inc was in classic arago only... but that was a special case |
| 20:45.10 | mr_science | martiert: is it really your defconfig in workdir? |
| 20:45.12 | denix0 | martiert: what's the problem? are you still looking for the load address? |
| 20:45.37 | martiert | denix0: yes |
| 20:46.35 | martiert | mr_science: yes, there is at least a zero diff |
| 20:46.43 | denix0 | martiert: what BSP are you using? |
| 20:47.10 | mr_science | okay, just checking... |
| 20:47.32 | martiert | denix0: I'm making one myself |
| 20:52.26 | *** join/#oe liveforeverx (~Adium@p5B06DE81.dip0.t-ipconnect.de) |
| 20:54.39 | martiert | seems like I fixed it by doing it in a do_configure_prepend, Guess I coudl also set B = "${S}" in my linux-yocto_3.4.bbappend |
| 20:55.30 | mr_science | sounds about right |
| 20:56.03 | mr_science | i had a similar "collision" replacing a package file from a bbappend |
| 20:56.19 | mr_science | not kernel-specific really... |
| 20:57.09 | martiert | except now it's complaining about an unclean directory during kernel_configcheck. Guess I'll have to look at that code next |
| 20:58.44 | bluelightning | erm, I'm not sure you should be trying to set B = ${S} |
| 20:58.51 | bluelightning | it's set separately on purpose |
| 20:59.27 | mr_science | martiert: did you put your defconfig in a machine subdir? |
| 20:59.35 | bluelightning | martiert: I'd really recommend you consult zeddii in #yocto or email the mailing list and cc him (Bruce Ashfield) |
| 21:00.14 | martiert | ok, I'll ask on #yocto then:) mr_science: Yes |
| 21:01.14 | mr_science | okay, now i'm curioous... |
| 21:04.17 | mr_science | martiert: looks like linux-rpi-3.6.11 uses the same method |
| 21:04.49 | mr_science | ie, do_configure_prepend and install their own defconfig into workdir/defconfig |
| 21:05.18 | bluelightning | that shouldn't be necessary though |
| 21:05.30 | bluelightning | it really is supposed to pick up the defconfig in SRC_URI as I understand it |
| 21:05.37 | mr_science | tell djwillis then |
| 21:05.52 | mr_science | i haven't hacked that recipe yet ;) |
| 21:06.22 | mr_science | also, the kernel_configure_variable thing looks handy |
| 21:07.31 | mr_science | martiert: maybe you could get by with setting some kernel_configure_variable options in your kernel recipe? |
| 21:08.02 | mr_science | as long as there aren't too many things you need to change... |
| 21:10.27 | mr_science | martiert: one more... does your recipe inherit both kernel and siteinfo? |
| 21:13.54 | *** join/#oe eFfeM1 (~frans@c73189.upc-c.chello.nl) |
| 21:18.44 | mr_science | before i completely dissect the apache stuff, anybody know how i enable mod_proxy? |
| 21:18.55 | *** join/#oe SoylentY_ (~SoylentYe@c-24-128-79-27.hsd1.ma.comcast.net) |
| 21:19.11 | mr_science | i don't see a separate recipe anywhere in my local trees... |
| 21:21.29 | *** join/#oe liveforeverx (~Adium@p5B06DE81.dip0.t-ipconnect.de) |
| 21:44.18 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 21:47.21 | *** join/#oe zenlinux (~sgarman@c-50-139-96-211.hsd1.or.comcast.net) |
| 21:49.07 | *** join/#oe W1N9Zr0 (~W1N9Zr0@24-246-93-30.cable.teksavvy.com) |
| 21:49.29 | mr_science | man, every time i get into something like this i wonder what i'm missing... |
| 21:50.54 | mr_science | eg, given the kernel recipe config options, seems like apache should have something similar for selecting modules and other stuff |
| 21:51.14 | mr_science | just feels like i'm always missing something... |
| 21:53.00 | *** join/#oe shawn286 (~Tiberius@unaffiliated/shawn156) |
| 21:53.24 | mr_science | feel free to whack me with the clue-stick at any time... |
| 22:00.14 | bluelightning | hmm, I'm not sure how apache extra modules are enabled |
| 22:00.40 | bluelightning | (and that's a bit sad because it was me who worked on that recipe) |
| 22:01.25 | bencoh | :] |
| 22:01.39 | bencoh | guess we should dissect your brain then |
| 22:03.57 | bluelightning | hey, I need that brain :) |
| 22:04.00 | mr_science | yup, looking at some recipes and the apache configure output |
| 22:04.29 | mr_science | looks like i definitely need to enable some things we need |
| 22:05.37 | mr_science | then there's tuning the whole mpm config for 600 MB of ram... |
| 22:05.54 | mr_science | maybe i should go back and look at nginx again... |
| 22:07.12 | bluelightning | apache is kind of heavy for a lot of embedded type applications for sure |
| 22:08.19 | bencoh | nginx definitely fits better for most embedded plateforms :) |
| 22:08.56 | bluelightning | we don't yet have an nginx recipe as discussed earlier, but for simpler configurations we have a number of alternative smaller web servers in meta-webserver |
| 22:09.11 | bluelightning | e.g. hiawatha and cherokee |
| 22:09.47 | *** join/#oe ant_home (~andrea@host218-250-dynamic.17-79-r.retail.telecomitalia.it) |
| 22:10.11 | mr_science | currently running lighttpd but one of the devs apparently needs reverse proxy support |
| 22:10.14 | bencoh | mr_science: btw, I'm currently building/using nginx, if you want a recipe |
| 22:10.28 | bencoh | (it relies on the cross patch) |
| 22:11.00 | mr_science | bencoh: pointer? |
| 22:11.40 | mr_science | i have a (currently nonfunctional) recipe i lifted from rascal, but it needs some luv to make it work |
| 22:12.13 | bencoh | I'm using a different one (with a different patch), currently building and working on both x86 and arm |
| 22:12.22 | bencoh | (others should work too) |
| 22:12.42 | bencoh | based on http://forum.nginx.org/read.php?29,179478 |
| 22:12.42 | mr_science | are those publicly visible somewhere? |
| 22:13.11 | bencoh | lemme pastebin that ... it's not public for the time being, but nothing really secret (just a private repo) |
| 22:14.03 | mr_science | looks like the op disabled the problematic parts of configure... |
| 22:14.16 | bencoh | mr_science: http://pastebin.notk.org/pastebin.php?show=d386380f4 http://pastebin.notk.org/pastebin.php?show=d16cfcf79 |
| 22:14.33 | mr_science | --without-pcre --without-http_gzip_module ... |
| 22:14.46 | mr_science | jeez, *i* could've done that... |
| 22:14.56 | bencoh | I'm building mine with pcre |
| 22:15.07 | bencoh | (and gzip) |
| 22:15.08 | mr_science | good |
| 22:15.48 | bencoh | the important part of the ml mail is the patch |
| 22:16.13 | mr_science | looks amazing close to what was in my head... |
| 22:16.21 | mr_science | *amazingly even |
| 22:16.44 | bencoh | :) |
| 22:17.26 | bencoh | what's really amazing (sic) is that this thing is more than 2 years old ... and vanilly nginx is still not cross-friendly |
| 22:21.51 | mr_science | i noticed, and had the same "amazing" thoughts in my head... |
| 22:22.07 | mr_science | so stop putting them there! |
| 22:22.17 | mr_science | dons his foil hat |
| 22:22.43 | bencoh | :)) |
| 22:25.41 | mr_science | is that really for 1.0.11 ? |
| 22:26.12 | mr_science | did you avoid the newer stuff on purpose? |
| 22:26.50 | bencoh | I first wrote this recipe 1.5years old and didn't have time to test it against newer versions |
| 22:27.00 | bencoh | s/old/ago/ |
| 22:27.07 | mr_science | ah |
| 22:27.18 | mr_science | i started making a 1.3.0 last night |
| 22:27.44 | mr_science | also noticing 1.3.11 is the latest in portage on my laptop |
| 22:27.46 | bencoh | wow, 1.0.11 really was latest-stable at that time :)) |
| 22:28.23 | bencoh | I guess I should give 1.4.2 a try, some day |
| 22:28.44 | mr_science | so maybe i'll just migrate everything to 1.4 then |
| 22:29.00 | mr_science | notice any hard deps in the new stuff? |
| 22:29.34 | bencoh | haven't checked yet |
| 22:30.03 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 22:31.23 | mr_science | from what i saw last night it's pretty much pcre and few more-or-less "normal" things |
| 22:31.43 | mr_science | so i guess we'll see... |
| 22:34.36 | *** join/#oe jkridner|work (~jkridner@nat/ti/x-djissblsvblyvvxy) |
| 22:39.16 | mr_science | i can't believe i just did that... |
| 22:40.29 | bencoh | did you take care of the different data types ? |
| 22:40.42 | mr_science | after look at the local config stuff in the nginx and apache2 source trees, i just went back to lighttpd and went "oh nice, autotools for a change..." |
| 22:40.50 | bencoh | :D |
| 22:41.28 | bencoh | from what I've seen (quite a few years of porting/crossbuilding), autotools still is one of the most friendly ... which is ... scary :) |
| 22:41.41 | mr_science | yeah... |
| 22:42.04 | mr_science | i can't remember ever saying that about autotools before |
| 23:07.19 | *** join/#oe dos11 (~dos@unaffiliated/dos1) |
| 23:29.45 | *** join/#oe mwester (~mwester@nslu2-linux/mwester) |
| 23:51.16 | *** join/#oe shawn286 (~Tiberius@unaffiliated/shawn156) |
| 23:55.45 | *** join/#oe Jefro (~jefro@50-0-152-82.dedicated.static.sonic.net) |