Hi - FYI, and for the archives.
This patch is now on master from PR # 4913. https://github.com/chapel-lang/chapel/pull/4913 Cheers, -michael On 11/23/16, 9:14 AM, "Michael Ferguson" <[email protected]> wrote: >Hi - > >Try the below patch, also attached. I'm using master (vs >the 1.14 release) but you might be able to apply the patch >to the release. > >If this works for you, I think we should consider making >this change on master since others have run into the same >problem. (But I'd like to hear some more discussion of it). > >Cheers, > >-michael > >diff --git a/compiler/Makefile b/compiler/Makefile >index c0110ac..971e1f6 100644 >--- a/compiler/Makefile >+++ b/compiler/Makefile >@@ -113,7 +113,8 @@ include $(COMPILER_ROOT)/make/Makefile.compiler.rules > # > > CHPL_CONFIG_CHECK_PREFIX = $(CHPL_BIN_DIR)/.built-for >-CHPL_CONFIG_CHECK = >$(CHPL_CONFIG_CHECK_PREFIX)-$(CHPL_MAKE_COMPILER_SUBDIR) >+CHPL_CONFIG_CHECK_DIR = >$(CHPL_CONFIG_CHECK_PREFIX)/$(CHPL_MAKE_COMPILER_SUBDIR) >+CHPL_CONFIG_CHECK = $(CHPL_CONFIG_CHECK_DIR)/built-for > > UPDATE_BUILD_VERSION = $(CHPL_MAKE_HOME)/util/devel/updateBuildVersion > >@@ -123,7 +124,8 @@ $(BUILD_VERSION_FILE): FORCE > test -r $(BUILD_VERSION_FILE) || (echo '"0"' > $@); > > $(CHPL_CONFIG_CHECK): | $(CHPL_BIN_DIR) >- rm -f $(CHPL_CONFIG_CHECK_PREFIX)-* >+ rm -rf $(CHPL_CONFIG_CHECK_PREFIX) >+ mkdir -p $(CHPL_CONFIG_CHECK_DIR) > echo $(CHPL_MAKE_COMPILER_SUBDIR) > $(CHPL_CONFIG_CHECK) > > >diff --git a/util/printchplenv b/util/printchplenv >index be9d86b..e66b1d2 100755 >--- a/util/printchplenv >+++ b/util/printchplenv >@@ -209,7 +209,7 @@ def print_var(env_var, value, mode, short_name='', >filters=None): > elif mode == 'compiler' or mode == 'runtime' or mode == 'launcher': > if not filters or mode in filters: > if not print_var.first_time: >- stdout.write(".") >+ stdout.write("/") > else: > print_var.first_time = False > > > > >On 11/22/16, 7:00 PM, "Stéphane Zuckerman" <[email protected]> >wrote: > >>Hi, >> >> >>I am trying to build Chapel on an Ubuntu 16.10 which runs e-cryptfs. As >>other users have pointed out, e.g., here: >> >>https://sourceforge.net/p/chapel/mailman/message/34914082/ >><https://sourceforge.net/p/chapel/mailman/message/34914082/> >> >> >>… One of the python scripts generates filenames which are too long when >>using '.' as a separator when running e-cryptfs. I tried substituting the >>dot ('.') of util/printchplenv in print_env by '/' which does get rid of >>the "filename too long" error, but now >> gives me a new error: >> >>echo linux64/gnu/wide-struct/llvm-none > >>/path/to/chapel-1.14.0/bin/linux64/.built-for-linux64/gnu/wide-struct/llv >>m >>-none >>/bin/sh: 1: cannot create >>/path/to/chapel-1.14.0/bin/linux64/.built-for-linux64/gnu/wide-struct/llv >>m >>-none: Directory nonexistent >> >> >>(which is true, there is no such directory) >> >> >>I'm currently stuck at this stage. I did try to tinker with the makefiles >>in the compiler/ and runtime/ directories, but to no avail. Any insight >>as to why I have this problem and what I could do to fix would be most >>appreciated. >> >> >> >>Thanks, >> >>Stéphane > ------------------------------------------------------------------------------ _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
