Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 86554 - Build tools for xscale-elf are not recognized
Summary: Build tools for xscale-elf are not recognized
Alias: None
Product: eCos
Classification: Retired
Component: ConfigTool
Version: CVS
Hardware: xscale
OS: Linux
Target Milestone: ---
Assignee: John Dallaway
QA Contact: John Dallaway
Depends On:
TreeView+ depends on / blocked
Reported: 2003-03-25 14:00 UTC by pascal Pediroda
Modified: 2007-04-18 16:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-03-25 14:43:41 UTC

Attachments (Terms of Use)

Description pascal Pediroda 2003-03-25 14:00:55 UTC
Description of problem:
Build tool folder with xscale-elf-* files is not seen as a valid folder.

Version-Release number of selected component (if applicable):
ConfigTool V2.11 (Windows 2000 Professional)

How reproducible:
Every time

Steps to Reproduce:
1.In ConfigTool, select the tools->paths->Build Tools
2.Browse for folder where xscale-elf-* are
Actual results:
The ConfigTool says it does not recognize arm-elf build tools.

Expected results:
The ConfigTool should recognize the xscale-elf build tools 

Additional info:
It did work in version 1.3

Comment 1 John Dallaway 2003-03-25 14:43:41 UTC
The configtool uses the CDL option CYGBLD_GLOBAL_COMMAND_PREFIX to determine 
which toolchain is required for a particular eCos target. Support for XScale 
targets is now fully integrated into the arm-elf toolchain and it is not 
necessary to use a specialized xscale-elf toolchain. The default values of 
CYGBLD_GLOBAL_COMMAND_PREFIX defined by the various eCos XScale HAL packages 
have been modified accordingly. If you wish to use an xscale-elf toolchain, 
you must now modify CYGBLD_GLOBAL_COMMAND_PREFIX using the configtool. 

Note You need to log in before you can comment on or make changes to this bug.