On Tue, 19 Jun 2012, Amul Shah wrote: > chmod: cannot access `gtmcrypt_ref.c': No such file or directory > chmod: cannot access `gtmcrypt_ref.h': No such file or directory > chmod: cannot access `gtmcrypt_interface.h': No such file or directory > chmod: cannot access `gtmxc_types.h': No such file or directory > chmod: cannot access `maskpass.c': No such file or directory > chmod: cannot access `gtmcrypt_dbk_ref.c': No such file or directory > ...
> I guess they shouldn't just be ignored, right? but those .c's are the > original sources which aren't installed with the "stage1" installation -- > is that just some legacy pieces in configure or am I missing smth? > [amul:1] I asked Brad to tar those C files into source.tar which the > configure script is trying to do. If we revert that bit, the configure > script will work just fine. Or we fix the configure script to not package > the tar ball when it is already present. I am sorry but I am a bit lost since I do not see any relevant commits in those files: $> git lg sr_unix/configure.gtc sr_unix/gtminstall.sh * dee7100 - (5.5-000, origin/v55000, gh-yarikoptic/v55000) ENH: Version 5.5000 from sourceforge. (3 months ago) [Luis Ibanez] * 9299623 - (origin/v54002B, origin/master, origin/HEAD, gh-yarikoptic/v54002B, gh-yarikoptic/master, master) ENH: Initial import from sourceforge. (5 months ago) [Luis Ibanez] anyways -- are they needed anyhow for stage2 building/installation to obtain the ultimate installation ? ;) -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
