=== warthylog [~warthylog@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-toolchain === Topic for #ubuntu-toolchain: GNU Compiler Collection, Glibc, Binutils, Linux-kernel-headers | GLIBC Todo: hppa, sparc NPTL, i386 biarch === Topic (#ubuntu-toolchain): set by jbailey at Wed May 11 01:20:59 2005 === #ubuntu-toolchain [freenode-info] please register your nickname...don't forget to auto-identify! http://freenode.net/faq.shtml#nicksetup [07:50] (fabbione/#ubuntu-toolchain) 1 2 3.. test! [07:50] ok logs to appear on the web within the next hour [07:51] fabbione: Thanks Fabio! === svenl [~luther@AStrasbourg-251-1-60-207.w82-126.abo.wanadoo.fr] has joined #ubuntu-toolchain [07:51] hi all. [07:52] now.. you got the logs... FIX SPARC YOU WANKERS! [07:52] gcc-3.4 is FTBFS [07:52] l-k-h is teh SUX! [07:52] Is that "fix" like how I had my cat "fixed"? [07:52] i have no idea about your cat.... [07:53] fabbione: In N. America (possibly all of english) to have an animal "fixed" is to have it neutered. [07:53] no seriously.. if we start the transtion before sparc has even a toolchain i might as well consider dropping the port [07:53] oh... poor cat [07:54] why does gcc-4.0 depend on libcairo-dev ? [07:54] anyway i must run to cook dinner [07:54] cya tomorrow === seb128 [~seb128@ANancy-151-1-30-146.w83-196.abo.wanadoo.fr] has joined #ubuntu-toolchain === ogra [~ogra@p5089FB28.dip.t-dialin.net] has joined #ubuntu-toolchain [08:07] weren't we supposed to start 7 minutes ago? ;-) [08:07] 6 here [08:07] poke doko [08:08] svenl: libgcj [08:08] doko: oh. [08:09] svenl: you can drop it, it's not a hard dependency [08:09] bah, i just installed it. [08:11] so doko, why have you called us all here? [08:11] fabbione: you could just change gcc-defaults to have g77 -> g77-3.3, then g77-3.4 won't be touched. [08:12] heh, yes, let's start ... [08:12] do we have a version of gcc which includes this fix? http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20973 [08:12] you are aware of https://www.ubuntulinux.org/wiki/BreezyToolchainTransition ? [08:13] yep [08:13] me too, excellent work! [08:13] ok, we are converting all the library packages first [08:14] any specific order? dependency-wise? [08:14] for a better view, see https://www.ubuntulinux.org/wiki/CxxLibraryList [08:15] dholbach: heh, good question, answer is in the wiki: Wait until all of your dependencies have been uploaded in c2 versions, and rebuilt on all architectures. [08:16] so we will rely on dep-wait? [08:17] or will elmo "freeze" every *c2 package until we are finished? [08:18] new lib packages cannot enter the archive, if there's already an 'ubuntu' package. [08:18] we will freeze all the application packages ... [08:19] Riddell: yes [08:19] could you explain it with libtest libtestc2 and program test which uses those? :-) [08:19] doko: in the archives now? [08:20] i didnt quite get what will will happen [08:20] Riddell: of course [08:20] excellent [08:20] dholbach: what didn't you get? [08:20] dholbach, all apps that depend on a c++ lib will be rejected if i undestood it right [08:21] until doko pulls the lever [08:21] ogra: correct [08:21] ok, but installing for example inkscape won't work in the transition time, because libgtkmm*c2 is available but not libgtkmm* [08:21] or didnt i understand it yet [08:22] dholbach, yep, gtkmm apps will break for a while... [08:22] dholbach: yes, that's correct, as you call it "Schmerz im Hintern" [08:22] alright [08:22] the "new" libraries will be built and put in the archive still? [08:22] dholbach: and all of KDE will break, that will be fun :-) [08:22] yep [08:23] alright... sounds good === ogra pats his gnome [08:23] what guidelines can i pass for the packaging === ogra comforts Riddell [08:23] "Some of them are handled specifically (mostly KDE)" doko, what's handled specially about KDE? [08:25] some KDE packages are not renamed, even if they contain shared libs. we'll only rename qt and kdelibs [08:25] doko: why does kdelibs have to be renamed? [08:25] it depends on qt too [08:26] but not every kde package depends on qt [08:26] I'm yet to find any [08:26] Riddell: we discussed that in Sydney ... and found some IIRC [08:27] not I, amu said he found some, I'll see if he knows which [08:28] doko: how much is going to be done automatically and how much by hand? [08:29] Riddell: the library packages by hand, the application packages automatically. you have to make the call for the KDE packages, which are applications, and which are libraries ... [08:30] ok, so what guidelines can i pass for the packaging, what do i need to tell the guys explicitly? about 1) the libraries 2) the applications? [08:30] what is the general attack plan for a MOTU? :-) [08:31] dholbach: you should delegate packages to people, all other things should be mentioned in the wiki [08:32] they will pick [08:32] if not, then we should complete the docs ... [08:32] i'll have to re-read the wiki then some dozen times to make sure i got everything [08:32] doko, will a rebuild and renaming be enough ? [08:33] we need to change the build-dependencies [08:33] doko, or do we have to expect odditys [08:33] and tell them to use a proper patching system [08:33] ? [08:33] and tighten the build-depends as well [08:34] dholbach: yes, the new ones enter the archive immediately [08:35] dholbach: no, please NO other changes in these uploads. we will use the bug reports to feed back exactly the transition changes to Debian [08:35] doko: how do I mark packages as libraries or applications? [08:35] ogra: ICEs [08:36] hmm... but thats nothing MOTU could fix... i mean compile issues we have to regard.... extra options, conflicting options, etc [08:36] doko: ok, need to read the wiki again [08:36] i seem to not get it yet and as i will need to tell people a couple of times, i want to understand it thoroughly [08:37] Riddell: we did talk about it in UDU, didn't we? maybe we should meet again with amu [08:37] dholbach: start with one package, and I can review it [08:37] dholbach, dont worry, i think i understand it and i was around during the big transition in debian some time ago.... [08:37] so i know what to expect worst .... ;) [08:38] little dumb dholbach will have to read it again [08:38] doko: don't think we need to meet again, just that it was amu not me who said there were packages that depended on kdelibs and not qt, I havn't found any [08:39] Riddell: in universe as well? [08:40] doko: dunno, is there an easy way to search? [08:40] lamont: how does the hppa toolchain look, or don't you care at the moment? [08:42] doko: He's waiting on me for glibc love on hppa [08:42] doko: Should be early next week. I just can't do that hacking on a single monitor system. I'm hoping p'haps Sunday evening. [08:42] ogra: for ICE's, a MOTU should extract the preprocessed source, add the command line, submit a bug report and put the bug report number in the comment field. then other people can continue [08:43] doko, would you mind to write some lines about how to do that on the wiki.... === amu [~amu@amu.developer.debian] has joined #ubuntu-toolchain [08:44] moin' [08:45] ogra: it's just recompiling with -save-temps, compress and send the resultint '.i' or '.ii' file [08:45] doko: what jbailey said [08:45] we have some very inexperienced guys in the MOTU wannabe league, so it sould be as easy as possible to "step in to help out" ;) [08:45] doko, [08:45] ok [08:46] ogra: it's even ok, if somebody else does this, but we have to know about ... [08:46] yep [08:47] we'll put a column on the wiki table for it... [08:47] we will keep the c2 suffix only until there's a new soname, right? [08:47] jbailey: that should be ok [08:47] dholbach: yes [08:48] so when do we start? Next Monday is bank holiday in Germany, and maybe somewhere else, so what about Tuesday? [08:48] sounds good [08:48] amu: do you know which packages depend on kdelibs but not qt? [08:48] this will mean that universe will start a week later, right? [08:48] monday is fine :) [08:49] dholbach, why ? [08:49] dholbach, anything we have to wait for ? [08:49] because most universe-c++-libraries will depend on main-crack [08:49] Riddell: all gnomepackages ? [08:49] ;) === chmj [~charles@wbs-196-46-69-187.wbs.co.za] has joined #ubuntu-toolchain [08:49] amu: on kdelibs? [08:50] dholbach: no, universe at the same time, for those, that don't depend on libs in main [08:50] hmm, i think there is a good bunch essential stuff in universe too... [08:50] amu: we talked about the necessity of renaming kdelibs4 ... [08:51] evening [08:51] fabbione: btw, if you haven't already, please add this channel to the logbot [08:52] lamont: he did: " now.. you got the logs... FIX SPARC YOU WANKERS!" === ogra points at ubuntulog [08:52] hehe === dholbach pipes innocently === lamont make a note to finish waking up sometime today [08:53] how about not renaming kdelibs4 and anything which is crazy enough to depend on kdelibs4 but not qt we just add a depend on qt [08:55] Riddell: doesn't work for existing apps [08:56] hmm yes [08:56] ok, now i see it clearer [08:56] amu, Riddell: please be careful about that issue, so that we have a solution, which works for Debian as well. A difference here would be a major PITA [08:56] so amu, where did you find packages that depend on kdelibs and not qt? [08:58] Riddell: good question ... at least they if they will not depends against qt kdelibs depend it [08:59] Riddell: you could search all dependencies of packages, which have kdelibs4, but not libqt3-mtc102 (or something like this) [09:00] ok.. the meetin in #u-meeting will start [09:00] i well tell the crowd that the KDE solution is still worked on, ok? [09:01] dholbach: what's happening in #ubuntu-meeting? [09:01] the briefing for the MOTU crew [09:01] Riddell, you should be there for qt/kde [09:03] ah kde-i18n* depends on kdelibs but not qt [09:04] ogra, dholbach: maybe just discuss the universe topics here as well, or point people here for questions [09:04] yes [09:04] yep [09:15] grep-available -Fdepends kdelibs4 --and --not -Fdepends libqt3 [09:15] looks to be quite a few, guess we will have to rename kdelibs4 [09:16] the question is are there other kde libraries which are also depended upon without qt [09:18] jbailey: just decided that you will be pestered about java specific things by the motu's === jbailey [~jbailey@dhcp802-2-37.dsl.ucc-net.ca] has joined #ubuntu-toolchain === ajmitch_ [~ajmitch@port162-41.ubs.maxnet.co.nz] has joined #ubuntu-toolchain === \sh [~shermann@server3.servereyes.de] has joined #ubuntu-toolchain [09:40] doko: can i have your tentative gcc ppc64 biarch packages or something ? === chmj [~charles@wbs-196-46-69-187.wbs.co.za] has left #ubuntu-toolchain [] === ChanServ [ChanServ@services.] has left #ubuntu-toolchain [] === lamont glares at cdbs, fix0rs it [09:50] q [10:17] svenl: http://people.ubuntu.com/~jbailey/glibc [10:18] svenl: http://people.ubuntu.com/~doko/gcc-powerpc [10:19] doko, the gcc will work on ppc32 too ? [10:19] svenl: heh, I never tried on ppc64 ... [10:21] doko: the above gcc packages, they are using the headers from suse as the older ones, or the real thing ? [10:21] doko: and you didn't provide the source packages. === dholbach [~daniel@td9091b75.pool.terralink.de] has left #ubuntu-toolchain ["Verlassend"] [10:22] svenl: these are built with jbailey's packages [10:22] ok. [10:22] source: apt-get gcc-3.4 [10:22] and edit debian/rules.defs [10:22] doko: no magic config option, apart from jbaileys ackages installed ? [10:22] ah, ok. [10:23] doko: i could then try building a biarch gcc-4.0 with those ? [10:23] yes, you can try, sure [10:24] :) [10:24] any chance of it actually working ? [10:25] I didn't try yet ... run the testsuite ;-P [10:26] doko: so, by installing all of the above, i should be able to create ppc64 executables, and also to build ppc64 kernels, right ? [10:26] doko: oh usable are the above on a debian system ? [10:27] svenl: I didn't test ... what about if you install them in a chroot? it shouldn't matter for a kernel build [10:27] bah, the packages need a newer version of linux-kernel-headers than the one in breezy. [10:27] doko: well. [10:27] doko: am runnin in a breezy chroot on a hoary powerbook right now. [10:27] sven: please ask jbailey about l-k-h [10:28] i found them [10:29] mmm, maybe. [10:29] damn. [10:29] jbailey: please ping me when you come back. [10:30] jbailey: your glibc is forced to use a l-k-h which is older than the one in breezy :/ [10:42] ls [10:42] doko: your gcc won do, it is too old for either the glibc currently in breezy or jbailey packages. [11:03] svenl: Ooh, that might be the one I had the typo in, sorry. [11:03] doko: The gcc you gave me before for building glibc on ppc64 worked fine for my testcases. === lamont waits to be told "go" on the bootstrapping process... [11:34] lamont: Working on it, still (again). elmo and I got rt up and running this morning. [11:34] jbailey: cool [11:49] Wow, ncftp isn't in main. [11:59] jbailey: you really want to support that??? [11:59] ISTR vomiting the last time I was hacking on that.