doko | infinity: when will the new gcc-defaults available on the buildd's? | 12:18 |
---|---|---|
infinity | When it's installible? | 12:32 |
infinity | (hint: depending on compilers newer than what we have isn't helpful) | 12:33 |
doko | infinity: hint: we don't have any mechanism to avoid that | 12:37 |
infinity | Sure we do. Make it build-dep on all the same packages/versions that it will eventually depend on. :) | 12:40 |
infinity | Then it'll be FTBFS until they're available. | 12:41 |
infinity | (Yes, it's ugly, but it would work) | 12:42 |
infinity | Anyhow, the alternate solution is for you to merge gcc-4.0_4.0.2-3. :) | 12:44 |
doko | I'm not supposed to merge things, if no merge is needed :-P | 01:32 |
doko | infinity: ^^^ | 01:32 |
infinity | Well, then you better upload a new gcc-defaults_1.29ubuntu1 that drops that compiler dependencies again for now. | 01:37 |
infinity | s/that/the/ | 01:37 |
doko | well, then I do prefer a gcc-4.0_4.0.2-3build1 | 01:38 |
elmo | err, what? | 01:40 |
elmo | for fuck's sake, will you guys chill out | 01:40 |
elmo | the sync stuff is running full time, catching up with the backlog, and I'm running around trying to get ready to fly tomorrow | 01:41 |
elmo | the world's not going to end if we don't sync a new gcc in the next 24 hours | 01:41 |
doko | elmo: no it doesn't end, just that the new gcc-defaults is already built, and gcc depending on gcc-4.0 (>= 4.0.2) | 01:43 |
elmo | so nothing's building? | 01:45 |
doko | that was the question: what happens, if the buildd's are updated to the new gcc and g++. currently nothing should build which uses gij/gcj/gfortran/gobjc | 01:49 |
infinity | The buildds can't be updated, since gcc is uninstallable. :) | 02:03 |
infinity | elmo : Anyhow, this has nothing to do with syncs, unless gcc-4.0 is meant to be synced (looks to me like it shold be merged..) | 02:04 |
infinity | Oh, unless doko requested a sync-with-overwrite. | 02:04 |
=== infinity shrugs. | ||
infinity | Whatever's going on, you'll get your new GCC when you get it. | 02:06 |
=== fabbione [n=fabbione@port49.ds1-van.adsl.cybercity.dk] has left #ubuntu-toolchain ["Leaving"] | ||
=== jbailey [n=jbailey@testhaus.cns.utoronto.ca] has joined #ubuntu-toolchain | ||
=== doko [n=doko@HSE-Toronto-ppp176543.sympatico.ca] has joined #ubuntu-toolchain | ||
lamont-away | g77: Depends: cpp (>= 4:4.0.2-1) but 4:4.0.1-3 is to be installed | 05:47 |
=== lamont-away grumbles | ||
=== karlheg [n=karlheg@host-250-237.resnet.pdx.edu] has joined #ubuntu-toolchain | ||
=== fabbione [n=fabbione@217.205.109.249] has joined #ubuntu-toolchain | ||
=== lamont [n=lamont@mib.fc.hp.com] has joined #ubuntu-toolchain | ||
=== doko [n=doko@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-toolchain | ||
lamont | Oct 26 07:57:11 buildd: Starting build (dist=dapper) of: | 04:27 |
lamont | Oct 26 07:57:11 buildd: gcc-3.3_1:3.3.6-10 gcc-3.4_3.4.4-9 gcc-4.0_4.0.2-3 dash_0.5.2-8 nessus-core_2.2.5-2 | 04:27 |
=== lamont crys | ||
lamont | cries, even | 04:27 |
lamont | gcc-3.3: 04:24:26 (1 entry, sigma 00:00:00) | 04:28 |
lamont | gcc-3.4: 11:34:22 (2 entries, sigma 00:44:39) | 04:28 |
lamont | gcc-4.0: 06:49:38 (2 entries, sigma 00:49:37) | 04:28 |
lamont | not much in the way of hppa uploads for the next 20 hours or so | 04:28 |
=== lamont disables ccache for builds of gcc-{3.3,3.4,4.0,snapshot} just because it's not gonna do anything anyway | ||
doko | why does gcc-3.4 takes so long? | 05:45 |
doko | lamont: and disable it for gcc-4.1 and gcc-snapshot as well ... | 05:46 |
lamont | 3.4 is just lucky or something... could be the expect bug | 05:47 |
lamont | s/expect/"expect"/. | 05:47 |
lamont | doko: that's true on all architectures, yes? | 05:47 |
=== lamont needs an hppa/mips patch to ld -r so that it doesn't merge sections (or emits long branch stubs if it merges) | ||
lamont | well, ok... I don't need or care about mips, but it has the same issue. :-) | 05:48 |
lamont | doko: remind me to hurt you if your next gcc-3.3 upload still uses expect instead of expect-tcl8.3 on hppa, k? :-) | 05:59 |
doko | lamont: well, it should be on all archs | 05:59 |
lamont | ok - I'll change the default gcc-opt config then | 05:59 |
doko | lamont: I think I did fix it ... | 05:59 |
lamont | expect (>= 5.38.0) [!hurd-i386] , | 06:00 |
lamont | gcc-3.3_1\:3.3.6-10 | 06:00 |
doko | ahh, no. will do it. the debian expect maintainer seems to be mia | 06:01 |
lamont | well, it's not properly an expect bug... iz kernel bug (I think) | 06:02 |
lamont | but the name sticks | 06:02 |
lamont | doko: I think 3.4's long time may be related to logwatch not exiting | 07:32 |
lamont | or maybe that's the "expect bug" again. | 07:32 |
=== elmo [n=james@83-216-156-21.jamest747.adsl.metronet.co.uk] has joined #ubuntu-toolchain | ||
lamont | hi elmo | 08:02 |
=== karlheg [n=karlheg@host-250-237.resnet.pdx.edu] has joined #ubuntu-toolchain |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!