IRC Logs for #crux-devel Tuesday, 2012-11-27

*** Roomster has quit IRC00:35
*** jue has quit IRC02:27
*** jue has joined #crux-devel02:30
*** Romster has joined #crux-devel03:13
*** Romster has quit IRC04:12
*** Romster has joined #crux-devel04:13
*** Romster has quit IRC04:21
*** Roomster has joined #crux-devel04:21
*** Roomster has quit IRC04:24
*** Roomster has joined #crux-devel04:25
*** Roomster is now known as Romster04:59
*** Romster has quit IRC07:07
*** Romster has joined #crux-devel07:13
*** Romster has joined #crux-devel07:13
*** Romster has quit IRC08:56
juejaeger: looks good to me, I'd suggest to bump the version after FS#60310:08
jaegerok10:10
juejaeger: is there something left we have to do before you can start building a first iso?10:24
horrorStruckthere may be some few patches to add to glibc10:30
juehorrorStruck: which ones?10:34
horrorStruckjue: http://sourceware.org/bugzilla/show_bug.cgi?id=1462110:34
horrorStruckhttp://sourceware.org/git/?p=glibc.git;a=commit;h=6c62f10810:35
horrorStruckand --without-gd and --with-lts could be removed10:36
jueI saw that commit but don't think it's really relevant in practice10:37
juebut, yes, the configure clean-up is nice10:38
horrorStruckjue: yeah right, it looks like it could only be triggered in very special cases10:40
juehorrorStruck: btw, I thought that they have fixed eudev because I had locally added introspection.m4 into eudev/m4 and forgot that ;)10:42
horrorStruckhehe i was *really* wondering wtf was happening with my machine :P10:45
jueshame on me :)10:48
horrorStruckdifficult with my skills to criticize but eudev development seems a bit amateurish10:50
jueyeah, my thoughts as well10:50
horrorStruckbbs, 10 minutes left to buy a 6 pack :O10:51
horrorStruck$name-segfault_in_strncasecmp.patch could be dropped too, it's i686 only11:23
horrorStruckwell, not from glibc-3211:23
horrorStruckoh and most important thing ever, remove the -n option from line 53 of rc.shutdown :P11:25
horrorStrucklfs uses umount -a -d -r -t notmpfs,nosysfs,nodevtmpfs,noproc11:37
*** mike_k has joined #crux-devel13:15
*** mike_k has quit IRC15:11
*** Roomster has joined #crux-devel15:42
*** Roomster has quit IRC18:18
*** Roomster has joined #crux-devel18:20
*** horrorStruck has quit IRC19:21
*** horrorStruck has joined #crux-devel19:22
jaegerwhat would be the reasoning for removing --without-gd from glibc's Pkgfile?19:29
jaegerit's still valid as far as I can tell19:29
*** jue_ has joined #crux-devel19:30
*** jue has quit IRC19:30
*** jue_ is now known as jue19:30
*** Romster has joined #crux-devel19:31
*** jue has quit IRC19:36
jaegerand regarding --with-lts I'm guessing you meant --with-tls?19:37
*** jue has joined #crux-devel19:38
horrorStruckjaeger: yes :)19:39
horrorStruck--without-gd is still valid but i guess we used it as per LFS instructions i.e. to prevent memusagestat to be built? because memusagestat is not being built anyway19:43
jaegerIs that the only thing it does? Because someone could easily build with gd support later without knowing they've done so, I guess19:44
Romstermuch like gcc could be rebuit with elfutils for LTO support19:45
Romsterbeen meaning to ask fi gcc can have LTO and elfutils put in core19:46
horrorStrucktalking about gcc, --with-x options is for java only, we could drop that19:47
horrorStruckRomster: i dont think elfutils are required anymore for LTO19:55
horrorStruckjaeger: i have to go to work but i'll dig into the --without-gd option, my guess is that it's doing not much :)19:56
jaegerI've heard mixed reviews of LTO, doesn't sound like it's a great idea19:59
Romsterworked on the majority of ports and those that it did break compile you just omit the LTO off the flags to build without it20:02
Romsteranyways back to work later.20:02
*** Romster has quit IRC20:06
*** Roomster has quit IRC21:36
*** __mavrick61 has quit IRC21:36
*** Roomster has joined #crux-devel21:36
*** ___mavrick61 has joined #crux-devel21:37
*** clb has joined #crux-devel23:29

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!