-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot build due unicode.h include error #1
Comments
It appears all the necessary files are there. Did you try a make clean first? |
yes.. also im do a cleanall.sh
|
also fail cterm.c for base64.h
|
i want to add that i can compile whitout problem under my cvs root of my bbs instance |
unicode.h should be located in the src/xpdev directory. Is it there? If they are not, a "cvs update -d" in those directories should get the files. |
These files are not in the git mirror (that sems the problem): https://github.com/RealDeuce/cvs-synchronet-src/tree/origin/xpdev |
I think then that I am not the right asignee. :-) |
@rswindell that file has never been added to CVS (though it is in the repo), so there's no commit that added it in this repo. The commit for encode/unicode.h is weird as well. |
Yeah, the files were originally committed in a different location by moved on the server (to retain history). The files have been updated since then however. Is that not enough for the CVS->Git thing to know they exist? |
Unfortunately no, the CVS->git thing only converts commits... so if there's no initial commit, the patches can't apply. Maybe I can jelly the current version in... |
@ftoledo I've added unicode.h... let me know if anything else is missing. |
For future reference, the "proper" way to move a file in CVS with history is:
|
Oh, it's also a good idea to remove all the tags from the new file as well if you care about being able to check out old versions. |
Good tips. I'll try that next time I move a file. |
i try to use this git repo to test build and sems to get out-of-sync from CVS for some files:
thanks!
The text was updated successfully, but these errors were encountered: