[04:47] <GyrosGeier> hi
[04:48] <GyrosGeier> given the massive overlap in toolchain maintainers and the lack of a #debian-toolchain, I think it's a good thing to ask here
[04:48] <GyrosGeier> I am building packages that provide wrappers around gcc that make it compile against uclibc
[04:49] <GyrosGeier> for that to work, I need to create symlinks from e.g. /usr/lib/gcc/foo-linux-uclibc/4.1.2/cc1 to /usr/lib/gcc/foo-linux-gnu/4.1.2/cc1
[04:50] <GyrosGeier> however gcc version is currently at 4.1.1-*
[04:50] <GyrosGeier> and somewhere in the 4.1.1-* time, directory switched from .../4.1.1 to .../4.1.2
[04:51] <GyrosGeier> since my symlinks only work if the directories do not change, I'm wondering how to form a dependency that will break as soon as gcc's tool directory changes
[04:51] <GyrosGeier> and not much more often than that, ideally
[04:52] <GyrosGeier> (specifically, I'd like to avoid an (= 4.1.1-12) dependency, for obvious reasons)
[04:52] <GyrosGeier> any ideas?
[05:57] <jb-home> doko: There?
[05:58] <doko> jb-home: hey, back to your second baby? ;-P
[05:58] <jb-home> Yeah. =)
[05:59] <jb-home> I just noticed that gcc-3.4-hppa64 has a dependancy on libc6-dev.  I don't think it should.  It's not worth fixing that package or doing an upload for it, but might be nice to remove it for future gcc versions.
[06:00] <doko> ok, will have a look
[06:00] <jb-home> Thanks. =)
[06:00] <jb-home> How's things? =)
[06:01] <doko> see my toolchain mail; currently gcc-4.1 doesn't build anymore due to the new binutils
[06:01] <doko> on powerpc and sparc
[06:13] <jb-home> Joy.  My toolchain mail goes to my work account, I should probably change that.
[06:13] <jb-home> Once I get some more hppa stuff building, I'll take a look at ppc.