This service will be undergoing maintenance at 20:00 UTC, 2017-04-03. It is expected to last about 30 minutes
Bug 58178 - Bad: file is missing
Bad: file is missing
Product: eCos
Classification: Retired
Component: ConfigTool (Show other bugs)
arm7 Linux
medium Severity medium
: ---
: ---
Assigned To: Julian Smart
eCos bugs internal list
Depends On:
  Show dependency treegraph
Reported: 2002-01-10 11:38 EST by Need Real Name
Modified: 2007-04-18 12:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-01-10 14:17:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-01-10 11:38:41 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
Config Tool 2.08 has a bug when loading self generated file:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Start Config Tool, set for Cirrus Logic developement board, ad Networking
2. Include in eCos HAL->Source level debugging support->Include GDB Stubs in HAL
3.Start Build->Library

Actual Results:  Last messages are

make[1]: Leaving directory `/ecos-c/0eC/net2_build/hal/arm/arch/v1_3_1'

In file included from =

make: Leaving directory `/ecos-c/0eC/net2_build'

/ecos-c/0eC/net2_install/include/pkgconf/mlt_arm_edb7211_ram.ldi:5: =
cyg/infra/ No such file or directory

make[1]: *** [/ecos-c/0eC/net2_install/lib/target.ld] Error 1

make: *** [build] Error 2

Expected Results:  correct library generation

Additional info:
Comment 1 Jonathan Larmour 2002-01-10 14:17:15 EST
Actually this problem is because you are using the 1.3.1 repository with a newer
configuration tool. Either use the anonymous CVS repository, or create the file
packages/infra/v1_3_1/include/ yourself as an empty file.

This will be irrelevant when 2.0 comes out.

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