[parsec-users] General build failure

Amittai Aviram amittai.aviram at yale.edu
Sat Jun 27 10:55:31 EDT 2009


I commented that line out in sys/types.h (temporarily!), and I was  
able to build until the next error :-).  I'll post separately about  
that.  Thanks!

Amittai

Amittai Aviram
Graduate Student in Computer Science
Yale University
646 483 2639
amittai.aviram at yale.edu
http://www.amittai.com

On Jun 27, 2009, at 10:33 AM, Christian Bienia wrote:

> Amittai,
>
> That seems to be an incompatibility between your system header files  
> and
> your compiler. I don't see what exactly causes the error. Try  
> playing around
> with the code and hopefully you'll be able to work around it.
>
> Best,
> Chris
>
>
> -----Original Message-----
> From: parsec-users-bounces at lists.cs.princeton.edu
> [mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of  
> Amittai
> Aviram
> Sent: Saturday, June 27, 2009 10:13 AM
> To: PARSEC Users
> Subject: Re: [parsec-users] General build failure
>
> Thanks, Christian!  Now PARSEC is able to build blackscholes, but I am
> getting a new compilation error on bodytracker:
>
> /usr/include/sys/types.h:153: error: duplicate 'unsigned'
> /usr/include/sys/types.h:153: error: multiple types in one declaration
>
> Now, here's what that line says in my sys/types.h:
>
> #ifdef __USE_MISC
> /* Old compatibility names for C types.  */
> typedef unsigned long int ulong;
> typedef unsigned short int ushort;
> typedef unsigned int uint;    // <-- LINE 153
> #endif
>
> Any idea why this is signalled as an error?  Thanks!
>
> Amittai Aviram
> Graduate Student in Computer Science
> Yale University
> 646 483 2639
> amittai.aviram at yale.edu
> http://www.amittai.com
>
> On Jun 27, 2009, at 1:00 AM, Christian Bienia wrote:
>
>> Amittai,
>>
>> You need to adapt the build configuration of PARSEC. To do that go
>> to the
>> config directory and edit gcc.bldconf.
>>
>> Best,
>> Chris
>>
>>
>>
>> -----Original Message-----
>> From: parsec-users-bounces at lists.cs.princeton.edu
>> [mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of
>> Amittai
>> Aviram
>> Sent: Friday, June 26, 2009 11:44 PM
>> To: parsec-users at lists.cs.princeton.edu
>> Subject: [parsec-users] General build failure
>>
>> Hi!  I am trying to do the default complete build by running
>>
>> parsecmgmt -a build
>>
>> But I am getting the following error:
>>
>> [PARSEC] [---------- Analyzing package blackscholes ----------]
>> [PARSEC] blackscholes does not depend on any other packages.
>> [PARSEC] [---------- Building package blackscholes ----------]
>> [PARSEC] Removing old build directory.
>> [PARSEC] Copying source code of package blackscholes.
>> [PARSEC] Running 'env version=pthreads /usr/bin/make':
>> rm -f blackscholes  blackscholes.m4.cpp
>> /usr/bin/m4 ./c.m4.pthreads blackscholes.c > blackscholes.m4.cpp
>> /usr/local/gcc-4.2.1/bin/g++ -O3 -funroll-loops -fprefetch-loop- 
>> arrays
>> -fpermissive -fno-exceptions -DPARSEC_VERSION=2.0 -pthread -
>> DENABLE_THREADS -DN=960 -DNCO=2   blackscholes.m4.cpp -L/usr/local/
>> gcc-4.2.1/lib64 -L/usr/local/gcc-4.2.1/lib  -o blackscholes
>> make: /usr/local/gcc-4.2.1/bin/g++: Command not found
>> make: *** [blackscholes] Error 127
>> [PARSEC] Error: 'env version=pthreads /usr/bin/make' failed.
>>
>>
>> It looks to me as if parsecmgmt "thinks" that g++ is found at /usr/
>> local/gcc-4.2.1/bin/g++, but, on my system, it's at /usr/local/bin/
>> gcc .  Does this mean that the system provided the wrong information
>> to parsec's configuration script?  In any event, what should I do?
>>
>> If I have to compile manually, and I want to use pthreads, should I
>> run make in each app/src directory this way? --
>>
>> make version=pthreads
>>
>> Thanks!
>>
>>
>>
>> Amittai Aviram
>> Graduate Student in Computer Science
>> Yale University
>> 646 483 2639
>> amittai.aviram at yale.edu
>> http://www.amittai.com
>>
>> _______________________________________________
>> parsec-users mailing list
>> parsec-users at lists.cs.princeton.edu
>> https://lists.cs.princeton.edu/mailman/listinfo/parsec-users
>>
>> _______________________________________________
>> parsec-users mailing list
>> parsec-users at lists.cs.princeton.edu
>> https://lists.cs.princeton.edu/mailman/listinfo/parsec-users
>
> _______________________________________________
> parsec-users mailing list
> parsec-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/parsec-users
>
> _______________________________________________
> parsec-users mailing list
> parsec-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/parsec-users



More information about the parsec-users mailing list