corsepiu at faw.uni-ulm.de
Fri Nov 10 10:03:41 UTC 2000
Dmitry Kargapolov wrote:
> When I used rtems-ss-20000802 snapshot,
> I had the next lines in the <install-dir>/make/target.cfg file:
> CC = /usr/local/rtems/bin/i386-rtemself-gcc --pipe
> AS = /usr/local/rtems/i386-rtemself/bin/as
> AR = /usr/local/rtems/i386-rtemself/bin/ar
> NM = /usr/local/rtems/i386-rtemself/bin/nm
> LD = /usr/local/rtems/i386-rtemself/bin/ld
> SIZE = /usr/local/rtems/bin/i386-rtemself-size
> STRIP = /usr/local/rtems/i386-rtemself/bin/strip
> OBJCOPY = /usr/local/rtems/bin/i386-rtemself-objcopy
> RANLIB = /usr/local/rtems/i386-rtemself/bin/ranlib
> CXX = /usr/local/rtems/bin/i386-rtemself-g++
> Now I try rtems-ss-20001103, and I see in <install-dir>/make/target.cfg
> CC = i386-rtemself-gcc
> AS = i386-rtemself-as
> AR = i386-rtemself-ar
> NM = i386-rtemself-nm
> LD = i386-rtemself-ld
> SIZE = i386-rtemself-size
> STRIP = i386-rtemself-strip
> OBJCOPY = i386-rtemself-objcopy
> RANLIB = i386-rtemself-ranlib
> CXX = i386-rtemself-g++
> Why? How can I handle this situation?
Where is your problem? What is wrong with the new style of
[--pipe having vanished from CC is a minor bug of this snapshot - It
has already been fixed in OAR's internal source-tree.]
> Is it bug of the "configure"?
No, this happened on purpose.
The disadvantage of the former target.cfg was that it contained
This can render these target.cfgs unusable if sharing installed
copies of RTEMS across a network (eg. automounter prefixes) or if
using different versions of the toolchain.
> Where is the sutable place to define path to cross-tools for my bsp?
Simply set up $PATH accordingly. In your case, make sure to have
/usr/local/bin in $PATH rsp. if using OAR's rpms make sure to have
/opt/rtems/bin in $PATH.
Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung
Helmholtzstr. 16, 89081 Ulm, Germany Tel: +49/731/501-8690
mailto:corsepiu at faw.uni-ulm.de FAX: +49/731/501-999
More information about the users