#ubuntu-toolchain 2006-02-05
-S0LaRlMp:#ubuntu-toolchain- New game started, http://sre.servegame.com  : This is a webgame based on SOLAR REALMS ELITE, a famous BBS game back in 1992 (Earth2025/BRE fans are welcome)
<dpm> I'm compiling a program where libtool is invoked with the -LNONE option from the makefile. Well, my version of libtool does not seem to like that, and the problem disappears when I manually change LDFLAGS = -LNONE to LDFLAGS =. My question is: was this NONE keyword maybe supported by an older version of libtool and was dropped in the newer version, or is there something wrong with the makefile?
#ubuntu-toolchain 2006-02-16
<_user> I've a problem with prelink on dapper drake. it prints: "/usr/bin/prelink.bin: dependency trace failed". i suspect it has to do with the libc6 update on 09.02.2006. has anyone experienced this or do you have a hint for me? bugreport etc??
#ubuntu-toolchain 2006-02-21
<jbailey> https://launchpad.net/distros/ubuntu/+source/evolution is telling me I don't have access to this page.
<jbailey> Bah, ECHAN
<jbailey> Applied.  But with the changes I checked in before all archs but x86 and
<jbailey> x86-64 are broken again.  Somebody needs to write the generic
<jbailey> lowlevelrobustlock.c file and adjust the lowlevellock.h files.
<jbailey> .
<jbailey> I wonder if Roland was being overoptimistic when he said that 2.4 would be out by April...
#ubuntu-toolchain 2006-02-26
<tepsipakki> lamont: ping
<tepsipakki> lamont: I mailed you
* lamont reads https://launchpad.net/malone/bugs/29187
<lamont>  and giggles
<lamont> hrm.. wrong channel
#ubuntu-toolchain 2006-02-27
<fabbione> doko: ping?
<doko> fabbione: good morning!
<fabbione> hey doko
<fabbione> doko: gcj-4.1 is building on sparc as we speak
<fabbione> i will let you know when it's done
<doko> yes, I checked before that it does build
<fabbione> ok
<fabbione> the sparc boxes are at the DC
<fabbione> they should be installed today
<fabbione> assuming they don't fry like the first one i did install
<doko> developer machine as well?
<fabbione> i think so
<doko> what kind of machine?
<fabbione> well as it is with one down, the 2/3 left will go in buildd rotation
#ubuntu-toolchain 2007-02-05
<fabbione> doko: ping?
<doko> fabbione: pong
<fabbione> doko: i just noticed the 2 gcc uploads.. is there anything specific like glibc that needs a rebuild?
<doko> fabbione: no, I don't think so.
<fabbione> doko: ok thanks dude
#ubuntu-toolchain 2007-02-06
<Dvalin> doko: around?
#ubuntu-toolchain 2007-02-07
<jbailey> doko_: Is it correct that the gcc build doesn't seem to honour DEB_BUILD_OPTIONS="nocheck" ?
<doko_> jbailey: yes, I think it's fixed for 4.2. WITHOUT_CHECK=yes works however
<jbailey> Ah well, it' shalfway through the gcc tests now.
<jbailey> Hopefully this won't take all night.
<jbailey> doko_: Before work this morning I started a new gcc build with what is hopefully a fixed glibc on hppa.
<jbailey> Checked it after a I got back from lunch. =)
#ubuntu-toolchain 2007-02-11
<jb-home> doko: ping
<doko> jb-home: pong
<jb-home> doko: They might be, I read the changelogs of them and pull out changes occasionally.  Mostly they've been updating to new freebsd support and such.
<jb-home> It's worth subscribing to the changelog.
<jb-home> But our glibc is always going to ride ahead of Debian's.
<jb-home> We also differ in a number of significant ways - they're still dragging along LT patches, for instance.
<doko> well, if you do have packages which can be installed on top of dapper ...
<jb-home> Dapper?
<doko> or was it breezy?
<doko> the last hp ...
<jb-home> Dapper still had LT support.
<jb-home> on i386, that is.
<jb-home> Edgy dropped it there, too.
<doko> so where are your glibc hppa packages?
<jb-home> Oh!  I see. =)
<jb-home> I have them on a500-hppa.montreal.canonical.com.  The binutils CVS that we've updated to is more picky about CFI constraints.
<jb-home> I updated to that after I got ubuntu10 building.
<jb-home> diff -uNr glibc-2.5.orig/ports/sysdeps/hppa/dl-trampoline.S glibc-2.5/ports/sysdeps/hppa/dl-trampoline.S
<jb-home> --- glibc-2.5.orig/ports/sysdeps/hppa/dl-trampoline.S	2006-09-07 16:34:43.000000000 +0000
<jb-home> +++ glibc-2.5/ports/sysdeps/hppa/dl-trampoline.S	2007-01-30 15:15:58.000000000 +0000
<jb-home> @@ -284,5 +284,6 @@
<jb-home>  	bv,n	0(%r2)
<jb-home>          .EXIT
<jb-home>          .PROCEND
<jb-home> +	cfi_endproc
<jb-home>  	.size   _dl_runtime_profile, . - _dl_runtime_profile
<jb-home> Is what's needed with the new binutils.
<jb-home> So I'll start that build in a moment.
<doko> I'll have a new binutils tomorrow
<fabbione> so we need new binutils and new gcc and we are good to go?
<fabbione> and new binutils will be able to build a working kernel?
<doko> for feisty+1 ...
<jb-home> fabbione: The binutils and gcc are already in the snapshot archive.  But they uncovered another bug in glibc.
<doko> snapshot archive? did I miss something?
<fabbione> so there is no hope to get hppa running for feisty?
<jb-home> doko: http://people.ubuntu.com/~jbailey/snapshot/hppa-feisty/
<fabbione> doko: it's his personal archive
<doko> ahh
<fabbione> brb.. my son is crying
<jb-home> fabbione: I haven't tested a kernel build with the binutils yet.  The kernel FTBFSs at the moment.
<jb-home> I think the hppa patches haven't been updated.
<jb-home> That'll block going ahead still, since we need the linux-libc-dev from it.
<jb-home> doko: I'm still hoping for at least main for feisty.
<jb-home> doko: For binutils, We had been using the bzr repo before, I think.
<jb-home> Would you mind going back to using it so we can share a bit easier?
<doko> yes, I can check in things there ... did debian packages yesterday
<jb-home> Cool.
<jb-home> What prompted the update?
<fabbione> jb-home: feh
<jb-home> fabbione: Eh, you know the life of a non-archive port as well as I do.
<fabbione> oh fuck... my son can't fall asleep
<fabbione> BRB
<jb-home> It's like chasing a train that's running just a bit faster than you are.
<doko> jb-home: the powerpc binutils could not built with themself, that works in the update
<jb-home> Ah, cool.
<jb-home> Well, binutils -ubuntu11 building on my hppa box.
<jb-home> LaMont offered to help with the hppa porting stuff, so I'm going to ask him to please twiddle the kernel into a buildable state.
<fabbione> jb-home: ok... well do you recall where the kernel FTBFS?
<fabbione> perhpas we can get kyle or Ben to fix it
<fabbione> i am sure Ben can do it
<jb-home> Nope, but it was about 30 seconds into the build, less than a page of "CC "...
<fabbione> ok
<fabbione> i might take a look at it sometimes next week
<fabbione> but i don't promise
<jb-home> Sure, I wanted to hand off to lamont because 1) He offered. 2) It means thatI can totally drop it from my thoughts.
<fabbione> sounds like a plan :)
<fabbione> but without running/building kernel we will still hit other issues
<jb-home> I need building kernel ASAP.
<jb-home> Running kernel can wait a week or two if it needs to.
<fabbione> i suggest we talk to Ben.. specially because we will need a kernel source in the archive for the bootstrap to happen
<fabbione> he has hppa in his barn
<jb-home> I'm sure Ben will be involved.
<jb-home> But you missed the point.
<jb-home> I don't want to care about the djennings@example.org.
<jb-home> I'm handing that off to someone else as quickly as I can. =)
<fabbione> yeah yeah i got it
<fabbione> we as in lamont/me
<fabbione> there... so you are happy ;)
<jb-home> \o/
<jb-home> Whee, the new glibc build appears to have gotten past the stage where it died last time.
<jb-home> So hopefully one more upload and we're all good. =)
#ubuntu-toolchain 2007-02-27
<lamont> doko:   * Reenable the workaround for a build failure on the ia64 buildd.
<lamont> what's that gdb changelog entry referring to?
<doko> lamont: it hangs in make check 2>&1 | tee log, now its >log 2>%1
<lamont> how very strange
#ubuntu-toolchain 2008-02-03
<arthur-> hi
<arthur-> doko: is -9 ok for the gdc lzma compression level?
<doko> arthur-: I didn't set the level explicitely
<arthur-> doko: ok
#ubuntu-toolchain 2008-02-12
<Mithrandir> doko: so, I have this idea.  Why isn't -Wall on by default?
<doko> we can try this, but I'd like to avoid stuff which breaks with -Werror
<Mithrandir> agreed, but I don't think anybody would use -Werror and not -Wall.  I'm probably wrong on a few packages, but probably not very many.
<doko> sure, at least we don't break things silently =)
<Mithrandir> hehe, that's true.
<Mithrandir> I think we might want to hold off until hardy+1 is bootstrapped.  What do you think?
<doko> it could be fine for the bootstrap as well, and then fix things
<Mithrandir> yes, that was what I meant.
#ubuntu-toolchain 2008-02-18
<\sh> doko: hi :) something weired is happening in wine country...and it looks like that something changed in between wine 0.9.54 and 0.9.55, there was a gcc upload from 636-721-3251 to 636-721-3251 was something elementary changed in this release ? looks like that something is going wrong in the wine-preloader thing
#ubuntu-toolchain 2008-02-20
<infinity> doko: Around?
<doko> infinity: yes
<infinity> doko: When we demoted gcc-3.3 to universe, we ended up with broken/mismatched overrides, since libgcc1/hppa still comes from gcc-3.3
<infinity> doko: Suggestions?  Drop libgcc1/hppa from gcc-3.3 entirely, build it from a newer gcc, promote gcc-3.3 back to main?
<doko> infinity: it should not be needed anymore. packages depending on it should be rebuilt
<infinity> Nothing depends on it, I checked that.
<infinity> So, you'd opt for "drop it completely"?
<doko> hmm, that would mean to remove gcc-3.3 for hppa from universe
<infinity> I can't imagine anyone complaining...
<doko> sure, but I'd like to avoid a new upload to just disable it
<infinity> I take it that building libgcc4 and libgcc1 from gcc-4.2 is a technical impossibility?
<doko> yes
<infinity> Figured.
<infinity> Anyhow, override mismatches cause DAK to explode, so we need to do something to fix this.
<doko> but then you should remove 3.4 and 4.0 as well (but maybe too much fortran stuff still depends on it=
<doko> so just remove it, and don't upload 3.3 again?
<infinity> Heh.
<infinity> Removing it will probably just cause a new build to happen on hppa.
<infinity> (I could P-a-s it out, but I'm not sure Debian would be keen on that change..)
<doko> well, try to upload a new version, which fails for hppa
<doko> but it should still work for the other archs. maybe upload to the ubuntu-toolchain ppa first?
<infinity> I imagine it would fail on hppa quite convincingly if I just removed the libgcc1 stanzas from control...
<infinity> Alternately, I could change every single arch:any binary to arch:i386,amd64,powerpc,sparc,lpia,ia64 ...
<infinity> *shudder*
<doko> well, just let the build fail
<doko> I think there's something like this for alpha
<infinity> pre-build:
<infinity> #ifeq (,$(filter $(DEB_TARGET_ARCH), $(build_only_archs)))
<infinity> #       @echo "The package is not built anymore for $(DEB_TARGET_ARCH)"
<infinity> #       @exit 42
<infinity> #endif
<infinity> That stuff?
<infinity> I can just replace that with "ifeq ($(DEB_TARGET_ARCH),hppa)" and uncomment it.
<infinity> doko: http://people.ubuntu.com/~adconrad/gcc-3.3.diff
<infinity> doko: Look good?
<infinity> lamont: Any complaints about the above?
 * lamont looks
<infinity> lamont: I would just P-a-s it out of hppa, but Debian might not like that (and we don't maintain our own P-a-s, for sanity's sake...)
<lamont> rigth
<lamont> +1
<doko> yes
<infinity> Kay, that's two +1s, uploading.  Thanks.
<infinity> doko: Hahaha.  I didn't even have to change the package at all, oh well. ;)
<infinity> doko: gcc-3.3 build-depends on itself, so removing it from the archive was enough to permanently break it.
#ubuntu-toolchain 2008-02-21
<doko_> infinity: well, it was just moved to universe, wasn't it?
#ubuntu-toolchain 2012-02-08
<Corey> doko: Howdy!
<Corey> I was told to ping you about getting dh_python2 working under Lucid.  
<doko> Corey, yeah, I need to catch up with this ...
<Corey> doko: Yeah.  What can I do to pitch in?
<doko> Corey, I'll update it next week, not this week while at Linaro Connect
#ubuntu-toolchain 2016-02-21
<doko> so gnutls is coupled with bind9 and linux; removed netexpect, trying to get filezilla done

{'channel': 'ubuntu-toolchain', 'month': 2}