They are the same actually, with the exception of flag "-s" that I have here and which doesn't seem to exist as a valid flag (not sure where it comes from yet). Is there a place to check more precisely how the package is built (version of gcc, cmake command, etc.)?
And do you also notice different speeds between packaged and compiled binaries? Bruno On 26/03/13 15:41, Anton Gladky wrote: > Most of flags are taken from build-environment, as it should be. The > current flags are: > > -Dplugins_EXPORTS -Wall -g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security > -DYADE_PTR_CAST=static_pointer_cast -DYADE_CAST=static_cast -fPIC > -DYADE_VTK -DYADE_OPENMP -fopenmp -DYADE_GTS -DQGLVIEWER_FOUND > -DYADE_OPENGL -frounding-math -DYADE_CGAL -DYADE_GL2PS -O3 -DNDEBUG > -fPIC > > They should not differ drastically from your local builds. > > Anton > > > 2013/3/26 Bruno Chareyre <[email protected]>: >> Hi, >> Am I the only one seeing an increase in computation time when using yade >> compiled locally compared to yade-daily (order of +50%)? >> Are there special compilation options used for the packaged binaries? >> >> Bruno >> >> >> >> -- _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
