This is the mail archive of the
ecos-bugs@sources.redhat.com
mailing list for the eCos project.
[Bug 1000070] New: Configtool startup type changes don't take effect
- From: bugzilla at ecoscentric dot com
- To: ecos-bugs at sources dot redhat dot com
- Date: Wed, 3 Mar 2004 16:05:47 +0000 (GMT)
- Subject: [Bug 1000070] New: Configtool startup type changes don't take effect
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000070
Summary: Configtool startup type changes don't take effect
Product: eCos
Version: 2.0
Platform: pc (i386 PC target)
OS/Version: HostOS: Win NT/2k/XP
Status: NEW
Severity: normal
Priority: normal
Component: ConfigTool
AssignedTo: jld@ecoscentric.com
ReportedBy: jifl@ecoscentric.com
QAContact: ecos-bugs@sources.redhat.com
This is with a freshly installed eCos 2.0 installation on Windows XP. Just
bringing up the configtool and changing the startup type works if you do it
before saving the configuration, and doesn't work correctly if you do it after
saving.
To reproduce, bring up the config tool. It defaults to the PC target. Change the
startup type to FLOPPY and then save as config "justfloppy". Now restart the
config tool (to be sure there's no state left), "Save As..." the config to
"ramthenfloppy". And then set the startup type to FLOPPY and save again.
At a cygwin shell do a "diff -urN" between the install trees. They should be
identical but they are not, and in fact MLT files are still given as RAM in the
"ramthenfloppy" version, thus breaking everything!
See the attached file for the install tree differences, and note the existence
of a file __libcdl_file1 in the ramthenfloppy_install/include/pkgconf directory
that does not exist in "justfloppy". This file is the correct version of
system.h, but for some reason it did not replace the system.h.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.