Hi, >> # ls -l /usr/bin/*-gcc >> -rwxr-xr-x. 2 root root 264112 Aug 23 2011 /usr/bin/i686-pc-mingw32-gcc >> -rwxr-xr-x. 2 root root 268216 Oct 18 18:24 >> /usr/bin/x86_64-redhat-linux-gcc >> >> I think the second part ("pc" / "redhat") can be choosen pretty freely >> when building gcc, so you could name your cross compilers differently, >> then have them in PATH and pick by name instead of typing full paths. > > For the most part I don't build these toolchains, so that's not an > option.
Ok. > Plus, I like having each toolchain fully contained in its own > directory. No need to change that, you can just stick all the directories into the PATH. Well, you could if the different compilers would have different names, thats why I suggested that ... >> ./configure >> --cross-prefix=/home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu- >> >> && make ? > > A few more options than that, but basically yes. > > I can get past this particular obstacle by doing something like: > > (PATH=/home/scott/.../powerpc-linux-gnu/bin:"$PATH" ./configure > --cross-prefix=powerpc-linu-gnu- ...) Why do you need this? Any tools not picked up correctly if you don't set the PATH? Which ones? > ...but then I run into the problem that --extra-cflags and > --extra-ldflags don't get passed into pixman. That should be fixable easily. Have a patch for that? If so, please send to the list. Otherwise I can have a look. Why do you need --extra-cflags + --extra-ldflags btw? cheers, Gerd