Build Rtems failed with Clang

[yangwei weiyang]

Hi all:
     When i build Rtems using Clang there is a problem i encounter. It
seems that it is related with configuration which can not probe the right
CC.
My configure command is :
----------------------------------------------------------------------------------------------------------------------------------------------------
CPU=i386
../rtems/configure --target=${CPU}-rtems4.11 --with-newlib \
  --prefix=/sdb1/rtems-llvm/rtems-install \
  CC_FOR_BUILD="clang " \
  CC_FOR_TARGET="clang -ccc-host-triple ${CPU}-rtems4.11 -ccc-gcc-name
${CPU}-rtems4.11-gcc "
-----------------------------------------------------------------------------------------------------------------------------------------------------
And it is OK, configure log is attached (named c.log)
Then i make RTEMS_BSP="pc386", it will failed when execut
c/src/lib/libbsp/i386/pc386/tools/configure. I see the
c/src/lib/libbsp/i386/pc386/tools/config.log
, when it check the build i686-pc-linux-gnu-gcc it using CC_FOR_TARGET. So
this is absolutely wrong.
I also attached make log (named b.log) and
c/src/lib/libbsp/i386/pc386/tools/config.log.

Wenjie
Best Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20120219/5b642126/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: c.log
Type: application/octet-stream
Size: 9532 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20120219/5b642126/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: b.log
Type: application/octet-stream
Size: 112522 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20120219/5b642126/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: application/octet-stream
Size: 9881 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20120219/5b642126/attachment-0002.obj>