[parsec-users] which program supports solaris/sparc ?

Christian Bienia cbienia at CS.Princeton.EDU
Fri Apr 11 12:37:59 EDT 2008


Huan,

You're right, you get these errors because your compiler is too old. You need 
at least version 4.2 if you want to compile everything with gcc.

- Chris



On Friday 11 April 2008 09:48 am, Huan Fang wrote:
> Hi Javier,
>
> I really appreciate your sharings, x264 problems are fixed now.
> For dedup, It stops at
> [PARSEC] Running 'env version=parallel gmake':
> gcc: unrecognized option `-pthread'
>
> Similar, freqmine stops at
> [PARSEC] Copying source code of package freqmine.
> [PARSEC] Running 'env CXXFLAGS=-O3 -funroll-loops -fprefetch-loop-arrays
> -fpermissive -fno-exceptions -DPARSEC_VERSION=1.0 -fopenmp gmake':
> /usr/sfw/bin/g++ -O3 -funroll-loops -fprefetch-loop-arrays -fpermissive
> -fno-exceptions -DPARSEC_VERSION=1.0 -fopenmp -Wno-deprecated -c
> fpmax.cpp -o fpgrowth.o
> cc1plus: error: unrecognized command line option "-fopenmp"
>
> I guess the errors above are related to compiler version. In my system :
> gcc version 3.4.3 (csl-sol210-3_4-20050802)
>
> Do you guys have the same problems?
>
> Regards,
> Huan
>
> > Hi,
> >
> > You are finding the same problems I found one month ago!
> >
> > For compiling that workload I make these fixes:
> >
> > Firstly, I had to modify the configure file in order to use /bin/bash
> > instead /bin/sh. This is because, for any reason, sh does not recognize
> > a substitution for getting the OS version.
> >
> > There is a one change more in configure script. You should enforce ECHON
> > variable to have the value "printf" instead of "echo -n".
> >
> > Finally, you should have to add the following define in the source file
> > "encoder/ratecontrol.c":
> > #define isfinite _finite
> >
> > Until now, I will have compiled the same workloads as you for
> > Solaris/sparc. If you find the way for successfully compiling some of
> > the rest workloads, I encourage you to share the fix needed to do that.
> >
> > Best regards,
> >
> > Javier
> >
> > On Fri, 2008-04-11 at 12:00 +0000, Huan Fang wrote:
> >> Anyway, I have moved to another newer machine with OpenSolaris
> >> installed. So far I have successfully compiled blackscholes, bodytrack,
> >> swaptions, fluidanimate, vips, streamcluster.
> >> As to x264, there is an error:
> >>
> >> [PARSEC] Running 'env
> >> PATH=/export/home/huanf/parsec-1.0/bin/../bin:/usr/sfw/bin:/usr/ccs/bin:
> >>/usr/sbin:/export/home/huanf/parsec-1.0/bin/../bin:/export/home/huanf/par
> >>sec-1.0/bin/../pkgs/tools/yasm/inst/sparc-solaris.gcc/bin:/usr/bin:/expor
> >>t/home/huanf/parsec-1.0/bin/../pkgs/tools/yasm/inst/sparc-solaris.gcc/bin
> >> ./configure --enable-pthread --extra-asflags= --extra-cflags=-O3
> >> -funroll-loops -fprefetch-loop-arrays -DPARSEC_VERSION=1.0
> >> --extra-ldflags=-L/usr/sfw/lib64 -L/usr/sfw/lib
> >> --prefix=/export/home/huanf/parsec-1.0/bin/../pkgs/apps/x264/inst/sparc-
> >>solaris.gcc': ./configure: bad substitution
> >> [PARSEC] Error: 'env
> >> PATH=/export/home/huanf/parsec-1.0/bin/../bin:/usr/sfw/bin:/usr/ccs/bin:
> >>/usr/sbin:/export/home/huanf/parsec-1.0/bin/../bin:/export/home/huanf/par
> >>sec-1.0/bin/../pkgs/tools/yasm/inst/sparc-solaris.gcc/bin:/usr/bin:/expor
> >>t/home/huanf/parsec-1.0/bin/../pkgs/tools/yasm/inst/sparc-solaris.gcc/bin
> >> ./configure --enable-pthread --extra-asflags= --extra-cflags=-O3
> >> -funroll-loops -fprefetch-loop-arrays -DPARSEC_VERSION=1.0
> >> --extra-ldflags=-L/usr/sfw/lib64 -L/usr/sfw/lib
> >> --prefix=/export/home/huanf/parsec-1.0/bin/../pkgs/apps/x264/inst/sparc-
> >>solaris.gcc' failed.
> >>
> >> Hope this information helpful.
> >>
> >>> Huan,
> >>>
> >>> The hooks package is usually compiled first because all other packages
> >>> depend on it. We don't support dynamic dependencies, so the hooks
> >>> package will get build even if you don't need it. It seems there's a
> >>> general issue with the way parsecmgmt works on your machine. It seems
> >>> that parsecmgmt wasn't able to copy the source tree to the build
> >>> directory. Could you compare the two directories
> >>>
> >>> /parsec-1.0/pkgs/libs/hooks/obj/sparc-solaris.gcc
> >>>
> >>> and
> >>>
> >>> /parsec-1.0/pkgs/libs/hooks/src
> >>>
> >>> on your machine? They should be identical. If not that the copy command
> >>> specified in the solaris.sysconfig configuration file in your
> >>> /parsec-1.0/config directory is not working on your platform. By
> >>> default for Solaris it is:
> >>>
> >>> # Usage: ${CP} SOURCE... DESTINATION
> >>> CP="cp -pRPf"
> >>>
> >>> Could you try it out manually? It works on my Solaris machine.
> >>>
> >>> - Chris
> >>>
> >>> On Thursday 10 April 2008 01:43 pm, Huan Fang wrote:
> >>>> Thanks for the useful informations! parsec can recognize my compiler
> >>>> now. Unfortunately, the error remains:
> >>>> [PARSEC] Error: Cannot find Makefile in
> >>>> /parsec-1.0/bin/../pkgs/libs/hooks/obj/sparc-solaris.gcc
> >>>>
> >>>> It seems something wrong with hooks, but I didn't use gcc-hook. Do you
> >>>> have any idea for this? BTW, my gcc version is 2.8.1, is this the
> >>>> reason for that?
> >>>>
> >>>> Regards,
> >>>> Huan
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> You should modify the file config/gcc.bldconf to allow parsecmgmt to
> >>>>> find your compiler.
> >>>>>
> >>>>> I have already compiled 7 of the Parsec workloads: blackscholes,
> >>>>> bodytrack, fluidanimate, streamcluster, swaptions, vips and x264
> >>>>> (this one modifying something solaris specific).
> >>>>>
> >>>>> The main problems I found were that the pthread library delivered
> >>>>> with Solaris 9 is not the one needed by Parsec. It will require
> >>>>> Solaris 10 instead. And, as README file says, the gcc compiler should
> >>>>> be at least the 4.2.X version.
> >>>>>
> >>>>> I hope my experience compiling that could help you. If someone else
> >>>>> have compiled some of the rest of the Parsec workloads for
> >>>>> Solaris/Sparc environment, please kindly tell your story to know how
> >>>>> you do it.
> >>>>>
> >>>>> Many thanks and best regards,
> >>>>>
> >>>>> Javier
> >>>>>
> >>>>> On Thu, 2008-04-10 at 12:07 +0000, Huan Fang wrote:
> >>>>>> Hello,
> >>>>>>
> >>>>>> I am trying to compile some programs for solaris/sparc, but it fails
> >>>>>> all the time. what I got is:
> >>>>>>
> >>>>>> [PARSEC] Warning: At least bash version 3 is recommended. Earlier
> >>>>>> versions might not function properly. Current version is
> >>>>>> 2.05.0(1)-release. ./parsecmgmt: /usr/bin/gcc: No such file or
> >>>>>> directory ./parsecmgmt: /usr/bin/g++: No such file or directory
> >>>>>> [PARSEC] Packages to build:  bodytrack
> >>>>>>
> >>>>>> [PARSEC] [========== Building package bodytrack ==========]
> >>>>>> [PARSEC] [---------- Analyzing package bodytrack ----------]
> >>>>>> [PARSEC] bodytrack depends on: hooks
> >>>>>> [PARSEC] [---------- Analyzing package hooks ----------]
> >>>>>> [PARSEC] hooks does not depend on any other packages.
> >>>>>> [PARSEC] [---------- Building package hooks ----------]
> >>>>>> [PARSEC] Removing old build directory.
> >>>>>> [PARSEC] Copying source code of package hooks.
> >>>>>> [PARSEC] Error: Cannot find Makefile in
> >>>>>> /parsec-1.0/bin/../pkgs/libs/hooks/obj/sparc-solaris.gcc
> >>>>>>
> >>>>>> I believe there are gcc/g++ in my system, but apparently it's not in
> >>>>>> /usr/bin.
> >>>>>> So how can I fix things up and which programs are verified to be
> >>>>>> successfully compiled on solaris?  Thanks a lot.
> >>>>>>
> >>>>>> Best Regards,
> >>>>>> Huan Fang
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> 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
> >>
> >> _______________________________________________
> >> 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