On Wednesday 16 November 2011 04:55:52 Joakim Tjernlund wrote: > Mike Frysinger <[email protected]> wrote on 2011/11/13 19:06:17: > > On Saturday 12 November 2011 18:39:33 Joakim Tjernlund wrote: > > > I guess crossdev should run binutils-config automatically? > > > > nah ... binutils eclass itself should be doing this already in toolchain- > > binutils_pkg_postinst > > > > > BTW, somewhat offtopic but why isn't libtool-2.4.2 unstable yet? > > > > no real reason. i forgot about it, and since no one has filed bugs about > > it breaking them horribly, i'll move it into ~arch now. > > Something else I noted. I remembered I had binutils 2.18 installed too: > $ binutils-config -l > [1] i686-pc-linux-gnu-2.20.1 * > > [2] powerpc-softfloat-linux-gnu-2.16.1 > [3] powerpc-softfloat-linux-gnu-2.18 *
these are toolchains in ROOT=/ [1] is probably: CHOST=i686-pc-linux-gnu CTARGET=i686-pc-linux-gnu [2] and [3] is probably: CHOST=i686-pc-linux-gnu CTARGET=powerpc-softfloat- linux-gnu > and I can select it but > > CHOST=powerpc-softfloat-linux-gnu \ > ROOT=/usr/powerpc-softfloat-linux-gnu \ > binutils-config -l > > Using binutils-config info in /usr/powerpc-softfloat-linux-gnu/ > [1] powerpc-softfloat-linux-gnu-2.16.1 * > > Only shows 2.16.1 these are toolchains in ROOT=/usr/powerpc-softfloat-linux-gnu/ [1] is probably: CHOST=powerpc-softfloat-linux-gnu CTARGET=powerpc-softfloat- linux-gnu -mike
signature.asc
Description: This is a digitally signed message part.
