[gccsdk] [GCCSDK commit] peter - r4189 - trunk/gcc4
John.Tytgat at aaug.net
Sun Nov 8 04:33:42 PST 2009
In message <E1N6uYr-0005Gk-3a at riscos.info> you wrote:
> Author: peter
> Date: 2009-11-07 15:19:12 -0800 (Sat, 07 Nov 2009)
> New Revision: 4189
> Fix path to zip
> Modified: trunk/gcc4/create-gcckit
> --- trunk/gcc4/create-gcckit 2009-11-07 15:40:41 UTC (rev 4188)
> +++ trunk/gcc4/create-gcckit 2009-11-07 23:19:12 UTC (rev 4189)
> @@ -345,8 +345,8 @@
> if [ "$GCCSDK_DO_PKG" == "YES" ] ; then
> # Package all the kits:
> - if [ ! -f $GCCSDK_CROSS_PREFIX/bin/zip ] ; then
> - echo Unable to create kits because of missing zip executable $GCCSDK_CROSS_PREFIX/bin/zip.
> + if [ ! -f $GCCSDK_INSTALL_ENV/bin/zip ] ; then
> + echo Unable to create kits because of missing zip executable $GCCSDK_INSTALL_ENV/bin/zip.
> exit 1
I know this is continuing on a change made in the past, but it still feels
wrong to have tools running on the host hardware installed and deployed
at $GCCSDK_INSTALL_ENV/bin, that really should be $GCCSDK_CROSS_PREFIX/bin
together with the rest of the cross compiler toolchain.
We should expect that all binaries at $GCCSDK_INSTALL_ENV/bin are
RISC OS binaries, like we expect that all libraries at
$GCCSDK_INSTALL_ENV/lib are RISC OS libraries.
And that all binaries at $GCCSDK_CROSS_PREFIX/bin (mmh, which is also
$GCCSDK_INSTALL_CROSSBIN) are binaries running on the host computer, i.e.
that platform on which the cross-compiler tools run on.
John Tytgat, in his comfy chair at home BASS
John.Tytgat at aaug.net ARM powered, RISC OS driven
More information about the gcc