db m wrote: > > There's a number of these, where environment variables are thrown up > like above, as a prefix to configure, which *should* result in a > correct library > path (pkgconfig path, gcc build..), but it seems this isn't always the > case. I've > redressed a few already, but there's no doubt more in the wiki wherein you > have to state the intention as an export (ie; export USE_ARCH=32 as > opposed to including it on the configure line). There appears to be > multiple > reasons for this, I believe the most of which are caused by a makefile in > certain packages which call in other helper apps (xmkmf, perl, others...) > during the make process, at which time the environment variables sent > to configure are unset and the (generated makefiles..) have no way to > pass the variables onto the helper apps on which the build relies.....or > something like this.... Correct, but I seriously doubt this is the case with pango, since everything happens during the configure stage. The problem is most likely with xmkmf itself.
_______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
