On 05/16/2014 05:38 PM, leif wrote: > Montgomery-Smith, Stephen wrote: >> I was building sage-6.2 using FreeBSD. I found out that the subpackage >> libm4ri was picking up the system libpng rather than the sage libpng. I >> was able to fix it with the following patch: >> >> --- build/pkgs/libm4ri/spkg-install-orig 2014-05-16 >> 18:34:53.000000000 +0000 >> +++ build/pkgs/libm4ri/spkg-install 2014-05-16 18:48:25.000000000 >> +0000 >> @@ -54,6 +54,7 @@ >> >> cd $ROOT_DIR/src/ >> >> +env PKG_CONFIG_LIBDIR=$SAGE_LOCAL/lib/pkgconfig \ >> ./configure --prefix="$SAGE_LOCAL" --libdir="$SAGE_LOCAL/lib" >> $ENABLE_DEBUG $DISABLE_SSE2 >> >> if [ $? -ne 0 ]; then >> > > ? We prepend Sage's pkg-config dir to PKG_CONFIG_PATH in sage-env... > > Or actually no longer... This is now done in our local/bin/pkg-config > wrapper script. > > Probably some flaw in our dependencies? > > Or do you happen to have PKG_CONFIG_DIR (rather than _PATH) set, and > that overrides PKG_CONFIG_PATH?
It doesn't look like PKG_CONFIG_* is set. Which subpackage creates pkg-config? The pkgconfig subpackage was created AFTER the libm4ri subpackage. So maybe that is the cause of the problem. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
