Fossil SCM
checkout/build failure
ef48c60cee1483e…
· opened 15 years, 5 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Important
- Resolution
- Fixed
- Subsystem
- —
- Created
- Oct. 26, 2010 11:19 p.m.
Using fossil [d13056] to co fossil repo at [57347e6ee87a] yields:
gcc -g -O2 -o mkindex ./src/mkindex.c ./mkindex add_.c allrepo_.c attach_.c bag_.c blob_.c ... >page_index.h gcc -g -O2 -o makeheaders ./src/makeheaders.c gmake: *** No rule to make target `src/../manifest.uuid', needed by `VERSION.h'. Stop.
where fossil set is:
[bch@ansel ~/work/fossil]$ fossil set auto-captcha auto-shun autosync (local) 1 binary-glob clearsign diff-command dont-push editor gdiff-command ignore-glob http-port localauth (local) 0 manifest mtime-changes pgp-command proxy repo-cksum ssh-command web-browser
The following will fix at command line, but is a brittle solution to real problem (in header file):
fossil set manifest 1
drh added on 2010-10-26 23:44:27: Once I get the server updated, new clones will set the "manifest" option automatically. What other fix do you suggest? Make "manifest" the default? The feedback I have received about the manifest and manifest.uuid files is uniformly negative - everybody hates them it seems - so it seems best to leave them turned off by default.
anonymous added on 2010-10-30 18:45:48: Hi, I recently got this error too. Could a command be implemented to generate the manifest and manifest.uuid files? Then they could be deleted when the build finishes. Thing is, this wouldn't work if you just zipped up the working tree and sent it to someone. Hmm. Thanks, kj4ufx.
drh added on 2010-10-31 23:14:15: The command
fossil set manifest on
creates the manifest and manifest.uuid files, in addition to making sure they are updated on all future checkouts.
If the "manifest" setting for a server is "on", then all ZIP archives generated by that server include the "manifest" and "manifest.uuid" files.