Hi Lydia, yes, I forgot to mention the message:
warning: --specialize was set, but CHPL_TARGET_ARCH is 'unknown'. If you want any specialization to occur please set CHPL_TARGET_ARCH to a proper value. One readme file told me that Chapel will use the best matching value vor CHPL_TARGET_ARCH automatically. I unset CHPL_COMM. Now CHPL_TARGET_ARCH turned into "native"... huh, I didn't change it since my last mail but ok. Unfortunately the message about SysCTypes stayed. bye Zitat von Lydia Duncan <[email protected]>: > Hi Michael (and Kyle, for reasons that will become apparent), > > I think having the value of CHPL_TARGET_ARCH be unknown is your > problem. I'm not sure how to fix this, but Kyle Brady will probably > have a better idea as he implemented that part of the code. > > Additionally, it looks like you have CHPL_COMM set in your > environment, the default value should be none rather than gasnet. > Try `unset CHPL_COMM` and verify that another run of printchplenv > shows that variable to be none. If that doesn't work, you will need > to set CHPL_COMM=none directly (and we'll need to figure out why > that didn't default correctly). > > Hope that helps, and thanks for your continued interest in Chapel, > Lydia > > On 10/20/2014 10:58 AM, Michael Dietrich wrote: >> Hi Lydia, >> >> the command is working now and gave me some output [1]. >> >> The variables you mentioned have the values they should have. >> >> I think I didn't build the multi-locale version. I don't remember >> how I did this with the last release but as far as I know it needs >> more then just executing the given make-file. >> >> bye >> >> [1] https://www-user.tu-chemnitz.de/~michd/output >> >> >> Zitat von Lydia Duncan <[email protected]>: >> >>> Hi Michael, >>> >>> printchplenv not found makes me think that perhaps you don't have >>> your path set up correctly. Have you run the command `source >>> util/setchplenv.bash` from the Chapel top level directory? That >>> won't solve your make problem but it will allow you to >>> printchplenv straight. Alternatively, that command lives in the >>> util directory, so you can just run it from there, i.e. >>> `util/printchplenv`. >>> >>> When you have the result of printchplenv, please pass that along. >>> There are some things you can do to verify on your own what is set >>> up - for instance, make sure that CHPL_HOME matches what you >>> expect and that CHPL_HOST_PLATFORM seems like a reasonable value. >>> Are you intending to build the multi-locale version first (given >>> the error message you copied, it looks like you're trying to, >>> which given the other information present leads me to believe that >>> you've set that variable)? >>> >>> Hope this helps somewhat, >>> Lydia Duncan >>> >>> On 10/20/2014 09:23 AM, Michael Dietrich wrote: >>>> Hello Tom and Brad, >>>> >>>> about the printchplenv command: I get the message that this command is >>>> not found. It belongs to Chapel, right? Apparently this also doesn't >>>> work correctly. >>>> >>>> About finding that data: There I don't get any output so it seems it's >>>> not there. >>>> >>>> About compiling: I severaly tried running "make", re-doing it and even >>>> re-downloading the release before trying again. Unfortunately it >>>> didn't help either. I didn't change any environment variables since it >>>> wasn't necessary. Building the previous release worked perfectly after >>>> the first try. >>>> >>>> After re-doing "make" it still returns some error messages, including: >>>> >>>> ../../../include/chpl-tasks.h:50: Error: expected »)« before »*« token >>>> // For several lines >>>> >>>> comm-gasnet.c:47: Error: expected »=«, »,«, »;«, »asm« or >>>> »__attribute__« before »chpl_comm_diagnostics_sync« >>>> // Followed by some more missing declarations >>>> >>>> make[6]: *** >>>> [gen/linux64.gnu.arch-unknown.loc-flat.comm-gasnet.udp.everything.tasks-qthreads.tmr-generic.mem-cstdlib.atomics-intrinsics.none.gmp.hwloc.re2.wide-struct.fs-none/comm-gasnet.o] >>>> >>>> Error >>>> 1 >>>> >>>> make[5]: *** [gasnet.makedir] Error 2 >>>> make[4]: *** [comm.makedir] Error 2 >>>> make[3]: *** [src.makedir] Error 2 >>>> make[2]: *** [all.helpme] Error 2 >>>> make[1]: *** [runtime] Error 2 >>>> make: *** [comprt] Error 2 >>>> >>>> >>>> Would it in the worst case be possible to make the built compiler >>>> available for downloading? >>>> >>>> bye >>>> >>>> Zitat von Brad Chamberlain <[email protected]>: >>>> >>>>> Hi Michael -- >>>>> >>>>> Adding to Tom's response: SysCTypes is a module that should be built >>>>> when you do >>>>> your top-level "make" command from $CHPL_HOME and should end up in >>>>> modules/standard/gen/$CHPL_TARGET_PLATFORM-$CHPL_TARGET_COMPILER. >>>>> Re-running 'make' from $CHPL_HOME should cause it to attempt to rebuild >>>>> the module or generate an error if something goes wrong. Could send >>>>> the result >>>>> of that output if it doesn't seem to complete properly? >>>>> >>>>> I think one of the main ways that this can go missing is if you >>>>> change one of those >>>>> two variables after you've done your 'make' without doing another >>>>> 'make' (Chapel >>>>> only builds the current configuration at any given time). >>>>> >>>>> -Brad >>>>> >>>>> ________________________________________ >>>>> From: Tom MacDonald [[email protected]] >>>>> Sent: Friday, October 17, 2014 7:31 AM >>>>> To: Michael Dietrich; [email protected] >>>>> Subject: RE: Unknown Error Message >>>>> >>>>> Hi Michael, >>>>> >>>>> Can you send us the output from running the following command: >>>>> >>>>> printchplenv >>>>> >>>>> There should exist a SysCTypes.chpl file. Please run the >>>>> following command: >>>>> >>>>> find $CHPL_HOME -name 'SysCTypes.chpl' >>>>> >>>>> to see if it is installed. >>>>> >>>>> Thanks >>>>> >>>>> Tom MacDonald >>>>> >>>>> -----Original Message----- >>>>> From: Michael Dietrich [mailto:[email protected]] >>>>> Sent: Friday, October 17, 2014 5:49 AM >>>>> To: [email protected] >>>>> Subject: Unknown Error Message >>>>> >>>>> Hello, >>>>> >>>>> since I got the new release of Chapel I get the following error >>>>> message when I try to compile: >>>>> >>>>> error: Can't find standard module 'SysCTypes' >>>>> >>>>> I have no idea what it could mean. Any suggestions? >>>>> >>>>> bye >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Comprehensive Server Monitoring with >>>>> Site24x7. >>>>> Monitor 10 servers for $9/Month. >>>>> Get alerted through email, SMS, voice calls or mobile push notifications. >>>>> Take corrective actions from your mobile device. >>>>> http://p.sf.net/sfu/Zoho >>>>> _______________________________________________ >>>>> Chapel-users mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/chapel-users >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Comprehensive Server Monitoring with >>>>> Site24x7. >>>>> Monitor 10 servers for $9/Month. >>>>> Get alerted through email, SMS, voice calls or mobile push notifications. >>>>> Take corrective actions from your mobile device. >>>>> http://p.sf.net/sfu/Zoho >>>>> _______________________________________________ >>>>> Chapel-users mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/chapel-users >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Comprehensive Server Monitoring with >>>> Site24x7. >>>> Monitor 10 servers for $9/Month. >>>> Get alerted through email, SMS, voice calls or mobile push notifications. >>>> Take corrective actions from your mobile device. >>>> http://p.sf.net/sfu/Zoho >>>> _______________________________________________ >>>> Chapel-users mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/chapel-users >> >> >> ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
