/srv/irclogs.ubuntu.com/2006/10/31/#ubuntu-toolchain.txt

fabbionemorning guys05:20
fabbionebuildd@sunfire:~/build$ sbuild -d feisty --comp=main gcc-4.1_4.1.1-18ubuntu105:27
fabbione*** glibc detected *** ./pthread5.exe: corrupted double-linked list: 0x71700490 ***05:27
fabbionedoko ^^^otherwise it builds fine05:27
dokofabbione: you did not run the testsuite in parallel, did you?09:23
fabbionedoko: i just builded the package as you did it.. 09:24
fabbionedpkg-build...09:24
fabbioneso if it's set to run in parallel then yes09:24
fabbioneld.so.1 (pid 7864): Privileged operation (code 10) at 401bc127   09:25
fabbioneld.so.1 (pid 9413): Protection id trap (code 7) at 400016a3                     09:25
fabbioneld.so.1(9618): unaligned access to 0x00010ae6 at ip=0x4010ce0b                  09:25
fabbioneld.so.1(10034): unaligned access to 0x00013736 at ip=0x4010b6ff                 09:25
fabbioneld.so.1(10718): unaligned access to 0x00010b06 at ip=0x4010ce0b                 09:25
fabbioneMEH09:26
fabbionethis can't be good09:26
dokowhich package?09:37
fabbioneglibc-2.5 (hppa)09:38
fabbioneanyway.. let's talk about sparc and 128 bits09:38
fabbionei just finished the second build of glibc-2.5 with newer gcc09:39
fabbionels still works :)09:39
fabbionei am going to open the gates once i have the chroots ready09:39
fabbionegates are open09:54
fabbionelibc6_2.5-0ubuntu1_hppa.deb10:33
fabbionewhooopa10:33
fabbioneok we are getting tons of non fatal unalligned access with 2.510:36
=== ..[topic/#ubuntu-toolchain:fabbione] : STATUS: gcc: sparc (under testing) | hppa: bootstrapping needed (test in progress)
fabbionewe have the fix for ppc kernel10:44
=== Keybuk [n=scott@quest.netsplit.com] has joined #ubuntu-toolchain
cjwatsonargh, Ben's udeb changes are crack11:06
fabbionecjwatson: i told him.. he was going to talk to you at UDS11:08
cjwatsonI've mailed him11:10
cjwatsonI don't care about the storage stuff, but the filesystem changes will break things11:10
cjwatsonnewed, anyway11:11
fabbionenah pointless again :)11:11
fabbioneit's still broken on ppc and sparc11:11
fabbioneit seems that the changes got lost somehow11:11
cjwatsonperhaps pointless, but harmless. :)11:12
cjwatsonand I don't like excess stuff stuck in new11:12
=== jerom2 [n=jeromeb@LSt-Amand-152-32-6-178.w82-127.abo.wanadoo.fr] has joined #ubuntu-toolchain
=== jerom2 [n=jeromeb@LSt-Amand-152-32-6-178.w82-127.abo.wanadoo.fr] has left #ubuntu-toolchain []
=== jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-toolchain
jbaileydoko: Around?02:46
dokojbailey, fabbione, cjwatson, lamont: ping02:46
dokojbailey: yes :)02:46
fabbionedoko: pongish02:46
jbailey=)02:46
fabbionei need 2 minutes break.. absolutely.. brb02:46
cjwatsondoko: yes?02:49
dokoabout the ABI change on powerpc and sparc: long double changing from 64bit to 128bit02:49
dokoglibc and libstdc++ are the only libs having both support for 64 and 128 long doubles02:50
dokohow should we handle other libraries using long double datatypes in their interfaces?02:51
doko- rename the library packages02:51
fabbionere02:51
doko- do nothing (minor ABI breakagae on some archs), and rebuild the archive02:52
fabbionedoko: do you have a list of packages affected?02:52
dokohttp://people.ubuntu.com/~doko/ldbl/  (these are all packages with a long[ _] *double string in their header files02:53
fabbioneeh02:53
cjwatsonI don't see that in http://gcc.gnu.org/gcc-4.2/changes.html02:54
cjwatsonis this an undocumented ABI change or something?02:54
cjwatsonoww, that's a lot of packages in main02:54
fabbionehold on.. those are headers.. what about stuff that B-D on those headers?02:55
dokofabbione: right, that's the next step ...02:55
jbaileydoko: I'm confused.  The ldbl change is supposed to be ABI-neutral, no rebuild needed.02:55
jbaileydoko: I thought we'd shown that the old symbols got provided?02:56
dokocjwatson: 4.2 is not yet released; these are backports from the fc 4.1 branch02:56
cjwatsonif it's supposed to be ABI-neutral, and isn't, then that seems like a bug, and can we unbackport those changes? :P02:57
dokojbailey: yes for libc and libstdc++; but what about rebuilding a library libfoo and packages depinding on that library?02:57
dokodepending even02:58
jbaileycjwatson: It's usually better to suck it up and follow upstream to be safe.02:58
fabbionethis is going to be another clusterfuck.. i feel  it02:58
jbaileydoko: Yeah, dunno.  I haven't followed all the header magic in that.  I don't know if there was some sort of compat macros or whatever that twiddled it transparently.02:59
cjwatsonjbailey: if renaming lots of libraries is involved, I'd rather have some time to consider that rather than being forced to do it immediately03:00
cjwatsonjbailey: especially if it might be a bug that gets fixed so we have to unrename everything later!03:00
dokojbailey: what does header magic solve for libraries which don't support both?03:01
fabbionecjwatson: it really depends on how soon you want to open feisty03:01
fabbioneif there is really an ABI breakage we better deal with it before03:01
fabbionerather than later and collecting pieces with tons of uploads03:01
cjwatsonisn't this a specs file thing?03:01
cjwatson-mlong-double-12803:01
cjwatsonfabbione: I would like to have it open before UDS03:01
fabbionecjwatson: toolchain is not ready yet.. it's likely we can make it for UDS, but for example ppc is now stalling on elmo to install a new kernel on buildd and he is not around today.03:02
jbaileydoko: Magic headers in the type definition, is what I'm thinking.03:02
dokosee http://gcc.gnu.org/PR25864 for the detauls03:02
dokocan't type anymore03:03
fabbionedoko: could you before ? ;)03:03
cjwatsonhow practical is it likely to be to provide _Q_ functions in other affected libraries?03:05
cjwatsonI'm not happy with a flag-day renaming of a bunch of libraries in main and all the upgrade pain that entails for the sake of two architectures, really03:05
cjwatson_Q_> or whatever the compatibility symbols are called03:06
fabbionecjwatson: what scares me is that we might trip in runtime errors during upgrades if we change ABI without renaming packages03:06
fabbioneor een using upgrader itself that's written in python and python is one of those affected pkgs03:07
cjwatsonif it's possible to provide compatibility symbols for both ABIs, that would solve that problem03:07
dokofabbione: there are not many extensions actually using long double03:07
fabbionecjwatson: right.. assuming we can03:08
cjwatsonif it's doable in libc ...03:08
fabbionedoko: can you write me a test case that will trip in that problem?03:09
dokocjwatson: what would that solve? having a "long double foo (long double)" function in libfoo, we would need to have these symbols in libfoo03:09
cjwatsonEPARSE03:12
fabbioneand i guess massive patching is not an option for the sake of 2 arches03:12
cjwatsonlibrary renaming that Debian isn't going to do for ages yet (given the etch freeze) counts as "massive patching"03:13
cjwatsonI'd actually be happier with a bunch of library patches ...03:13
=== mdz [n=mdz@studiocity-motorola-bsr1-70-36-194-85.vnnyca.adelphia.net] has joined #ubuntu-toolchain
fabbionecjwatson: hmmm massive code patching is more dangerous IMHO03:14
fabbionehi mdz03:14
mdzmorning03:14
=== ..[topic/#ubuntu-toolchain:fabbione] : STATUS: gcc: sparc (under testing) | hppa: bootstrapping needed (test in progress) | ppc needs fixed kernel on buildd (elmo informed)
cjwatsondoko: glibc clearly has code that uses the old-style long double type somehow03:15
dokocjwatson: "some arches" = sparc, sparc64, powerpc, powerpc64, s390, s390x, alpha03:15
jbaileycjwatson: glibc handles it by not actually using the real function names.03:16
cjwatsondoko: i.e. powerpc and sparc from our point of view03:16
jbaileycjwatson: When you call open, it gets mapped to _open@GLIBC_2.403:16
fabbionedoko: for us is still sparc and ppc only03:16
dokocjwatson: no, it provides functions handling both the old and new data types03:16
cjwatsondoko: yes, that's what I said03:16
jbaileycjwatson: They change symbol version for the new ABI.03:16
cjwatsonjbailey: right, I know that, but the new glibc still builds the old _open@GLIBC_2.4 code with the current gcc03:17
jbaileyRight.  I'm guessing that they still have a compat type sitting around that they use.  I don't know off hand.03:17
cjwatsonyep, and if that compatibility type can be / is exported, it would not be that hard to make other libraries support both old and new ABIs03:18
fabbioneok.. is there any way i can have a test case?03:18
fabbionedoko: ^^03:18
fabbionei have almost done rebuild edgy on top of feisty toolchain on sparc03:18
fabbioneand i can test03:18
fabbionebut i want test cases03:18
fabbionethat should tell us if we need to do something fancy or not03:18
cjwatsonalso assuming that it's possible to call the GLIBC_2.4 code directly03:18
cjwatson(or do exceedingly cunning linker tricks to make that happen automatically for some objects)03:19
fabbioneROFL03:19
cjwatsonfabbione: one of my concerns is that we have no established mechanism for ABI changes in perl and python03:19
infinitySpeaking of ABI changes...03:20
cjwatsonfabbione: I don't particularly want to establish one in a hurry (or at all, if we can get away with it)03:20
fabbionecjwatson: that's why i need a test case :)03:20
fabbionecjwatson:  i can test with old and new stuff03:20
infinityjbailey: Is glibc/hppa still going to give us a broken ABI, and should I whip up a clever script to find every package that's not changed since dapper, so I can make sure they get rebuilt? :)03:20
fabbioneinfinity: hppa will be rebuilt in full.. no matter :)03:20
fabbioneinfinity: we lost an entire release03:21
infinityfabbione: Yes, hence the "find things that haven't changed since dapper".03:21
infinityfabbione: We still ship packages that haven't changed since warty, you know.03:21
fabbionei don't think there is something left :)03:21
fabbioneinfinity: probably because nobody uses them ...03:21
infinitySome just don't need updates. :)03:21
fabbioneexactly :)03:21
cjwatson$ ./suite-diff.py ubuntu/dists/warty/main/binary-i386/Packages.gz ubuntu/dists/edgy/main/binary-i386/Packages.gz eq | wc -l03:21
cjwatson2803:22
infinityI maintain one that hasn't changed since dapper. *shrug*03:22
cjwatson$ ./suite-diff.py ubuntu/dists/warty/universe/binary-i386/Packages.gz ubuntu/dists/edgy/universe/binary-i386/Packages.gz eq | wc -l03:22
cjwatson80603:22
infinitycjwatson: I see I'm not the first person to want this statistic. :)03:22
infinityAnyohw, 28/806 is very workable.  Cool.03:22
jbaileyinfinity: Totally changed thread ABI.03:23
cjwatsonI use suite-diff more for ge, gt, le, lt comparisons, but eq is occasionally handy and was trivial to implement03:23
infinityAnd main's all I care about initially anyway.03:23
cjwatsoninfinity: one sec and I'll give you dapper->edgy figures03:23
infinityjbailey: Right, so after bootstrapping the toolchain, I'll want to rebuild everything in {Build-,}Essential, and then move up the chain.  Fun.03:24
infinitycjwatson: Oh, that was warty.  I wasn't paying attention.03:24
jbaileyinfinity: It's an interesting experiment to see how ugly a bootstrap is these days.03:24
cjwatsoninfinity: counting by source package:03:24
cjwatsonmain: 47803:24
cjwatsonrestricted: 103:24
cjwatsonuniverse: 388503:24
cjwatsonmultiverse: 25803:24
infinityjbailey: Shouldn't be too bad, and for all that I complain about them, the hppa buildds are still pretty quick.03:24
cjwatsonfeel free to go "dear god" now03:25
infinitycjwatson: Those figures sound more correct anyway. :)03:25
infinityedgy's short cycle didn't help there.03:25
infinityWe might get those numbers down just with the initial round of merge/sync madness.03:26
infinityBut, whatever.  Worst case, I just do a mess of rebuild uploads.  Serves a dual purpose of fixing hppa, and getting the rest of the arches built against a modern toolchain.03:27
infinityhppa's simple, just time-consuming.03:27
infinityThis long double thing sounds far more icky.03:27
fabbioneinfinity: hppa is a pain at the moment.. second round of glibc build will fail but we have our super-Jeff on it03:27
infinityOh, it's not self-hosting yet?  Fun.03:28
fabbioneinfinity: and you really want to take the debs i did build to get to gcc B-D03:28
fabbioneinfinity: yes.. it's a header issue that shows up only at the second rebuild03:28
infinityfabbione: Yeah, I'll use your bootstrap stuff, thanks.  It'll be several rebuilds before I get to the final archive debs anyway, so I don't mind the taint.03:28
fabbioneinfinity: i know, they are just useful.. it's building gcc for feisty now.. that will come handy too03:29
=== infinity hopes no one quotes him out of context as saying "I don't mind the taint".
fabbionedoko: ok.. so what is your suggestion on how to handle this ABI breakage+03:29
fabbione?03:29
infinityI suspect I won't fully open hppa until I get back from UDS and have my 6750 powered on anyway.03:29
infinityBut the primary arches should, ideally, be opened in the next two or three days, if we can at all manage.03:30
fabbioneinfinity: or we can play with it together.. i have console on mine03:30
fabbioneand your has also remote power capabilities.. that's even better03:30
fabbioneok should we do a summary before my wife will kill me?03:30
infinityfabbione: Well, I'll have a console on mine as soon as I've visited a Frys in SF and bought a USB->Serial dongle. :)03:30
fabbione(i was supposed to be out of the office 2 hours ago)03:30
fabbionei think i386/amd64 are fine.. at least so it seems03:31
infinityfabbione: And yeah, the DC ones have remote power that I can mangle from anywhere, which is rather handy in light of the hppa kernel's... Oddities.03:31
fabbioneinfinity: i am not running .19 kernel.. only dapper kernels03:31
fabbioneppc needs a new kernel. the patch is in pitti/elmo hands03:31
dokofabbione: last time we had an arch specific ABI change on sparc in unstable, we didn't do anything03:31
fabbionesparc/ppc have the ABI issue03:32
fabbioneia64 looks good03:32
fabbionehppa whatever...03:32
cjwatsondoko: powerpc is first-class and released; IIRC last time sparc wasn't03:32
fabbionesparc is released now and first-class on enterprise servers03:32
infinitydoko: Is this the sort of ABI breakage that will royally mess up upgrades (ie: postinst scripts dying and the like)?  If so, "just ignoring it" isn't going to cut it.03:32
=== fabbione hides a bit
cjwatsonif it stands a decent chance of not breaking during upgrades (and that sounds plausible; do upgrades really require serious floating-point code?), then ignoring it is an option I'd certainly consider03:33
infinityYeah, that's the point I was driving at.03:33
infinityUnlike Debian, we don't really pretend to support partial upgrades.03:33
fabbionecjwatson: i can test scenario too03:33
cjwatsonthought I'd emphasise it the other way round. :-)03:33
infinitySo, I'm cool with "once your upgrade has settled, you'll be okay"... If the upgrade can go smoothly.03:34
fabbionebut i need a couple of more days to get there03:34
fabbioneotherwise somebody needs to ship me another T2000 and i could run 64 buildd03:34
cjwatsoninfinity: and if we can figure out how to do compatibility code for this, we could do that just for libraries that break during upgrade, if any03:34
infinityfabbione: You have enough toys.. Share with the class. :P03:34
fabbioneinfinity: ehhe03:34
infinitycjwatson: Fair point.03:35
fabbionecjwatson: that's even scarier.. 03:35
fabbionebut well whatever03:35
fabbioneinfinity: can you get Ben to upload a working kernel today?03:36
dokoright, that was my thinking. there shouldn't be too much code (if any) which needs floating point arithmetics in installation/removal03:36
cjwatsonfabbione: surely it's less scary03:36
infinityfabbione: I tried that yesterday. :)03:36
cjwatsongiven that it involves less work and less code03:36
infinity(But yes, I'll try again)03:36
fabbioneinfinity: try harder? ;)03:36
fabbionejbailey: is binutils ok for you to upload or does it need more?03:36
fabbionedoko: did you review binutils?03:36
dokofabbione: yes, looks fine to me03:37
dokojbailey: ^^^03:37
fabbionei know we lack a patch for hppa that miscompile the kernel, but we CAN live with an unbootable hppa kerenl for bootstrapping03:37
jbaileyfabbione: I'm happy with it from ppc/ppc64/hppa tests.  I haven't looked at i386/amd64.  Given that it's HJ, I suspect those and ia64 are pretty guaranteed.03:37
jbaileyfabbione: Yes, that's fine.03:37
fabbionejbailey: ok.03:37
infinityUnbottable hppa kernels don't matter to me right now.03:37
fabbioneinfinity: neither for me03:37
fabbionejbailey: what about glibc debian/patches?03:37
infinityIf you guys are happy with binutils, toss it in the queue SVP.03:38
fabbioneshould we go with what we have and review later?03:38
jbaileyfabbione: I want to commit what I've got in there.  The Debian patches cause one of the tests to segfault.03:38
fabbionejbailey: ok.03:38
jbailey(yay debian)03:38
fabbionejbailey, doko: i am going to upload binutils then.03:38
fabbionei did check the testsuite with .17 and .19 hreaders03:38
fabbionethere is no difference03:38
fabbioneso it doesn't matter to wait for the new kernel03:38
jbaileyCool.  I'm happy to see binutils go in.03:39
jbaileyfabbione: You're putting in the same one that I put into bzr?03:39
infinityAnd binutils passes its testsuite with no regressions regardless of whether it's built against edgy or feisty?03:39
fabbionejbailey: yes and the same orig03:39
infinity(ie: Can I build it now, now, now?)03:39
fabbioneinfinity: yes it can build now now03:39
infinity\o/03:40
jbaileyfabbione: Do you know any timeframe for the kernel patch going in for ppc?03:40
infinityjbailey: Being applied on the buildds, you mean?03:40
fabbionejbailey: i guess tomorrow... elmo is not around today03:40
fabbioneinfinity: yes03:40
jbaileyfabbione: I have Angie's ultrasound midday today, but I'd like to beat on this when I'm back to get that patches directory in shape.03:40
infinityI can get Znarl to do it.03:40
jbaileyLovely, so there's no pressure for today for glibc going in.03:40
infinityOh, unless you want the breathing room.03:40
infinityThen I'll, uhm, not get Znarl to do it.03:40
fabbioneinfinity: i have the patch and i can send it to Znarl, but we still need to jump to edgy .1703:41
fabbioneinfinity:  i didn't test the patch on dapper yet03:41
infinityShould apply to .15 without terrible issues, I'd suspect.03:41
infinityOn the other hand, we wanted the PPC buildds upgraded to edgy kernel source for other reasons.03:42
fabbioneyes it might apply but it's not tested and you don't want to DoS the buildd.. do you?03:42
infinitySome sketchy build failures that were kernel-releated.03:42
infinityrelated, too.03:42
fabbioneinfinity: well elmo will have to speed that up a lot03:44
infinityI've got a laundry list of things to talk to elmo about, so I'll make sure this gets done.03:44
infinity(Still have some sketchiness on jackass to deal with, which takes priority, but only barely)03:44
fabbioneinfinity: he has the patch in an email03:45
infinityI know, you CC'd me, remember? :)03:45
fabbioneinfinity: i did? ok03:45
infinityOh, looks like the buildds went to edgy kernels when I wasn't looking anyway.03:46
fabbioneno i didn't03:46
infinityThat makes life easier.03:46
fabbionebinutils on the way03:46
fabbionejbailey: does bzr support tagging?03:46
fabbioneno it doesn't03:46
jbaileyfabbione: I remember there was a spec for it, dunno where that got to.03:46
fabbionejbailey: ok...03:46
infinityfabbione: "local DoS fix for ppc", sent to elmo, CCd to pitti and I.03:46
jbaileyj-a-meinal will be on in an hour or so usually, we can ask him.03:46
fabbioneinfinity: BenC is around!03:46
infinityfabbione: Your memory's failing in your old age. :)03:46
jbaileyinfinity: Why not the RT queue so that one of the other sysadmins can deal with it?03:47
fabbioneinfinity: screw you old boy! :P03:47
fabbionejbailey: because they don't do kernel stuff.. i did ask on -sysadmin03:47
infinityZnarl does kernels occasionally.03:47
fabbioneinfinity: up to you.. without that kernel ppc boxes will die like KITTIES if we upload glibc :)03:48
fabbioneinfinity: binutils uploaded03:48
infinityDoes it cause the build to fail, or just cause the machine to Zombie half to death?03:49
infinityCause I *do* have remote power on them. :)03:49
fabbionemachine will die03:49
infinityRight, not pleasant.  Will wait.03:49
fabbioneand the build won't finish03:49
fabbioneit's pointless03:49
jbaileyinfinity: reboot -f works, too. =)03:50
jbaileyfabbione: I never reproduced machine death.03:50
fabbionejbailey: i did03:50
jbaileyJust the Hallowe'en drama of things running around yelling "GRAAAAIIIIINNNNSSSS...."03:50
fabbioneThis upload awaits approval by a distro manager03:51
fabbioneinfinity: ^03:51
infinityfabbione: Yes dear. :)03:51
fabbioneslacker! do you want to accept the upload?03:51
fabbionei got this email more than 60 secs ago! :P03:51
infinityI'm on it, I'm on it.03:51
infinityPunk.03:51
fabbioneyou are getting slow.. must be the age03:51
fabbioneMUHHAHAHA03:51
infinityNo, it's the latency.03:51
=== fabbione claims revenge
fabbioneyeah between fingers and eyes03:52
jbaileyfabbione: Bah..  When *I* was young...03:52
infinityTakes 12 minutes to do an SSH handshake between .au and the DC.03:52
jbaileyinfinity: Throw *out* the m68k, dude. =)03:52
fabbionejbailey: speaking of which.. congratulation.. your bday was yesterday?03:52
jbaileyfabbione: Yeah, thanks.03:52
infinityjbailey: *grin*03:52
fabbionethere.. i guess we are all set.. more or less03:53
infinityGetting there.03:53
fabbioneinfinity: yeah...03:53
fabbionejbailey: ok.. i will be back later this evening...03:54
fabbionejbailey: so we can look again at glibc03:54
fabbionedoko: are you ready to upload gcc?03:54
jbaileyfabbione: 'kay.  I'll try to run the glibc stuff today over the day, but will focus on it tongiht.03:54
jbaileyI'll also get some more hppa love going.03:54
jbaileyI've just sent a final "we're doing this, any questions?" email to the parisc list.03:54
fabbionejbailey: ok. your tonight is my deep night... should i shift working hours?03:54
jbaileyNope, there's not much to share except scrolling consoles.03:55
fabbionei don't mind it at all.. i just need to know so that we can work closer03:55
fabbioneok03:55
fabbionewe can still share the orgasms on each line text03:55
jbaileyfabbione: More useful to have you work when I'm asleep for a final test with goal of upload tomorrow.03:55
fabbionejbailey: ok perfect works for me03:55
fabbioneby tomorrow i should have enough sparc debs to do some kind of tests03:55
fabbioneok dok03:56
fabbioneoky doky03:56
fabbionei am off03:56
infinityfabbione: Did you forward that ppc fix to BenC too, for inclusion in edgy-updates?03:56
fabbioneinfinity: i think i did?03:56
fabbioneinfinity: wasn't he in the email?03:56
infinityNot in the same email you sent me.03:56
jbaileyfabbione: I'd imagine benh will submit it for the . release, won't he?03:56
fabbioneinfinity: ok. i will talk to him once benh gives me the greenlight for stable release03:57
fabbionejbailey: yes i am sure he will03:57
infinityKay.03:57
fabbioneinfinity: there are 2 solutions to that problem.. really03:57
fabbioneone is the patch03:57
fabbioneand one is to disable a couple of syscalls in the kernel03:57
dokofabbione: davis:~doko/gcc/4.1/tst/03:57
fabbionedoko: what's that?03:58
fabbionedoko: ok thanks.03:58
fabbionelater guys04:00
=== fabbione takes off
fabbioneinfinity: and yes.. even pigs can fly given enough thrust04:00
infinityIt's not nice to talk about my mother that way.04:01
jbaileyAnd with the image of FAbio thrusting a pig...  Off to the office I go.04:01
fabbioneinfinity: i miss the association with your mother... if it's there for some reasons it was REALLY not meant04:02
=== jbailey [n=jbailey@montreal.canonical.com] has joined #ubuntu-toolchain
fabbionedoko: i did build that test case on edgy and it segfaults10:06
fabbionedoko: should i try on feisty and it should work.. right?10:06
fabbioneor the other way around?10:06
fabbionedoko: it segfaults also when built with feisty toolchain10:10
=== rodarvus [n=rodarvus@ubuntu/member/rodarvus] has joined #ubuntu-toolchain
=== anibal_ [n=anibal@debian/developer/anibal] has joined #ubuntu-toolchain
=== doko_ [n=doko@dslb-088-073-093-229.pools.arcor-ip.net] has joined #ubuntu-toolchain
=== jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-toolchain
jbaileydoko: There are libgcc-compat patches in here to expose some extra symbols.  I wonder if they actually matter to anyone.11:57
jbaileyThey're old versions, so nothing new will build with them.11:57
dokojbailey: disconnected, maybe I did miss something?12:00
jbaileydoko: No, sorry.  I started mid-thought.12:02
jbaileyI'm reviewing all of the glibc patches again.12:02
jbaileyglibc for awhile leaked some libgcc symbols directly.12:02
jbaileyWhen Jakub fixed up glibc to not leak stray things, he removed these, but we brought them back.12:03
jbaileySadly, there's no explanation *why* we did this, and I was wondering if we should maybe not do so.12:03
jbaileyNot important for right now, but probably something to look at for feisty+112:03
jbaileyBut it might be nice to start stripping out some of these patches.12:04
dokook12:05
dokojbailey: I'm not opposed to a feisty+1 toolchain roadmap, but I think we can do better than the edgy+1 roadmap; we should discuss this next week.12:06
jbaileyI don't think we booked a bof for it. =)12:07

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