This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
>>>>> "Craig" == Craig Vanderborgh <craigv@voxware.com> writes: Craig> Hello All: Craig> I am trying to build the latest version of eCos (on Craig> x86/Redhat 7.1) and am having some trouble. As per the Craig> instructions in README.host, I creating a build tree Craig> subdirectory, entering it, and running: Craig> % ../configure Craig> Unlike the previous version of eCos I've been using, this Craig> operation does not produce the expected results, in Craig> particular a "host" directory populated with its usual Craig> contents. What am I missing here? Normally I create a completely separate build directory, rather than a "build" subdirectory in the eCos repository. That way CVS will never complain that it does not know anything about "build". However I just tried configuring and building in a "build" subdirectory (x86, RH 7.2) and it seemed to work just fine. Does the configure script report any errors? A fairly recent change is that there is now an acsupport directory at the toplevel of a CVS checkout, containing some configury information that is shared between the generic host-side and package-specific host support. The configure script will fail if that directory is missing. If so you need to do another CVS checkout of the ecos-full module. Bart -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |