[Bug 1000136] target.ld make dependencies incomplete, so startup type changes ineffectual

[bugzilla at ecoscentric dot com]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000136


jifl@ecoscentric.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bartv@ecoscentric.com
         AssignedTo|bartv@ecoscentric.com       |jld@ecoscentric.com
             Status|NEEDINFO                    |NEW
          Component|CDL                         |ConfigTool




------- Additional Comments From jifl@ecoscentric.com  2005-08-02 05:17 -------
Yes when I said MLT files I was talking about .ldi primarily, not .mlt.

But on looking closer, it looks like it's some other non-straightforward issue,
and I was presumptuous with my "diagnosis". Maybe CDL, maybe config tool.

Taking the AdderII as an example, and using Windows as my OS (I have some
unrelated problems on Linux), if I select the adderII as my platform with the
kernel template, and then build it, that's fair enough. If I then go into the
adder HAL config and change the startup type to ROM, click elsewhere (another
bug that IMHO), and then click the save button, I can then appear to build. But
something's actually gone wrong, and the exes will be bogus. On closer
investigation the blah_install/include/pkgconf/system.h file has not been
updated with the new startup type.

But notably, in that directory there is a file "__libcdl_file1" which looks like
a partial new system.h, which does have the startup type correct. (At this point
I definitely have deja vu over seeing that file, but I don't see anything in
bugzilla about it.)

So it looks like something's failed, but nothing's noticed. Anyway, I think I
need to reassign to Jld as a config tool issue (since ecosconfig doesn't have it).

Incidentally I also get an odd visual effect when I open the AdderII HAL CDL
package, at least in the windows config tool. The configuration pane goes blank
and flickers for about 10 seconds. Related? Hmm.





------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.